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".
> I didn't. I gave Claude Code the guest's screenshot and asked whether the problem was ours or his phone's. It answered that in twenty minutes and, while verifying the deploy, noticed the ten-second floor and kept pulling: the logs by hour, the 47 ms TCP measurement, the pg_stat_statements query, the arithmetic.
If your brain, dear reader, is aneurysm-proof, by all means go ahead and read TFA.
You won't learn much, though, but then again neither did its author.
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?
And that's not slop, it's the real smoking load bearing foot gun.
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.
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".
> I didn't. I gave Claude Code the guest's screenshot and asked whether the problem was ours or his phone's. It answered that in twenty minutes and, while verifying the deploy, noticed the ten-second floor and kept pulling: the logs by hour, the 47 ms TCP measurement, the pg_stat_statements query, the arithmetic.
If your brain, dear reader, is aneurysm-proof, by all means go ahead and read TFA.
You won't learn much, though, but then again neither did its author.