I also owned every iPhone from the first through iPhone 7 and kept each as I replaced the old one. After a while, none were usable due to changes in cellphone tech. And I realized keeping LiO batteries around was a huge fire hazard...

I grew up in the 70's. About the only thing I would say is less fragile are cars. Today's cars are just better in so many ways but are unmaintainable by the average user.

And people throw out things instead of repairing them because they don't know how. But that's changing as self-repair movements have taught millions. For example, the Kitchen Aid mixer. The original, built by Hobart and acquired by KitchenAid was a tank. However it had a sacrificial gear and people said that was a flaw because they didn't understand the purpose of sheer pins or sacrificial gears. Now it's pretty well understood thanks to YouTubers like Mr. Mixer that repairing these is easy peezy.

When iPhones became common, my ex-wife would get upset when I wouldn't reply to a text message. Sometimes I was busy and missed the notification, or couldn't answer (like in a meeting, driving, etc). Or I knew that the message would be better answered in person.

The social expectations part is hard to overcome. Societal contracts, whether implicit or explicit are very hard to ignore.

IIRC the samples in this program were actual performances, so I'm curious how they captured all the variations...

There's really not much of a place for AI in my work. We're not cutting edge, we're just a large, safe business protected by a regulatory moat. We don't want to be on the cutting edge, since the bleeding is bad for profits and reputation. But the incentives our IT execs operate under is all about resume/credential building and moving on to bigger things. Our C level officers are not even slightly technical, so they defer to the CIO. Nothing new at all in this company, it's a story told a thousand times.

So I was just very curious how it would be to approach vibe coding as if I was my VP. You don't know what you don't know, right? And the ease at creating a simple app that would be beyond 99% of the people in my company gives way too much confidence. And with misplaced confidence comes poor decision-making.

I can see where someone who currently is an Excel jockey would benefit from some of this stuff. As long as they can compare and test the outputs. But the danger from false confidence has to be an institutional risk that's being ignored.

While I downplayed my job experience, I'm very in touch with developers and their workflows; the challenges they face. And I'm scared because they won't be making these decisions about LLM usage; their bosses, the guy who vibe coded a dumb app over the weekend will.

So I set out to build an app with CC just to see what it's like. I currently use Copilot (copilot.money) to track my expenditures, but I've become enamored with sankey diagrams. Copilot doesn't have this charting feature, so I've been manually exporting all my transactions and massaging them in the sankey format. It's a pain in the butt, error prone, and my python skills are just not good enough to create a conversion script. So I had CC do it. After a few minutes of back and forth, it was working fine. I didn't care about spaghetti code at all.

So next I thought, how about having it generate the sankey diagrams (instead of me using sankeymatic's website). 30 minutes later, it had a local website running that was doing what I had been manually doing for months.

Now I was hooked. I started asking it to build a native GUI version (for macOS) and it dutifully cranked out a version using pyobjC etc. After ironing out a few bugs it was usable in less than 30 min. Feature adds consumed all my tokens for the day and the next day I was brimming with changes. Burned through that days tokens as well and after 3 days (I'm on the el cheapo plan), I have an app that basically does what I want in a reasonable attractive, and accurate manner.

I have no desire to look at the code. The size is relatively small, and resource usage is small as well. But it solved this one niche problem that I never had the time or skill to solve.

Is this a good thing? Will I be downvoted to oblivion? I don't know. I'm very very concerned about the long term impact of LLMs on society, technology and science. But it's very interesting to see the other side of what people are claiming.

Lessons like the value of AWACs. Now we're down to 15 and the availability rate is like 50%. So 8 or so WORLDWIDE. Yeah, that's a good lesson. And we've cancelled its replacement after someone (probably Elon) whispered BS into Trump's ear about space based sensors.

I'm sure China is watching with a notepad out about all these lessons. Thucydides is rolling in his grave.

Just because things hung around didn't mean that Sun/Solaris/Java were long for this world. Linux/x86 was just too cheap compared to SPARC gear. Even if it wasn't as robust as the Sun gear, it just made too much sense especially if you didn't have any legacy baggage.