But it seems trivially easy to run it against local models. Their onboarding guide offers that option, though I have no idea if it changes any functionality.

I also built a couple of harnesses, I wonder if I could swap this for Claude in those...

(Lots of interesting ideas in the blog post, but like all the AI developments these days, hard to be sure what's valuable without extensive experimentation.)

It's a lot easier to become a really successful company if you can keep your inventory costs down. Perhaps by investing in local law enforcement instead, to make sure no one looks too close at said inventory?

Donald Trump is famous for not paying even really cheap contractor bills, because he knew he could get away with it.

https://news.ycombinator.com/item?id=48302822

I'm totally not surprised, except that Trump's admin is actually catching and prosecuting these people.

I assume that means this is just the tip of the iceberg, and the grift is so predominant that they can't help but catch some people.

People, especially in remote jobs, benefit from being organized into groups intentionally, with distinct rituals that enable them to operate effectively while they get to know each other better. Another person needs to design and oversee all that.

While you can provide templates for that structure that allow oversight to scale so that one person can oversee larger groups, that tends to be more effective in non-remote, and more predictable, work environments. Modern software development is very little of that.

I don't have much in-person experience with middle management in contexts outside of software development, and I suspect there are some opportunities to use AI to bring engineers closer to customers.

So good for me.

But there's some really scary stuff in here happening to other people that I'm not even aware of.

Yes, lower classes have access to many more conveniences then they might have had in earlier decades, but they are working far more hours, and their expected lifespan has started decreasing.

MiMo is the best one I've used so far, but I haven't done anything interesting with the Claude 4.7 models. It seems conservative with generally good "instincts", getting things working quickly without too much complexity. I've also embedded it in several different projects so far, and it's been pretty easy and effective.

If we're going to stabilize the software industry, we need to have more discussions like this that identify what constraints apply. (We should have had those discussion before pushing AI out this widely, but that wouldn't have gotten anyone rich.)

I actually think that there's a world of software systems agents can change, but it's materially different from the one we have now, and has a different set of constraints that we've also mostly done a poor job identifying. So hopefully the discussion can help those of us on both sides. ;)

My plan was just upgraded to 38 BILLION tokens per month. That's at least 10X the tokens I've used in my entire agentic development so far.

I should probably downgrade my plan, but we'll see. :)

Though for myself, I like having time to think about ideas in between when I collaborate with folk on them, so I have a lot of optimism about the success of the experiment. :)

Take all that AI productivity and found a one-day work week company. One day of focused collaboration each week, let bots and brains chew on stuff in the interim.

If someone with $200,000 wants me specifically dead, I'm going to die, one way or another. This tech doesn't substantially change the likelihood of their success.

If they want to cause a mass casualty event, there are already much easier ways. Once we tackle some of those, we can start worrying about this.

Nov 2025 was also when most of us learned about the acting Chief Security Officer at DHS, whose name AND photo seem exactly like the calling card of someone who had these "keys to the kingdom". https://bsky.app/profile/andylevy.net/post/3m6ivhnthts2o

I want to believe...