Rendered at 18:52:41 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
tecleandor 25 minutes ago [-]
To the author:
First of all, you still have the images problem (among others). Loading your home site takes around 60MB of downloads, including the autoloading 40MB MP4 file. Reduce resolution and compress. You don't need a phone to reproduce that, you just need to open your web browser development tools and reload the site to see how heavy is it. Also, the memory use calculation is off, but that's not important because probably an LLM did it.
Second, your API in karibukit.com is down
Don't rely that much in the LLM. Check things with your own eyes.
ProjectBarks 1 hours ago [-]
> "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?
Tostino 1 hours ago [-]
That's how postmortems have been written for ages.
tecleandor 50 minutes ago [-]
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.
OG_BME 1 hours ago [-]
Completely AI written unfortunately
tecleandor 59 minutes ago [-]
"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.
tonymillion 1 hours ago [-]
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".
wmadden 36 minutes ago [-]
I mean, the real takeaway is they’re using Prisma 5. That reached EOL years ago, we’re on Prisma 8 now
smallnix 40 minutes ago [-]
> The crash and the slowness turned out to be unrelated. The crash is the short story; the slowness is the one worth writing down.
And that's not slop, it's the real smoking load bearing foot gun.
jihadjihad 50 minutes ago [-]
> Who found it
> 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.
First of all, you still have the images problem (among others). Loading your home site takes around 60MB of downloads, including the autoloading 40MB MP4 file. Reduce resolution and compress. You don't need a phone to reproduce that, you just need to open your web browser development tools and reload the site to see how heavy is it. Also, the memory use calculation is off, but that's not important because probably an LLM did it.
Second, your API in karibukit.com is down
Don't rely that much in the LLM. Check things with your own eyes.
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?
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".
And that's not slop, it's the real smoking load bearing foot gun.
> 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.