- 92comments
- 38comments
- 154comments
- 466comments
- 42comments
- 225comments
- 125comments
- 33comments
- 12comments
- 304comments
- 15comments
- 123comments
- 162comments
- —discuss
- 68comments
- 272comments
- 19comments
- 34comments
- —discuss
- 143comments
- 342comments
- 40comments
- 253comments
- 61comments
- 12comments
- 7comments
- 192comments
- 314comments
- 7comments
- 540comments
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.
It sounds like there could be something extremely interesting in this article, but the writing style is really off-putting.
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.
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".
I mean, the real takeaway is they’re using Prisma 5. That reached EOL years ago, we’re on Prisma 8 now
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.
And that's not slop, it's the real smoking load bearing foot gun.
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.