The Psychology of Computer Programming, by Weinberg. Its from 1971 but still relevant. It tackles the management aspect of working in a team, how to handle difficult people etc.
Clean Code, a great book for those interested in adopting a better coding style. Are your routines longer than 5 lines?
Wrestling With Bears , goes into details about how to mitigate risk, evaluate and prioritize requirements and keep your projects on track.
Test Driven iOS Development.
Cocoa Design Patterns (if your an iOS developer); it really helps to understand what is happening under the hood of the API.
Software Engineering by Ian Sommerville, for those interested in design, architecture and large systems. Its a rather long and very traditional (not agile friendly), but its comprehensive and good.
Someone already mentioned K&R, I'd add C++ by Bjarne Stroustrump.
Agile and Iterative Development: A Manager's Guide. Its not really a "managers guide", but more of a "How can I be a good team player" with an introduction on XP/UP and Scrum kind of a guide. Highly recommented.
Just pay for it FFS, why try to combine different free services, and go throuth the trouble of running your own linux server in order to save 10$ a month
oh my god, "!#$ excited kids.
Follow your software design criteria and your design documents, then it should be clear.
One should not simply sit down and hack away changes without careful planing.
Slashdot Mirror
The Psychology of Computer Programming, by Weinberg. Its from 1971 but still relevant. It tackles the management aspect of working in a team, how to handle difficult people etc. Clean Code, a great book for those interested in adopting a better coding style. Are your routines longer than 5 lines? Wrestling With Bears , goes into details about how to mitigate risk, evaluate and prioritize requirements and keep your projects on track. Test Driven iOS Development. Cocoa Design Patterns (if your an iOS developer); it really helps to understand what is happening under the hood of the API. Software Engineering by Ian Sommerville, for those interested in design, architecture and large systems. Its a rather long and very traditional (not agile friendly), but its comprehensive and good. Someone already mentioned K&R, I'd add C++ by Bjarne Stroustrump. Agile and Iterative Development: A Manager's Guide. Its not really a "managers guide", but more of a "How can I be a good team player" with an introduction on XP/UP and Scrum kind of a guide. Highly recommented.
Just pay for it FFS, why try to combine different free services, and go throuth the trouble of running your own linux server in order to save 10$ a month oh my god, "!#$ excited kids.
Follow your software design criteria and your design documents, then it should be clear. One should not simply sit down and hack away changes without careful planing.
Stop trying to be hero's by trying to rebuild countries after destroying them with wars or business blocks.