To clarify, I use AI agents, but I absolutely hate them submitting code in my editor. Chatting is fair enough and useful, but I need to turn off the auto-generating code part.
Here I am on my free-as-in-freedom operating system, making commits with my free DVCS tool in my free programmable text editor, building it with my free language toolchain, using my free terminal emulator/multiplexer with my free UNIX shell. VC backed tools like Warp and Zed that seek to innovate in this space are of zero interest to me as a developer.
I think just about literally anyone can go up to someone on the street, shoot them while they're defenseless and then get caught within 5 days.
Also, I can help you on your moral waffling: what he did was fundamentally wrong.
When I talk to people who actually run factories here, they say that manufacturing in the U.S. is fine. It's just highly, highly automated. You'll have a production line that takes in plastic and chips and solder, and spits out consumer electronics at the end, and there are maybe a couple dozen employees in the whole plant whose job is to babysit the line and fix any machine that goes awry. Their description is backed up by data: manufacturing output has been flat since roughly 2000 [1], but manufacturing employment has dropped by more than 50% [2].
The public discourse about why we want to bring manufacturing back to the U.S. has been split into two main points (and you'll see it in comments here):
1) We should bring back manufacturing jobs so that we can have good, middle-class wages for the large segment of the population that's currently in low-wage service jobs and about to be displaced by AI.
2) We should bring back manufactured goods so that if we go to war with China, we can still make all the things we need to wage that war.
If it's #2, that's fair enough, and every indicator is that we can do that, it'll just take time and capital and perhaps some entrepreneurship. But it won't fix #1. Just like all other manufacturing in America today, the lines will be highly automated and largely run by themself. And that's a good thing - if we go to war, we want highly productive, distributed factories because we'll need the people to actually fight the war itself. The jobs are not coming back. If you expect someone with a high-school degree to be able to own a home today, the solution is not to put them to work in a factory ("manufacturing engineer" is a skilled job today anyway, not unlike a computer programmer), but to automate building houses and get rid of zoning/permitting constraints so that there are actually enough houses for everybody.
Is this just a case where politicians tell voters what they want to hear so they can go do what they want to do anyway? "We're going to bring back good high-paying manufacturing jobs for everyone" is a lot more palatable message than "We're going to go to war so you can die."
And on top of it you retain the knowledge to build, assemble and maintain these robots. This is alone worth the effort.
The way our store worked, every PC was built to order - we had inexpensive cases with sharp edges, we had higher end ones as well. I assembled a TON of PCs over those two years. We had a PC configuration app the owner had built in QBasic - it was very much like pcpartpicker.com , with all the parts we had available.
We played with a bunch of hardware and were familiar with it, we'd walk customers through the decisions - the impact of increasing cache, the differences in video cards. I believed it at the time, and in retrospect, still believe that it was an awesome shop - I can remember, by policy, we would sell customers printers if they really wanted one, but always recommended they buy one at the big box shop down the street, as we couldn't match their pricing. I loved that job.