frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Small Programming Tricks

https://will-keleher.com/posts/small-programming-tricks-matter/
154•signa11•2h ago•90 comments

Dream-RSI: Recursive Self-Improvement through Evolving Worlds

https://arxiv.org/abs/2609.14858
122•bananaflag•4h ago•38 comments

Mistral X Mozilla: Private, Multilingual AI Browsing

https://mistral.ai/news/mistral-x-mozilla/
416•vertigoruntime•10h ago•152 comments

Introducing System One Models and Jev

https://typesafe.ai/blog/introducing-system-one-models-and-jev
1747•albelfio•23h ago•466 comments

The DeepMind Institute

https://institute.deepmind.com/
51•vertigoruntime•3h ago•11 comments

Tell the speakers that you liked their talks

https://ohhelloana.blog/tell-the-speakers/
154•whisper2020•1d ago•41 comments

Claude Cowork and chat are now one Claude

https://claude.com/blog/cowork-is-now-claude
101•vertigoruntime•2h ago•118 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
1909•arnemunthekaas•1d ago•225 comments

ER visits for gambling disorders doubled after expanded online gambling market

https://temertymedicine.utoronto.ca/news/emergency-room-visits-gambling-disorders-nearly-doubled-...
34•geox•1h ago•25 comments

How big are factorials?

https://eli.thegreenplace.net/2026/how-big-are-factorials/
49•ibobev•1d ago•15 comments

Apple Reference Image: A New Approach for Verified Photography

https://security.apple.com/blog/apple-reference-image/
461•imwally•16h ago•303 comments

Learning Programming in an Age of LLMs

https://blog.ploeh.dk/2026/09/16/on-learning-programming-in-an-age-of-llms/
175•moneroloop2018•9h ago•123 comments

The Siberian Ice Maiden and the Scythian World

https://patrickwyman.substack.com/p/the-siberian-ice-maiden-and-the-scythian
10•NaOH•23h ago•0 comments

Hackers Got Inside a Flock Camera

https://www.wired.com/story/hackers-flock-camera-data-shows-how-system-works/
322•driverdan•5h ago•159 comments

Can we stop with the uptime percentages?

https://blog.jim-nielsen.com/2026/stop-with-the-uptime-percentage/
82•surprisetalk•2h ago•66 comments

The Google Play app review process now regularly takes longer than a week

https://gultsch.social/@daniel/117280438824908947
286•inputmice•7h ago•271 comments

Show HN: How Stale Is Your AI? Release age and training cutoff for 20 models

https://stale.jock.pl/
43•joozio•5h ago•32 comments

Salesforce Global Outage

https://status.salesforce.com/products/all
239•mabil•7h ago•141 comments

Kyber (YC W23) Is Hiring a Forward Deployed Engineer

https://www.ycombinator.com/companies/kyber/jobs/eturrAR-forward-deployed-engineer
1•asontha•6h ago

An update on Wayback Machine access

https://blog.archive.org/2026/09/15/an-update-on-wayback-machine-access/
658•ChrisArchitect•1d ago•342 comments

This Code Is CRAP (2011)

https://testing.googleblog.com/2011/02/this-code-is-crap.html
59•luispa•2h ago•40 comments

Anecdotally, Programmers Dislike "Reduce"

https://evanhahn.com/posts/2026-09-13-programmers-dislike-reduce/
19•praptak•2d ago•17 comments

A warning about 'model welfare'

https://mustafa-suleyman.ai/a-warning-about-model-welfare
96•andsoitis•4h ago•251 comments

Scaling Golang CI by Replacing actions/setup-go

https://www.cloudx.ai/posts/setup-go
54•peterldowns•5h ago•12 comments

Original Sony PlayStation 2 security chip 'broken wide open' after 26 years

https://www.tomshardware.com/video-games/playstation/26-year-old-sony-ps2-security-chip-broken-wi...
212•rbanffy•6h ago•61 comments

Anatomy of a Texture

https://agentlien.github.io/texture/
32•Agentlien•4h ago•7 comments

Show HN: I made a flight simulator, except you're just a passenger

https://inflightsimulator.com
358•rkotcher•2d ago•192 comments

Gemini 3.8 Live and 3.8 Live Extended Thinking

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-8-live-gemini-3-...
477•leumon•1d ago•314 comments

Measuring Gauss-Seidel loop-carried dependency and fixing it via loop unrolling

https://loiseaujc.github.io/posts/blog-title/make_gauss_seidel_great_again.html
22•loiseaujc•1d ago•7 comments

Why I'm still bearish on LLMs after Navier-Stokes

https://dank.systems/posts/2026-09-15-ai-bear.html
412•jaykru•1d ago•539 comments
Open in hackernews

Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)

https://blog.simbastack.com/four-round-trips-six-months/
8•asenna•1d ago

Comments

OG_BME•55m ago
Completely AI written unfortunately
tecleandor•36m 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.

ProjectBarks•55m 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•49m ago
That's how postmortems have been written for ages.
tecleandor•26m 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.
tonymillion•45m 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...

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".

wmadden•12m ago
I mean, the real takeaway is they’re using Prisma 5. That reached EOL years ago, we’re on Prisma 8 now
jihadjihad•27m 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.

smallnix•17m 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.

tecleandor•1m 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.