4 ms·
> I spent around $400 on o3 last month because I was banging my head against a wall with some really tricky code. When I hit truly difficult problems, throwing
by prepend 1y ago
> I spent around $400 on o3 last month because I was banging my head against a wall with some really tricky code. When I hit truly difficult problems, throwing o3 at them for a few hours beats getting stuck in debugging rabbit holes for days.
I wish I could get some examples of this. I remember asking seniors for help on problems and they could help in minutes what would take me hours. And, likewise, I’ve had people ask me for a minute of help to stop them being blocked for days.
It surprised me that people would block for days and I wonder what that looked like. Do they just stare at the screen, walk around, play candy crush?
I’m trying to figure out if the author is a junior, average, or senior programmer and what they get stuck on would be something that a good programmer learns how to debug around. So you can finally get a good ROI on being a good programmer by comparing the time to what an AI would cost.
- roxolotl 1y agoYea I’d love to know what these look like. I’ve been using Claude and Claude code a bit for things I’m too lazy to do myself but know it’ll be solid at, for example a parser for iso dates in Janet. I set a $10 budget in February and have used $4 of it. I genuinely don’t know how to use these tools to spend $20 a month but at the same time they've been very helpful. I similarly get confused about normal blocking. I genuinely don’t understand it. I get procrastination. I go for runs during work. But rarely is something genuinely so much that it’ll take hours of programming. Edit: of course some tasks take multiple days. But visible progress is almost always achieved on the scale of hours not days.