,
6 tweets,
1 min read
Read on Twitter
I describe a problem. I get replies telling me to "just" use a solution that involves a million lines of third party code, or 200 transitive dependencies, or a README that says "not ready for production use", or, most often, doesn't even address the stated problem.
Sometimes I get 20 of those! Then, suddenly, the 21st reply gives me a four-line function, with no dependencies, that completely solves the problem.
Reaching for huge tools to solve simple problems is irresponsible. Reaching for explicitly "not ready for production" tools to solve core business problems is irresponsible. Recommending that other people do those things is irresponsible.
Software is unreliable, and it's so difficult to maintain that products often stop changing completely after being bought for billions of dollars. Using the first solution that comes to mind, without analyzing its actual impact, is how you get those buggy, ossified messes.
(This is one of the reasons that I don't like our field being called "engineering" and don't use that word. Balancing constraints is a huge part of engineering. A lot of "software engineering" is the equivalent of attaching a 10 kW diesel generator to a smartphone.)
otoh my phone's battery wouldn't be flat at 6 pm if it had a diesel generator so maybe electrical engineering is bs
