mgkimsal

I've taken a somewhat different approach, although more reliant on voice. Tied up a phone number to some agent/llm service, tied to some APIs on some of my own code, and I have a system that calls me regularly to let me brain dump. I can tell it what I need to get done, it can remind me of things I mentioned before, clear things that are no longer important or required, etc. The key for me is the incoming call - something that regularly pings me and lets me just... talk it out, then sorts it out for me - it's useful. There's probably folks already doing some of this with claude and whatnot, but this also gave me some ability to learn how the best way to fit some of these together. Or... at least a way - might not be the best way yet :)

lob.com iirc

Would have been nice to have a test demonstrating the fix.

That was Perl though, wasn't it? mod_perl more specifically, IIRC. That alone relegated to a small pool of users.

Maddening for a bit - I've got problems that Flash is better on, and some Luna is better on, but I generally don't know until one has wasted time/tokens. Then I switch to the other one and... it's often just... bam - done. Correctly. I can't find the patterns ahead of time to determine what model I should be using first. :/ That said, I've been alternating between both the last month or so and they've both been pretty good compared to earlier models.

I haven't looked in to this in ... decades, but I seem to remember stored procs executed measurably faster 20+ years ago. That was one reason a project I was on pushed them. And the benchmarks they showed... it wasn't unreasonable. But we have faster networks, more memory, ssd, etc - I'm unsure if speed is a big reason any more. IIRC cached execution plans was a big win back then, but may not be as a win today. I'm thinking about sybase and mssql from the late 90s when I was first getting in to this topic.

But... over the years, I've seen push to sprocs where the logic was never version controlled or subject to the same level of testing the regular app source code was. The DBA folks had total control and were treated as a separate class of engineer than mere 'app' engineers, which caused all sorts of problems...

leaning yes 0.72

Logo unit testing supports a mock turtle.

Or you got the epyx fast load cartridge and could hit 'run/stop-restore' keys together to automatically type LOAD "*",8,1 and ENTER

> But reading that headline is bittersweet: I was nine in 1982, I'm now 53. Where have all those years gone? Don't get me wrong, I had a great life (so far) and I'd replay it just the same but... It's still bittersweet to think about my mates and I learning to code on those 8-bit machines. And the games. So many games...

Yep. 10 here. A lot of the same feelings.

It was a good buy for folks who got in early to build software/games for it. Friend of family was building games in 1982/1983 and had some early clones of games out (pacman, centipede, frogger clones, etc) and... while there were a lot of early publishers, it was fairly cheap to do in the early days, and they made more than enough to justify the $595 price (multiple units, IIRC).

IIRC the monica team already did this between v1 and v2, so v2 to v3 as another rewrite would be the same move.

Expanded rights for some at the direct expense of others. That's not the same as simply expanding rights, unless you count other people being 'offended' in the same category as someone being physically assaulted or killed.

I'd go further and say chatgpt offering continuing service just with degraded model keeps me in their 'free web use' tier. I have API keys for coding stuff, but for most of my day to day use of public llm, I know I won't get 'blocked' using ChatGPT. Yes, the model may change, and I'll get 'worse' output, but usually I can't tell the difference. Using Claude for day to day stuff, I get completely locked out after so many hours. Again, I have API keys for Claude as well, and use it for 'pro' work, but day to day chat stuff... it's not my daily driver.