|
Requirements analysis
This is a very interesting phase of a project. Like a detective you have to find out what really happens. What people say sometimes differs from what they mean. When you encounter contradictions you need to discuss until you get a commonly agreed upon solution. You have to be an active listener rather than an elaborate talker.
|
|
Programming
Also really interesting. Theoretically, you could let a far-shore junior developer do the programming. At least if your specifications are good enough. In practice experience pays off.
-
Erich Gamma, Richard Helm, Ralph E. Johnson:
Design Patterns. Elements of Reusable Object-Oriented Software.
-
Joshua Bloch: Effective Java. A Programming Language Guide (Java Series)
|
|
Testing
Software without tests is like a car without an air bag. It runs but it's not state of the art.
-
Gerard Meszaros: xUnit Test Patterns. Refactoring Test Code.
|
|
Documentation
Don't forget documenting. You'll be glad having a good documentation when you need it.
|
|
Project Management
Although there is so much knowledge out there on project management it still seems to be quite a challenge.
Inspiring books sometimes with a broader focus are
-
Frederick P. Brooks: The Mythical Man-Month. Essays on Software Engineering. (First published in 1975!)
-
Tom DeMarco: The Deadline. A Novel About Project Management.
-
Kent Beck: Extreme Programming Explained. Embrace Change.
-
Andrew Hunt, David Thomas, Ward Cunningham: The Pragmatic Programmer. From Journeyman to Master.
|
|
|