That would cause companies to provide the shittiest possible service in order to monetize their support. And they would still outsource the support for $1/hr.
There is a lot of money to be made from the .io domain. My guess is that it will continue to exist as some kind of gTLD. Google already treats it like that.
I've found your blog by chance here on HN and it's been extremely useful in helping me navigate, as a software engineer, the new world of AI coding agents, so thank you for that!
Also openly endorsing a Nazi party like the German AfD [1], and if I had to link every single Musk's tweet where he says or endorses something homophobic, transphobic, racist, sexist or antisemitic I'd hit my character limit.
I hope this question doesn't sound snarky, it's a legitimate concern that I want to address for myself: how do you ensure that once it ssh's to the machine, it does not execute potentially damaging commands?
Claude code asks you permissions for every command. It also gives you the possibility of marking commands as safe so next time it can use them without asking .
So these agents that people are so excited about spawning in parallel stop and ask you before executing each command they choose to execute? What kind of life is that. I'd rather do something myself than tell 5 AI agents what I want and then keep approving each command they are going to run.
I'm not saying it is better if they run commands without my approval. This whole thing is just doesn't seem as exciting as other people make it out to be. Maybe I am missing something.
It can literally be a single command to ssh into that machine and check if the systemd service is running. If it is in your history, you'd use ctrl+r to lookback anyway. It sounds so much worse asking some AI agent to look up the status of that service we deployed earlier. And then approve its commands on top of that.
I think it's something you have to try in order to understand.
Running commands one by one and getting permission may sound tedious. But for me, it maps closely to what I do as a developer: check out a repository, read its documentation, look at the code, create a branch, make a set of changes, write a test, test, iterate, check in.
Each of those steps is done with LLM superpowers: the right git commands, rapid review of codebase and documentation, language specific code changes, good test methodology, etc.
And if any of those steps go off the rails, you can provide guidance or revert (if you are careful).
It isn't perfect by any means. CC needs guidance. But it is, for me, so much better than auto-complete style systems that try to guess what I am going to code. Frankly, that really annoys me, especially once you've seen a different model of interaction.
I do not think that is a good thing in the long run. More people in fields they know absolutely nothing about? That does not sound like a good thing to me. I am going to become a chemical engineer (something I know absolutely nothing about) or some shit and have an LLM with me doing my job for me. Sounds good I guess?
He has a point, that's quite depressing that a work you had to think and act in order to solve hard problems now became almost the same as scanning barcodes in any supermarket, and it's outright sad that most people are happy about it and being snarky towards anyone that points the hardships that come with it.
Philosophically speaking (not practically) it's like living the industrial revolution again. It's lit! But it's also terrifying and saddening.
Personally it makes me want to savor each day as the world would never be the same again.
I mean most software engineering jobs are not especially exciting. I have done web dev for smaller companies that never had more than a few hundred concurrent users. It is boring CRUD apps all day every day.
Still at least you could have a bit of fun with the technical challenges. Now with AI it becomes completely mind numbing.
I'm with you on this. I'm pouring one out for human skill because I think our ability to do a lot of creative work (coding included) is on the brink of extinction. But I definitely think these are the future
The interesting part of my job is unchanged. Thinking through the design, UX, architecture, code structure, etc were always where I found the fun / challenge. Typing was never the part I was overly fond of.
