Ok - hear me out.

We get idk 1000 of us poors to buy some cheap land in the Midwest. Up in Appalachia.

We sell “Rapture Survival Communities”

They’re $999/month and you’ll get a hidden bungalow community complete with bunker. We’ll fill it with doctors and pastors and birthing women.

BUT YOU CANT KNOW THE LOCATION UNTIL THE RAPTURE HAPPENS. You don’t want any pesky liberals finding it and gaying up the place with their liberal demonic child sacrifice transness.

We will deliver coordinates via analog radio and Morse code once the rapture has started.

By business plan makes Sam Altman hard in his butt:

1. Collect money
2. Don’t build anything.
3. repeat

When they come screaming for proof and receipts and refunds… Just gaslight them and buy a politician.

What do you mean I shouldn’t give AI admin privileges on my or any other machine?

What do you mean we apes try to anthropomorphize(?) everything?

Let me help you:

AI does create a lot of slop - but at the same time, a lot of people don’t know what capabilities exist and what’s just marketing/hyperbole.

They read “AI will replace software engineers” and think that they can just talk to an AI and spit out working production level code.

Not saying that’s you. I don’t know your work.

1. It doesn’t know your machine unless it has local access. How will it know where you’re installing if it doesn’t know your directory tree?
2. it doesn’t know that it needs to import other modules or how separate functions need to interact. Not until you build it out and track what you’re doing and how the functions interact. It’s just documenting the work you do.
3. It defaults to basic framework from which to build - just like we would.

You don’t sit down and write 8,000 lines of code just one line after another. Shit - it could take me 3 days to figure WHERE to put 2 lines of code.

4. Claude web and Claude code can be split into dedicated projects or containers.

This allows specific contextual awareness. The more work you do in a project the more you can build off of it.

Organizing into context aware containers allows you to massively improve your code base because it actually accesses the code itself. Less guess - less slop. Not “no slop” just less.

It doesn’t replace everything, but recently I had Claude code evaluate ~43,000 lines of code. I verified its audits manually, and let it do its thing. I still had to make corrections on some assumptions it made but I fixed 110 critical bugs in an afternoon because of this system I’ve described.

If you’re expecting to say “build me x” it isn’t going to be successful.

Treat it like it’s a tool in the toolbox, not a replacement for good practices.

To your other note - the first time I tested Claude code I was blown away. Then the 2nd or 3rd time it took over… I felt like I lost my purpose. I need to be involved, not replaced.