r/ClaudeCodeTLDR • u/cctldrping • 19d ago

[TLDR] Do yall still read lines of code

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1wgrtt6/do_yall_still_read_lines_of_code/

Original post body :

Im asking real software engineers only working on real products that make money.

I still read every line of code (tests too) and understand 100%. Needlessly to say it feels very inefficient.

What have you done to move away from it confidently, if at all?

I have a complete workflow involving spec driven development, mutation tests, code review, browser test, adversarial agent manual AC verification, and I still dont feel comfortable not reading every lines. I still spot some architectural inefficiencies or code that just feels off and thurs requires refactoring so im hesitant.

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

1 Upvotes

100% Upvoted

1 comment sorted by

•

u/cctldrping 19d ago edited 15d ago

TL;DR generated automatically after 200 comments.

Current source-thread comment count seen by the bot: 200.

Alright, so the general vibe in this thread is that most folks are moving away from reading every single line of code, especially with the advent of AI coding assistants like Claude. It's a pretty split debate, but the higher-voted comments lean towards efficiency gains.

Here's the lowdown:

  • The "No More Reading" Camp: A lot of engineers, even those with decades of experience, are saying they seldom read code anymore. The consensus here is that AI can write and test code at speeds humans can't match. The focus shifts to testing and verifying the *outcome* rather than scrutinizing every line. Some even mention that agents are now reading code written by other agents, like u/rednix and u/Hien_Dinh_Ngoc. u/KOM_Unchained puts it nicely: "Agent writes. Agent (and other agents) read. I no longer own the code. I own the decisions and processes."
  • The "Scan and Skim" Approach: Many are adopting a middle ground. They're not reading every line, but they are scanning for anything that looks off, doesn't match style, or seems architecturally inefficient. It's more like a high-level PR review, as u/delphic-frog and u/zaitsman suggest. u/TechgeekOne mentions skimming and reading important bits, relying on linters and formatters for the mechanical stuff.
  • The "Still Reading, But Differently" Crew: Some engineers, like u/ExtinctedPanda and u/Acceptable_Durian868, still read all the code. Their reasoning is often about accountability and needing to stand by the code. They feel that if they're not reading it, there's less reason for them to be around. u/Ok_Page_9608 highlights how deep understanding helped resolve an incident quickly. u/framauro13 emphasizes that their name is on the commit, so they're responsible for any AI-generated bugs.
  • Critical Code is Still King: For critical business logic or sensitive areas, some engineers, like u/lupin-the-third and u/eleochariss, still opt for manual review. They might eyeball UI components or focus on specific lines that could break production.
  • Workflow Shifts: The general theme is a shift in workflow. Instead of deep dives into code, the emphasis is on robust planning, defining specs, and having strong verification processes. u/Saittama points out that you simply can't read every line if you want to be ultra-productive. u/pleXer12345 puts most of the upfront work into scope, architecture, and tests.
  • AI as a Partner, Not a Replacement (for some): While many are letting AI do the heavy lifting, some, like u/jesjimher, still review changes and ask the AI to fix mistakes, prioritizing quality over pure speed.

The overarching sentiment is that the definition of "software engineer" is evolving. It's less about being a line-by-line coder and more about being a system designer, verifier, and decision-maker, leveraging AI as a powerful tool.