bushido
Joined 16 years ago
Joined 16 years ago
But its refusal to work pattern is getting pretty obnoxious. Another one I ran into last week was it refused to start a developer session to do browser testing for a code base it was working on because signing in was suddenly against it's programming.
It listed all the conditions it needed for a sign in to be possible, agreed that my code base met all conditions, but refused to progress. I tried it in multiple fresh sessions with the same result.
They pretty much write the case for why open weights and open source models need to win. The amount of policing that Claude does is pretty problematic.
I'd written about this recently, but it won't even sign in during some browser tests on my local system for authentication which goes to my local system because it's built into its programming now. I literally can't use it on some long horizon work.
The reason I mentioned that here is it deems that as problematic behavior, and nothing I can give it will change its mind. I feel like with video game development, it is going to do something of the same.
However, looking at the other side, I think what this might do is add some barrier or consideration when a bailout is considered.
The last time we did large scale bailouts (TARP[0], in 2008), It was rushed through and ratified in around two weeks following the sudden collapse of Lehman.
Any measures we can take to ensure that we don't fall into a situation where there is only one choice is sensible.
[0] https://home.treasury.gov/data/troubled-assets-relief-progra...
I had an issue recently where I asked claude code to log into a developer user on Chrome on my local host for a system which is fully local and part of the code base the agent was developing and it refused to do it, like flat out refused, I did it on multiple sessions and I could not get Claude to budge on entering the credentials - it required me to manually sign in.
Would be amazing if they used that same level of training for their intake exercises.
I don't mind talking to machines. I do mind micromanaging them, and I ming micromanaging people as well, and I don't like being micromanaged.
I added that last bit because in the rare circumstance that I am constantly going back and forth with AI, I feel that I'm the one who's being micromanaged.
> Does this not result in some inherent level of mental/skill degradation though
Not in my experience. I get to try a lot more things without having to actively sit with it. In the past, I would assign it to a engineering team if it was practical for the company. If it was side projects, if it was really, really important, maybe I'd squeeze in some time on the weekends, but mostly I didn't have time for it.
Now, experiments really come down to do I have the personal or professional budget to do it. I do use a lot of the subscription still, so it's do my subscriptions have capacity. I try every harebrained idea that comes to mind.
I definitely feel I've developed more skills in the last 6 months, than I did in the 2-3 years before it.
YMMV
The way I tell this to people is "I have never worked less and I have never been more productive".
All of my effort goes into ensuring that agents work autonomously for days to weeks without me having to coddle them. This takes a lot of effort to ensure that my memories are pruned, my git logs are clean, that I've transferred my way of thinking to agents so that they can make autonomous decisions which are 60-80% aligned with what I would want.
And the reason I go with 60-80% is that's the level of alignment I expect to get from my product & engineering teams, in a given sprint/period. Like with them, I've accepted that I'm not the perfect solution and it's going to go through a few iterations before I shape it into what I want it to be.
If I had to constantly chat with my agents, I think I'd be burnt out too. because I find that it's an absolute drag talking to the machine.
edit: changed the last sentence, which was unintentionally judgey.
Think of all the times you or someone you know has been frustrated because their AI did not remember things from moments, days, weeks ago.
It is kinda scary that we're here already, I can see this being pretty problematic for seniors/public prone to getting scammed.
That is an awfully simplified view of BI. In my experience, most companies struggle to define what is important, what needs to be measured, and how those measurements should be used to improve business.
While businesses try to work these details out, they try getting their analysts to in the author's words print out good pictures. But the BI tools really exist to make it easy for analysts to navigate hairy internal situations.
Producing a picture or HTML more easily is not going to solve the decisioning problem. If anything it might make it worse.
In the end, it's going to cost a lot more than 50 cents a picture.
The Canadian provincial governments usually have a monopoly in running gambling services, and there is a strong case to be made that this is as much about ensuring that they keep making revenue from gambling as it is to reduce the ill effects of other gambling ads.
ex: https://www.canadiangamingbusiness.com/2026/10/22/new-brunsw...
Good mental model to have in our arsenal.
Credit worthiness of each mortgage wasn't the issue with mortgage-backed securities. It was that low value mortgage-backed securities were repackaged into a basket with a mix of securities and given a higher credit rating than what Subprime would have gotten on their own.
This repackaging is absolutely going to happen again with GPUs. If there are GPUs of different generations within the same security, it's already happened.