frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Open in hackernews

If you stop writing code, you also get worse at reviewing it

https://cekrem.github.io/posts/if-you-stop-writing-code-you-also-get-worse-at-reviewing-it/
48•theanonymousone•2h ago

Comments

jqpabc123•1h ago
In other words, AI creates a self degrading and ultimately defeating feedback loop.

It works to supplant/eliminate those who produce the quality data (aka well written code) it needs for training.

AI trained on AI slop can only get sloppier over time.

rootnod3•49m ago
A full on Ouroboros
jghn•1h ago
This must be why I keep getting told by people that it's better to offload the reviewing to the agents as well.
popkkksidhd•33m ago
I do wonder about this. I’ve landed on:

1. Anything that’s boring to write - aka I’m not learning, done it before, I can quickly review - I offload to agents. And still review entirely since it’s my reputation behind it, but I’ve found it to be relatively pain free to review.

2. Anything that I don’t know what it’s gonna look like, I do my normal planning but with a lot of agent review involved up front. At the end of this, I more or less know the code that’s gonna be written and thus don’t type it myself. I still do line by line review and spend a lot of time on things I don’t understand. It still feels like the same process (wrt understanding) when I had typed and then reviewed what I typed.

I still (from what I can tell) have the same mental model I did when I hand typed the code, even though for the most part I’m not. I am worried if I’m losing something, but so far it seems ok. It’s also certainly not a 10x speedup.

yusefnapora•9m ago
You're pretty much at the top of the "vibe bobsled" [1]. Unfortunately, your lack of 10x speedup will stand in contrast to those who have descended further down the slope.

Unless you have uncommonly clear-headed management, you will likely feel pressured to increase your speed, since it's so much easier to judge output volume and delivery speed than the ephemeral "quality" that you add by thorough review and understanding. Having already adopted the tooling, and especially having seen it successfully churn out the boring parts, it will become easier and easier to justify offloading the review of those parts. Then a few weeks later, some of the trickier parts become boring, and you rinse and repeat until your only remaining job function is to take the blame when the code nobody has read blows up.

Not saying this is inevitable, just incredibly common. So even if you are personally able to hold the line, you should expect to be increasingly surrounded by colleagues who have gone all in.

1: https://dustycloud.org/blog/faulty-towers-vibe-sickness-and-...

boramdd•1h ago
This just reminds me a quote from Filippo di Strata, a scribe in 15th century.

"The pen is a virgin; the printing press is a whore."

bemtevi•36m ago
That's obvious. People claim they understand every line of code their agents write, but there's understanding...and then there's understanding. A cursory idea of how code works does not mean the same deep understanding of the solution nor does it give the feeling of the 'lightbulb' when a thorny problem is solved.

For a long time in coding, we've constantly been piling on technical debt, even before AI. With frameworks, layers, etc. But AI is a quantum leap that makes the problem far worse.

Note that compilers that go from C to assembly/machine code are a lot different because C for instance (or Rust, Python), etc. still exposes all of the core abstracted logic. AI does not. It hides the logic.

In the future, no one is going to understand much of anything except a few who will command vast AI infrastructures that will just attack each other, because the attack surface will just have multiplied to a point that bringing other people down is far more lucrative than doing anything else.

It's all so obvious and yet we continue on.... a sad state of affairs for programming. AI is a bad thing indeed....

deltarholamda•7m ago
People now may be able to understand it. I'm very concerned about the future programmers who are 10, 15 years old now. If you have never built by hand, how are you going to understand the code emitted from an LLM, or whatever New Thing we come up with in 10 years?

Back in the 90s, places that hired 3D modelers/animators would say something like "Look, we don't care if you know the program. We can teach you that. What we want to know is can you draw?" There's a base level understanding required for any higher-level endeavor. I would not expect a person who might even be considered an expert Python programmer to immediately be ready to become a core maintainer for the kernel. If you don't do the low-level stuff, early and often, you won't recognize the foot-gun when you see it.

Maybe the LLMs will get so good that isn't a problem? Okay, sure, possibly. If it gets to that point before all the greybeards retire or die, then it's possible we can dodge what I see is a negative feedback loop. If not, then I think the future is much less rosy.

bluGill•9m ago
There are plenty of coaches that are not great at the game they play. Some of them never were even good. The ability to tell someone how to do something is not the same as being able to do it.

Reviewing code and writing code a different skills. They are related, but they are very different.

snailcoder•7m ago
What about the code you were never able to write because you were time constrained? I have learned so much about the devops process through Claude and ansible playbooks and terraform that I would’ve never known was possible because of a lack of time. I do agree we can’t shut off our brains.

But a good bit of software dev was taking the time to go through documentation to understand specific syntax or what was possible with a certain type of tooling. I’m okay with automating the mundane and having much better software using the latest infrastructure and libraries. This all comes with tradeoffs, but I just don’t buy the “autopilot” argument. I’ve learned more in the past year than any year prior in technology. All this learning is now possible, because I’m not spending my time wiring a react front end to a backend for a simple table crud operation.

gosen•7m ago
Yes and no

