Ask HN: How to deal with shipping AI-written code you don't understand?

Hacker News Top News

Summary

A Hacker News discussion sparked by a Meta engineer's LinkedIn post questioning the growing practice of shipping AI-written code without fully understanding it, asking how developers cope with this new standard.

I saw this LinkedIn post from a Meta engineer and it resonated with me:<p><a href="https:&#x2F;&#x2F;www.linkedin.com&#x2F;posts&#x2F;ali-hamie_im-an-engineer-at-meta-and-i-never-felt-share-7517317918666211328-7C8N" rel="nofollow">https:&#x2F;&#x2F;www.linkedin.com&#x2F;posts&#x2F;ali-hamie_im-an-engineer-at-m...</a><p>&gt; I&#x27;m an engineer at Meta and I never felt this uncomfortable doing my job. I&#x27;m writing code these days and it all feels like a black box. This new standard of shipping with AI is moving so fast that if we&#x27;re going to spend our time checking each line of code, it&#x27;s going to take forever. That means you can end up with systems you&#x27;ve built where you don&#x27;t truly understand how all the code works. You understand the high level, but not every detail. And maybe this is becoming the new standard. It goes against every instinct of being a software engineer. I&#x27;m used to understanding what I&#x27;m building. Now I&#x27;m trying to figure out how much I need to understand before I&#x27;m comfortable moving forward. Are other engineers feeling this too?<p>How are you handling this?
Original Article

Similar Articles

Reviewing code requires reading

Lobsters Hottest

A developer blog post argues against the idea of shipping AI-generated code to production without reading it, emphasizing that code review serves critical purposes: diffusing responsibility, reducing bus factor, and maintaining team knowledge of the codebase.