proomt

Search

Search posts, papers, and topics

All posts

Lobsters12 min readintermediate

There's no point at which turning your brain off will work

Summary

Dan Luu argues that turning off your brain and letting LLMs write code unchecked doesn’t work; while agents can help, they still need human oversight, especially on out‑of‑distribution problems, and cannot replace skilled engineers for most production work.

  • Assuming LLM output works without verification leads to broken software; human QA remains essential.
  • LLMs still struggle with out-of-distribution tasks (obscure languages, board games), requiring supervision.
  • "Meat proxy" loops can reduce some effort but rarely replace skilled engineers for high‑value work.
  • Over‑promising LLM productivity often stems from selective examples; real projects still need extensive iteration.

Engineers evaluating fully automated code generation need to understand LLM limitations to avoid costly failures.

6/10

Related reading

  1. Debugging in My First Language: A Bilingual Developer’s Accidental Discovery

    Switching the language you think and talk in (e.g., from English to your native Spanish) can reduce mental overhead when debugging complex architectural issues, especially when using LLMs like Codex. The author treats bilingualism as a cognitive tool, not a deficit, and recommends deliberately switching languages—or any mental mode—to break through tough problems.

    Atomic Objectatomicobject.com4 min
  2. How to Write with an LLM

    The post proposes a two‑rule workflow for using LLMs as copy‑editors rather than ghostwriters: never adopt a phrase the model suggests, and block its encouragement feedback. It then shows how to automate iterative copy‑editing with a small Python/HTMX/Tailwind app and a set of concrete prompts.

    Hacker News front pagesockpuppet.org6 minHN712401
  3. Should you read the code, is RAG dead, and did Skills kill MCP?

    The article debunks five common AI‑tool hot takes, arguing you still must read AI‑generated code, AI fluency matters in hiring, MCP and Skills serve different purposes, RAG remains useful, and needing fine‑tuning signals a messy codebase. It offers concrete rules for reviewing generated code and integrating AI components responsibly.

    GitHub Oldgithub.blog5 minHN3
  4. Everybody's Lost Their Minds

    The author argues that the AI hype wave is draining engineering resources without improving security, and that basic practices like inventory and automated patching are far more valuable. He warns that over‑reliance on AI‑generated code erodes understanding and makes debugging harder.

    Lobstersnetmeister.org6 minHN368338lobste.rs193