So at some point you have to trust that the tech is safe. Both in terms of "robot won't go off the rails", but also in terms of hostile actors can't remotely take over your robot while you sleep.

In terms of sleeping, personally, I would like for the law to mandate that robots must have a physical off switch, in a very visible location, that physically disconnects power. The switch should be illuminated while in the ON position. What makes me a bit pessimistic there is that we don't even have laws to mandate webcam indicator lights (e.g. a very tiny red LED) must be ON in hardware.

In other words, can AI tech help? Probably, but I doubt it's going to be a major money maker, and it won't make a ton of money overnight. It's not like Claude Code where every programmer can begin using it instantly.

Not all of the memory usage is the fault of Bun/JS. Some of it is likely memory leaks (holding on to data it shouldn't). However, some of the blame does go to using JS. In Rust you can tightly pack your data if you want to, but in JS you can't have nested structs for example. Every object referencing another object is two separate chunks of memory, each with a header, and a pointer from one object to the other. GCs also use more memory. The overhead adds up.

Building a CLI program in JS is a bad choice, and nobody should be defending this decision. Especially since Claude Code is very much able to write Rust code, and they've shown it can port code. Just port Claude Code to Rust directly.

The issue is probably that many managers can't really tell the difference between a good programmer and a vibe-coder. The vibe coder ships a lot of PRs. Maybe they themselves ship some vibe-coded PRs. They hate the idea that programmers might know better than them.

I quit later, as it became increasingly clear to me that this guy knew nothing about technology, didn't care, but also had a fragile ego where he had to present himself to the company as being in charge, even though he was the worst person for the role. To top it all off, it also dawned on me over time that we basically had an absentee CEO who was working only ~15 hours a week at most. Then when I quit I found out there was a third co-founder who owned a huge stake of the company and I did not even know existed while I worked there.

When I first interviewed, the CTO seemed like a nice and friendly guy, I didn't immediately see red flags. This was my first startup experience. I'll try to research things better if I decide to join one again. I might also just not join unless I can myself be a co-founder. Fuck reporting to incompetent twats.

Currently taking a sabbatical. I decided to take the summer off. I'm working on personal projects. Lucky enough to have good savings from a previous job so I can afford to do this. I'm planning to take gradual steps towards returning to work near the end of the summer.

Then there's the fact that many of those datacenter are being built over what would otherwise be usable farmland. I'm sure many will say "it's not that much land", but then tech billionaires would like to build datacenters the size of Manhattan. What for? To train a bigger LLM? Yay?

Just yesterday, I was trying to use Claude Opus 4.7 to debug an issue in a program that I wrote, and its solution was to remove a feature, change the design to eliminate the problem without consulting me. I only found out that it had removed this feature through testing. Imagine not reviewing things like that. How can people argue for this with a straight face? We'll probably get there eventually, but there's no need to rush before the tech is ready. Doing that is just being clueless.