Re:Postgres 19 is late, and it's AI's fault
by matsemann on Monday November 02, 2026 @06:23AM
(#50335458)
AI makes it possible to fix bugs and solves issue one wouldn't do before. But just because it's easier now doesn't mean it's automatically worth it. There are tradeoffs (like code complexity or breaking stuff), or it really just wasn't that important to fix if it was in the backlog forever. I've seen devs go down this rabbit hole, and perhaps overdo it. It feels productive, but at some point it might stop to provide value, and other things should've been prioritized. It's just easier to say to the AI "fix bugs" instead of solving real issues. At some point boasting about running 10x agents in parallel to fix bugs becomes a sign that there's a lack of value provided to boast about.
[ Parent
| on HN ]
Re:Postgres 19 is late, and it's AI's fault
by braiamp on Monday November 02, 2026 @06:39AM
(#50335555)
While that is true, there's also the other side of the coin: most bugs are hit, but never reported. Users are pretty unlikely to report bugs and when they do they are very vague about it. That's why client observability is such a boon for teams because they find what bugs users are actually hitting. If the agents are directed using that, then perfect
Re:Postgres 19 is late, and it's AI's fault
by BatteryMountain on Tuesday November 03, 2026 @06:34AM
(#50350706)
Not all 10 are doing bug fixes. Two of them are mobile apps, 5 of them are long-term feature work, 1 is infra/monitoring, the rest is adhoc stuff like bugs.