We got past the bump, and I’m getting stuff done. I write this stuff because I will probably forget most of the frustration. Frontier is a hard piece of software to get going, it’s got a lot of integrations, which you want when you’re using, but hard when you’re getting it all to work the first time. And this port is very much like getting it work that way. But Claude does some things poorly and others spectacularly. It can play the role of a CPU and run the code and tell you where it will fail. Helpful when you don;t have a working debugger to step through the code and see exactly how and why it failed where it did. Before debuggers it was either all or nothing. #

Today’s song: So into you. #

Every day with Claude I end up debugging the things it broke overnight. Yesterday I actually got a useful script written and debugged, along the way reporting glitches but no deal-stoppers. This morning, after updating to the latest version, the script doesn’t run. It’s been like this for two weeks. No wonder every day before starting work I think of ditching this project and do whatever, but I don’t think I could ever muster the determination to get Frontier working on modern systems. And I can’t give up. But if you think this system can replace programmers, you are sorely mistaken. It can’t even do the job of a programmer fielding good bug reports and verifying that they fixed the problem and didn’t break anything else. Breakage happens, but this is something it does every freaking day. And then it admits that it didn’t do the other half of what it knew it had to do. I say it every day, this is ridiculous and I am fed up, and that’s just the beginning of the frustration. What keeps me coming back is when I can build up a head of steam in Frontier on my new Mac laptop. #