At what point do LLMs enable bad engineering practices, if instead of working to abstract or encapsulate toilsome programming tasks we point an expensive slot machine at them and generate a bunch of verbose code and carry on? I'm not sure where the tradeoff leads if there's no longer a pain signal for things that need to be re-thought or re-architected. And when anyone does create a new framework or abstraction, it d…
How much of "good engineering practices" exist because we're trying to make it easy for humans to work with the code? Pick your favorite GoF design pattern. Is that they best way to do it for the computer or the best way to do it for the developer? I'm just making this up now, maybe it's not the greatest example; but, let's consider the "visitor" pattern. There's some framework that does a big loop and calls the visi…
So I don’t care about assembly because it does not matter usually in any metric. I design using code because that’s how I communicate intent.
If you learn how to draw, very quickly, you find that no one talks about lines (which is mostly all you do), you will hear about shapes, texture, edges, values, balance…. It’s in these higher abstractions intent resides.
Same with coding. No ones thinks in keywords, brackets, or lines of code. Instead, you quickly build higher abstractions and that’s where you live in. The pros is that those concepts habe no ambiguity.