Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're arguing idealism; I'm arguing reality. In most cases, programmers serve a role that is closer to the construction worker than the architect.


Sure, and maybe right now is not the time to find a new job, but being treated like a construction worker should not be acceptable to any competent programmer. I'm not arguing that it doesn't happen, just that it doesn't have to be that way. Anyone stuck in those kind of conditions should know that there are better jobs out there where they can be treated like smart, competent adults instead of code monkeys.


I'm with cstejerean on this issue. Remember the premise of the original article was an idealistic one, it basically said: "Which kind of programmer should you hire when you have a choice".

Given the goal is to make money I know which kind of team I would prefer. I'd definately prefer the one that automates everything out of the way as soon as possible because in an IT-heavy operation that really is one of the most basic dogmas in order to maintain momentum in the long term. If your goal is to cash out fast and close shop in 2 years then fine, spit and glue may be just right for your project. If your goal is to build to last then you'd damn sure better hire people who know what they're doing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: