and once you've got your wish: ugly code without tests or a way to comprehend it, but cheap!
How much value are you going to be able to extract over its lifetime once your customers want to see some additional features or improvements?
How much expensive maintenance burden are you incurring once any change (human or LLM generated) is likely to introduce bugs you have no better way of identifying than shipping to your paying customers?
Maybe LLM+tooling is going to get there with producing a comprehensible and well tested system but my anectodal experience is not promising. I find that AI is great until you hit its limit on a topic and then it will merrily generate tokens in a loop suggesting the same won't-work-fix forever.
What you wrote aligns with my experience so far.
It's fast and easy to get something working, but in a number of cases it (Opus) just gets stuck 'spinning' and no number of prompts is going to fix that.
Moreover - when creating things from scratch it tends to use average/insecure/ inefficient approaches that later take a lot of time to fix.
The whole thing reminds me a bit of the many RAD tools that were supposed to 'solve' programming. While it was easy to start and produce something with those tools, at some point you started spending way too much time working around the limitations and wished you started from scratch without it.
I'm of the opinion that the diligence of experts is part of what makes code valuable assets, and that the market does an alright job of eventually differentiating between reliable products/brands and operations that are just winging it with AI[1].
I would think that the better the code is designed and factored and refactored, the easier it is to maintain and evolve, detect and remove bugs and security vulnerabilties from it. The ease of maintenance helps both AI and humans.
There are limits to what even AI can do to code, within practical time-limits. Using AI also costs money. So, easier it is to maintain and evolve a piece of software, the cheaper it will be to the owners of that application.
NVDA has more money than they know what to do with. One strategy when you have extra money is investing it in equities. You exchange money for a slice of future profits. Not sure what the confusion is here
It's all about efficiency. You can store heat in anything, but the question is for how long and how much energy can you get back out later. The first part is easy and how we got ovens and stoves, the second part can be pretty tricky depending on your requirements. Large scale energy storage sometimes uses massive amounts of sand for example, but they heat it to hundreds of degrees which is not really feasible in most settings.
Fine piece of what it's really about. The feeling of losing one's joy and possible applause for doing a good job.
But the inevitable is not a fact, it's a rigged fake that is, unfortunately, adapted by humans which flock in such large groups, echoing the same sentiments that it for those people seem real and inevitable.
Humans in general are extremely predictable, yet, so predictable that they seem utterly stupid and imbecile.
reply