Hacker news

  • Top
  • New
  • Past
  • Ask
  • Show
  • Jobs

If you stop writing code, you also get worse at reviewing it (https://cekrem.github.io)

71 points by theanonymousone about 2 hours ago | 15 comments | View on ycombinator

snailcoder 32 minutes 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.

bemtevi about 1 hour 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....

gosen 32 minutes 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

bluGill 34 minutes 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.

jghn about 2 hours ago |

This must be why I keep getting told by people that it's better to offload the reviewing to the agents as well.

boramdd about 1 hour 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."

jqpabc123 about 2 hours 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.

arbor-group 8 minutes ago |

[flagged]