Saturday, January 3
A moment ago I noticed this on a slash dot comment, been a good software developer requires the following:
1. understand the problem (interact with people)
2. understand the external constraints (interact with people)
3. design an effective solution to the problem
4. while designing the solution, design some tests to verify that the problem is solved (and remains solved)
5. code the effective solution to the problem
6. teach other team-members about your solution to the problem (interact with people)
This seems very much true, because in people interaction comes the true problem solving aspect of computer science.
1. understand the problem (interact with people)
2. understand the external constraints (interact with people)
3. design an effective solution to the problem
4. while designing the solution, design some tests to verify that the problem is solved (and remains solved)
5. code the effective solution to the problem
6. teach other team-members about your solution to the problem (interact with people)
This seems very much true, because in people interaction comes the true problem solving aspect of computer science.