> Gets very emotionally attached to programming decisions, even if they will have no effect on the user. Well, yeah? A lot of decisions affect the programmers

> Gets very emotionally attached to programming decisions, even if they will have no effect on the user. Well, yeah? A lot of decisions affect the programmers — how easy will the code be to manage, extend, etc. Just because it has no effect on the user directly doesn't mean it isn't important. > Isn’t actually very capable creating software (hasn’t won any coding competitions, has trouble with git reset, hasn’t written any software that people enjoy using) Coding competition wins are a prereq for being capable? > Probably studied philosophy, english, film-studies, or engineering. This is absurd. You're throwing out the good with the bad here. REST, microservices, SOLID, being passionate about the quality of the work are all good things. That they're presented poorly, or being overused where they're not needed is a separate issue, but that doesn't make the points of those things less correct. Frankly, the original article[1] that seems to be the source of this rant didn't seem well written, but this is hardly constructive criticism of it. The original comment[2] from the author of this post (mentioned in the post, but not linked, unfortunately) was better, and while I feel some of the pain lamented (people assigning terms to ideas so simple they're better expressed directly; inscrutable UML diagrams), this post simply seeks to brand those people with a form of ad hominem rather than engage in debate with them. [1]: http://www.firatatagun.com/blog/2016/01/09/analysis-of-software-architectures/ http://www.firatatagun.com/blog/2016/01/09/analysis-of-softw... [2]: https://news.ycombinator.com/item?id=10872314 https://news.ycombinator.com/item?id=10872314