3 ms·
I also hate the "tool fetish" (and general advocacy of hidden but substantial complexity) that the software industry seems to have created... Programmers like
by userbinator 4y ago
I also hate the "tool fetish" (and general advocacy of hidden but substantial complexity) that the software industry seems to have created...
Programmers like to think that they spend all their time creating elaborate & complex abstractions
...and that's the essence of the problem. If you want to create needless complexity, you'll also suffer its consequences.
although there absolutely still is a pretty strong contingent of people that advocate for a reversion to a “simpler” way of doing things
I'm one of these, and I still avoid additional tools like the plague, unless they offer a very clear cost-benefit tradeoff. The vast majority of what I do needs only a few windows of a plaintext editor and a terminal. In my experience, others I've worked with who are also similarly minimalistic tend to be more competent too; at the other end of the scale, those who seem to love complex tooling are also the ones who need them as a crutch the most.
That said, I have a different view of the "coding" vs "programming" distinction than some of the other comments here; to me, the latter implies more mindless work while the former (exemplified by terms like "sizecoding" or "democoding") refers to a more intimate and lower-level knowledge of what's going on, along with increased creativity and a problem-solving perspective.
- asdff 4y agoPeople need to live by the quote of "learn the rules before you break them." Its fine to use abstractions to save you time perhaps, but if you use them without understanding how they work, the considerations or assumptions being made, or what these results mean compared to alternatives, you are trodding off into the dangerous unknown, maybe even moving backwards. Uncertainty should be minimized.
- akkad33 4y agoCan you give a resource on how a non programmer can learn these things? I learned and used Design patterns and functional programming techniques but I think I lack a foundational knowledge and feeling for why these are useful and why one is better than the other
- asdff 4y agoRead the documentation for whatever language or tool you are working with. Read the textbooks assigned in computer science university courses if you want to go further. But specific to abstractions, say you have some tool that promises some way to structure your data or allow you to plot a chart or something like that. It's important to know how to do what this tool does the "old fashioned way" without the tool, so you can even vet whether the tool is actually useful or just more cruft you really don't need if you did your due diligence.
- Lerc 4y agoI'm with you on this. I'm ok with tools that tha I choose to make things easier. When a tool is a necessity it is a big red flag. Once you get to compulsory tool chains, you are working in a world of someone else's personal preferences. Android development is like this. Ironically the code I have developed for Android tries to hide all of that by providing another tool to the end of the chain that takes simple code and wraps it in a package of monstrosity for the designated 'correct path' tool chain to use.