If "writing code" is a craft then not writing it would result badly reading it, true. But I disagree that software engineering is a "writing code craft", it contains much more (designing system, architecture, testing, requirements and spec design, etc.) so all these things stayed with AI agents writing the code, and also software engineering craft expanded with new workflows and kinds of problems with AI. So getting worse at reviewing the code might be somewhat expected outcome in that change, we'll see over time

If you can't explain something in simple terms, you don't understand it (2017)

https://kottke.org/17/06/if-you-cant-explain-something-in-simple-terms-you-dont-understand-it
257•sammatilda•4h ago•149 comments

Frostbite: A new CPU architecture discovered, designed and verified by AI

https://architectlabs.com/blog/frostbite
342•shioyama•4h ago•222 comments

Anthropic employee claims general proof of the Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
32•iamronaldo•26m ago•4 comments

Show HN: I made an audio-to-MIDI model 60x more efficient

https://kobi.music/research/dettato
40•hidude562•3d ago•10 comments

Floppy3.5: A portable 3.5-inch floppy WiFi NAS

https://github.com/bigcrimping/floppy3.5
43•fortran77•1d ago•8 comments

Llms.txt and MCP didn't move the needle

https://backpackforlaravel.com/articles/opinions/llms-txt-and-mcp-didn-t-move-the-needle-for-us-h...
16•moebrowne•42m ago•4 comments

The Making of Oxygene

https://jeanmicheljarre.com/aaa/the-making-of-oxygene
95•hggh•4h ago•33 comments

Show HN: Fast deterministic natural language search for OpenStreetMap data

https://hippomaps.ch/?q=cafes+by+the+Limmat+100+m+from+the+lake+in+zurich#map=15.02/47.36708/8.54935
58•vihren•23h ago•23 comments

What people are building, discovered through new domains

https://startups.novumsignals.com/
89•walterschnitzel•4h ago•40 comments

Why the Airbus A321XLR often gets stuck climbing for first few hours of flight

https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/
46•edward•6d ago•26 comments

Signal Is Serious About Protecting Your Privacy

https://signal.org/blog/protecting-your-privacy/
67•dotcoma•5h ago•18 comments

OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-121481, CVSS 9.8)

https://github.com/openssl/openssl/pull/33652
320•JacobHenner•12h ago•262 comments

I can’t believe it’s 1!

https://aperiodical.com/2026/11/i-cant-believe-its-1/
26•ColinWright•3d ago•21 comments

Epic Games Turns to AI Coding for the Unreal Engine

https://spectrum.ieee.org/epic-games-unreal-engine-ai
23•rbanffy•2h ago•15 comments

Carnival Cruises emits ten times more sulphur oxide than all of Europe's cars (2019)

https://ecohustler.com/article/one-corporation-to-pollute-them-all/
285•sammatilda•5h ago•172 comments

Show HN: Tinnitus frequency finder and audio notch tool

https://trynotched.com/find
82•brianrhea•2d ago•48 comments

UK fridges secured from hackers

https://www.bbc.co.uk/news/articles/c6eq49zyx7p4o
95•tomnext•4h ago•85 comments

Global stock markets slump as Anthropic's record IPO fails to stem AI sell-off

https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell...
39•cdrnsf•1h ago•12 comments

FFmpeg 9.1 'Gauss'

https://ffmpeg.org/download.html#release_9.1
219•gyan•10h ago•30 comments

If you stop writing code, you also get worse at reviewing it

https://cekrem.github.io/posts/if-you-stop-writing-code-you-also-get-worse-at-reviewing-it/
51•theanonymousone•2h ago•11 comments

µ-Wire – USB on an ATtiny 10

https://cpldcpu.com/2014/03/19/%c2%b5-wire-usb-on-an-attiny-10/
77•mofosyne•2d ago•9 comments

The Strongest Sokoban Solver

https://healeycodes.com/introducing-the-worlds-strongest-sokoban-solver
102•ibobev•3d ago•23 comments

Postgres 19 Repack: Faster, Built-In Table Bloat Cleanup

https://www.snowflake.com/en/blog/engineering/postgres-19-repack-table-bloat/
142•craigkerstiens•11h ago•23 comments

Jujutsu Primer

https://ethanlowman.com/posts/jj-primer/
175•renehsz•8h ago•109 comments

How to CAD Almost Anything

https://ocw.mit.edu/courses/res-16-002-how-to-cad-almost-anything-january-iap-2024/
323•o4c•3d ago•109 comments

"I can tell you wrote this yourself"

https://em-online.bearblog.dev/i-can-tell-you-wrote-this-yourself/
304•BrunoBernardino•7h ago•292 comments

PostgreSQL 19

https://www.postgresql.org/docs/release/19.0/
295•linzhangrun•10h ago•15 comments

Vint Cerf on why TCP/IP was never patented

https://seremot.com/p/vint-cerf-on-why-tcpip-was-never
134•emot•13h ago•64 comments

What Comes After AGI?

https://institute.deepmind.com/essays/what-comes-after-agi/
111•jdkee•11h ago•219 comments

Show HN: Radiotherapy Delivery Demo

https://tps.neuralrad.com
13•coolwulf•5d ago•3 comments