5 ms·
Also, make sure to read tons about how programmers feel about business guys / managers, and figure out how not to be like those people. There's tons of advice o
by DTrejo 16y ago
Also, make sure to read tons about how programmers feel about business guys / managers, and figure out how not to be like those people. There's tons of advice out there, and there may even be some good advice in the most offensive rants. Read those rants, feel the pain of those programmers, and see the opportunity to improve yourself so you don't inflict similar pain.
Some possibly helpful resources which you may have already seen:
http://www.amazon.com/Peopleware-Productive-Projects-Teams-Second/dp/0932633439 http://www.amazon.com/Peopleware-Productive-Projects-Teams-S...
http://www.joelonsoftware.com/ http://www.joelonsoftware.com/ (right sidebar has a ton of articles)
http://www.amazon.com/Facts-Fallacies-Software-Engineering-Robert/dp/0321117425 http://www.amazon.com/Facts-Fallacies-Software-Engineering-R...
- patrickk 16y agoAlso, read Peopleware. It's an excellent book for anyone who has to manage technical teams. http://www.amazon.com/Peopleware-Productive-Projects-Teams-Second/dp/0932633439/ref=sr_1_1?ie=UTF8&s=books&qid=1281947572&sr=8-1-spell http://www.amazon.com/Peopleware-Productive-Projects-Teams-S... Joel Spolsky mentions that every manager at Microsoft has to read it (I could be wrong on that, but a lot do read it apparently).
- SoftwareMaven 16y agoI think this is SO much more valuable for a biz founder than learning to code. Understanding the development process and developers is critical. On the other hand, knowing how to code is merely useful. (Note: I differentiate "knowing how to code" from being a coder. One means I made it through Python for Dummies; the other means I have a history of making software and understand the issues around it. That is far more than useful.)