The Beefy 5 Layer Burrito used to be under $1. Yes, that was like 15 years ago, but we're still talking like a 300% increase. Even the regular bean burrito has doubled in price!
To some extent, but people still need to ultimately decide what to build, if it's being built correctly, etc. The accumulation of crappy code / slop is an issue, but it's going to improve. We're just getting started in all this, people are figuring things out.
AI will maintain the features, unless you think we're going back to the old days? The job of a developer will become 1) writing and refining specs, 2) "managing" agents by answering questions, evaluating new models, new tools, etc, 3) testing and validating AI output.
Yes, I miss those days. The late 80's through mid 90's was the golden age of BBSing. The transition from BBSes to ISPs was fun, but I still miss the community aspect of BBSes.
I hesitate to make blanket statements, since this is quickly evolving, but in general I agree. LLM generated docs will quickly degrade to overly verbose, unreadable crap.
On the other hand, imagine going back in time to 1985 and telling people that one day AAPL would have over 10x the profit and 20x the market cap of IBM.
Same. I taught myself C when I was in high school, back in the early 90's. Fortunately, in college, I was able to test out of the intro classes for credit.
You're absolutely right, and that is a fair critique! You have discovered a load-bearing gap, full stop.
In all seriousness, many people here, including myself, regularly receive 5 to 10 page long AI generated "documentation" where it is clear the "author" never made it past the first paragraph.
Abundance? Yes. Quality? No. I generated over 10,000 lines yesterday because "someone wants the whole thing done in a week." I did look at some of it. Real fast.
I think it was May for me for MacOS 26. I immediately updated to 27. Despite the various bugs, it is still a solid improvement. iOS 27 was also provided huge performance boost to my 5 year old phone!
It probably would've been merged if it had a smaller blast radius. It had "fixed" (actually broken) many unrelated tests in the process of making a small update.
Cool! I never knew anyone who did a 68010 upgrade back in the day.
I also had a 30 meg hard drive on my A500 (Supra, which included the RAM expansion.) It was a pretty decent Amiga setup. I taught myself C on that machine (Lattice / SAS C)
I had it look at some 30+ year old C code I wrote in college and it triggered some sort of guard rail. I mean, the code was bad and full of buffer overflows, but I already knew that.
I've seen similar. They wasted weeks of senior engineering time, between reviews, meetings, and follow up in Slack, only to have the PR closed without merge. The offending individual was eventually moved to another project.
I'm curious, how did the hardware present itself? It couldn't have been an Amiga Zorro card since it would've been impossible to get that into a PC. Did it connect over a serial or parallel port?
I never knew anyone who used the ECS "productivity" modes. That would've required an expensive multisync monitor since other Amiga stuff would still need the 15 kHz support. The only useful feature of ECS, as far as I can recall, was support for additional chip RAM.
I would expect something truly intelligent to be able to communicate well, if nothing else. That means knowing your audience, using plain language where it makes sense. Also, it yaps on and on, babbles endlessly when it a human would likely express something in a much shorter concise way. This is especially obvious when you generate project READMEs or technical docs. I find them borderline unreadable.
It smells of corporate speak, a total nonsense phrase. Even by your own admission, it is essentially meaningless. If I release a model an hour late, I'm "pacing the frontier."