Programmers think that they hate politics but when it comes down to the actual technical stuff, they do politics as well. Some programmers want to be "relevant

Programmers think that they hate politics but when it comes down to the actual technical stuff, they do politics as well. Some programmers want to be "relevant" in the HN sense so they push new technology that they just picked up last week religiously (node.js for a CRUD app, which most websites are anyway, comes to mind) like it is the next big thing. Or they just read 37Signals books and drank the 37Signals + RoR kool-aid and push 100% 37Signals mindset to the workplace that doesn't fit with that (different target, client base, market, etc). Come back in 3 years time and you'll see the same guy pushing for MVC in client-side/browser as opposed to stick with simplicity yet still pushing 37Signals mindset whenever he refused to do work that doesn't inline with him for whatever reasons (laziness, or else). Or perhaps they came back from Agile meeting and think that Scrum is the only way to run a project that everybody else must follow it. (Hint: Scrum is hard to understand and to apply to a large group of people who don't know Scrum 100%). On the flip side, cowboy coders hate a single addition of "process" even if that process is called Continuous Integration. They'll do whatever it takes to make sure they can continue to code like cowboys. Even the unit-test debate can be considered as politics. Some people want the company to rely on themselves so they prefer no unit-tests. Programmers are notorious with locking in the knowledge in their brain only hence no unit-tests, no documentations. Just Read The F... Code they say. C'mon, don't give me excuses that these are useless except for your weekend projects. We all know that most startups develop from prototypes. They almost rarely re-write their main (with odd codebase) products. ... more reasons to be an indie developer I suppose...