11–20 of 26 posts
Yep. Ongoing problem for decades. And now with “AI” to make it more ridiculous. I look forward to retiring soon and never looking at code again.
But in theory, AI should be able to write directly in assembler. The 'stacks' would be merely layers of understanding in the AI, and it should be able to compress these down to tight assembly code that does the thing required, rather than using actual software layers. In theory.
Or even just insert print("foo") like the barbarian I am.
Now I can't attache the IDE because everything is 50 microservices. I can't print-debug because the logging system requires fully formed JSON output and it's clustered and distributed and billed by line and I need to use a Web UI to see my own application's logs ffs.
Get off my lawn.
Amen! The funny thing is this sounds like a “get off my lawn!” rant, and yet it’s so true if you’ve been around long enough to have seen a few tech cycles. But this also only seems to matter if you are NOT in a “move fast and break stuff” environment.
Abstractions would be fine, if they were solid code. Code that I don't have to write, that I don't have to debug, that I don't have to maintain, is wonderful - if it works. The problem isn't abstractions. The problem is that too many of the abstractions don't work - they have bugs. (Yes, I know, all code has bugs. I even found a bug in the STL once. Still, that's one bug I have seen in it in 30 years. There are other…
Yep. Ongoing problem for decades. And now with “AI” to make it more ridiculous. I look forward to retiring soon and never looking at code again.
lol But in theory, AI should be able to write directly in assembler. The 'stacks' would be merely layers of understanding in the AI, and it should be able to compress these down to tight assembly code that does the thing required, rather than using actual software layers. In theory.