This field doesn’t do well on long-term thinking. Even if all this turns out to be a net loss, it will be reinterpreted as a win and just an opportunity for even more of the same solution. There are numerous examples of this, e.g. the OOP craze. Tech is a stock market of ideas and HN is a trading floor. The “line goes up” logic applies - not merit.
replyDescribing OOP as a "craze" is incredibly out of touch. It's been a thing for, what, three decades?
replyYou may not recall the crazy era of OOP where people would go bonkers with massive object trees trying to objectify everything and using operator overloading to do (dumb) things like adding a control to a window with +=.
replyOOP is great. "OOP is the one perfect paradigm for all coding" was the craze.
replyI'm sure I'm not the first person you've seen hinting at OOP (and all that came with it) having been hyped up beyond its merits.
replyThere certainly was an OOP craze, that's not out of touch to talk about.
replyAbstractBeanFactoryFactoryInterfaceBeanContextFactoryBeanBean.java
replyThat’s just falls. I’ve spent disproportionate amount on “understanding” awful tooling like Gradle and npm. There’s no value in it if you’re not an infra engineer. It would take me a couple of days to manually restructure my hobby app, now I can just say “extract this into another workspace/subproject” and be done with it in minutes. And that’s just one example.
replyI agree with this sentiment. I just also see AI-driven development in core business logic, where truly understanding what is going on is essential and yet completely disregarded.
replyIf I never have to debug a gradle file ever again, it's all worth it.
replyYou might say the same about garbage collected programming languages. It’s an acceptable tradeoff in a lot of scenarios. Same goes for AI.
reply