Claude outage – Resolved
61–70 of 167 posts
Re: Claude outage – Resolved
#62Damn, I'll have to think for myself now...
Haha, I was more like: I have to think alone now. But I get the feeling, as someone who has always made a point of using only foss on my own machines (own the means of production so to say), this is a weird time. I don't like it, I hope soon local models get good. But in the mean time... We have this... dependency.
I can feel that my actual cognitive engineering skills are in decline. Does anyone else see this? To those of you who haven't hand written a PR in months, can you still write your own personal software as easily as you once could?
Re: Claude outage – Resolved
#63HN is not a claude uptime tracker!!
Re: Claude outage – Resolved
#64Re: Claude outage – Resolved
#65A nice chance to try sonnet again, must say, I'm not missing the load bearing assumptions, honest read of the permission matrix, what's genuinely a Django convention and what's a design choice, what's worth my thinking, and what's worth being precise about. Long story short, it seems to be faster and less vocal but not much dumber (it's just my thinking partner, so I read a lot of the output as I create a large data…
The verbosity of Opus 5 isn't even my issue, it's consistency. For every 10 tasks Opus 5 accomplishes, there's at least one task that Opus 5 does just an atrocious job of, or a debugging investigation that it just completely goes off the rails on.
Re: Claude outage – Resolved
#66A nice chance to try sonnet again, must say, I'm not missing the load bearing assumptions, honest read of the permission matrix, what's genuinely a Django convention and what's a design choice, what's worth my thinking, and what's worth being precise about. Long story short, it seems to be faster and less vocal but not much dumber (it's just my thinking partner, so I read a lot of the output as I create a large data…
I would never have predicted this a year ago.
I always scoffed about engineers not doing work during Github outages - I'd always find some kind of other engineering to do if PRs or builds were piling up.
But during model outages, and since I'm not actively set up to use OpenAI/Codex at the moment, I'll just find something else productive to do. I don't think I'm ever going to write code by hand again unless I'm fixing something the AI can't manage or the change is small enough. Why even try when the machine is 100x faster?
Should I give Codex another try? It's been a month or so since I last used it, and it always felt inferior at Rust and TypeScript.