The software industry has engendered a culture of distracted programmers using bad tools to solve problems they don’t have time to fully understand. In this essay, I try to explore why. https://medium.com/@smarimc/when-programming-became-a-chore-a0be2b9919c0
@smari Have you worked on an engineering team with really great programmers new to the language you are maintaining? I ask because actually I prefer several of the the anti-patterns in the essay for the sake of either inten-revealing simplicity (in the case of isOdd, although why use NPM when you could create the function in two lines?) or propagating errors to the front end (in the case of the HTTP response codes).
@ratamacue I've worked on engineering teams with well educated, but somewhat junior programmers ─ which I think is similar. I'm not sure the goal of a collective working group should be to "reveal the interns"; but perhaps I'm missing your point?
@smari Oops.. Typo: Should have said "intent-revealing"
@ratamacue ahh! I see. I'm not actually complaining about calling things good intent-revealing names, note. I'm more complaining about the line of thinking that leads people to doing it in that particular way.
@smari Agreed. I work in a PCI-DSS certified company, and it's nice how much scrutiny we give to even simple additions to our external dependencies. That dependency would never fly in package.json. Although a package with common math operations inside the project, including a function to check if something is odd probably would fly.
@ratamacue yes. That also breaks out of the thing I'm pointing to about including the logic rather than the interface. I guess I'm saying I prefer assimilate to graft. Borg > Vidiians.
