2 ms·
There's a difference between hiring someone who is a C#/Java programmer and someone who can program in C#/Java. That's my point. As for Product Managers and QA
by staunch 19y ago
There's a difference between hiring someone who is a C#/Java programmer and someone who can program in C#/Java. That's my point.
As for Product Managers and QA people. They have a tendency to slow development down to a level they can manage and test. I avoid them both like the plague.
- Tichy 19y agoUm, what's so bad about being a Java/C# programmer? Is the hubris of the scripting crowd really that sky-high?
- staunch 19y agoNot sure. I didn't say anything was bad about being one. I don't speak for any crowds either.
- Tichy 19y agoSo what exactly was the point you were trying to make?
- mynameishere 19y agoOh, for the love of beans, they're taking the words straight from the mouth of St. Paul: http://www.paulgraham.com/pypar.html http://www.paulgraham.com/pypar.html
- hello_moto 19y agoThey might slow the development down but to what advantage? Better design docs, better func spec, better docs, better quality. If your startup has a room to grow, this is one option to go. You don't just hire all developers and hope your software doesn't have bugs. Cowboy code a.l.a Agile (the bad Agile) is very dangerous and this is what some people warn these young startup people. The whole RoR (or Python/PHP, whatever) + Agile is like playing with fire; if you know how to stop it, you're in a great shape, if you don't, it'll burn your product faster than any other mistakes.