It'd be great if it were written as a postmortem, but seems like that's almost the only moment where a concrete hour is mentioned. Except for the screenshot footnote.
I tried to read this article but something about the writing style made me go cross eyed. That being said, it sounded like something I had heard before and lo and behold...
I'm not sure the real intention of this blogpost, but my takeaway is "someone who has no idea what is going on finds a problem <LLM OF CHOICE> left for them, like a little code land mine".
> "The uncomfortable part is that the fix already existed. Claude Code, Anthropic's command-line coding agent".
It sounds like there could be something extremely interesting in this article, but the writing style is really off-putting.
> "on staging first and then on production at 23:40"
Why does the reader need to know the exact minute-to-minute timeline?
That's how postmortems have been written for ages.
It'd be great if it were written as a postmortem, but seems like that's almost the only moment where a concrete hour is mentioned. Except for the screenshot footnote.
Completely AI written unfortunately
"The crash is the short story; the slowness is the one worth writing down."
The horror.
I'd rather read a "badly written" and to the point story, than a clone of the last 20 postmortem-ish/incredible discovery stories I've seen this week.
I tried to read this article but something about the writing style made me go cross eyed. That being said, it sounded like something I had heard before and lo and behold...
Literally raised 4 years ago: https://github.com/prisma/orm/discussions/15164
I'm not sure the real intention of this blogpost, but my takeaway is "someone who has no idea what is going on finds a problem <LLM OF CHOICE> left for them, like a little code land mine".
[dead]
[dead]
[flagged]
[flagged]