1. AI is useful but under‑hyped – it’s realistic, not magical
“The fact that it’s underwhelming compared to the hype we see every day is a very, very good sign that it’s practical.” – alterom
“Finally, a step‑by‑step guide for even the skeptics to try to see what spot the LLM tools have in their workflows, without hype or magic.” – alterom
2. Skill, experience and the “read‑code” bottleneck
“The bottleneck has gone from writing code to reading code.” – sksisksbbs
“You still have to read the code.” – tptacek
“I still have to review it.” – datsci_est_2015
3. Workflow engineering – break tasks, harness, iterate
“Break down sessions into separate clear, actionable tasks.” – mjr00
“Treat the agent as something that does narrow, reviewable diffs against a plan.” – EastLondonCoder
“The sweet spot has been moving upwards every 6‑8 weeks with the model release cycle.” – kcorbitt
4. Cost and accessibility concerns
“I’m paying $190 a month for this.” – JoshuaDavid
“I spend $1500‑$1600 a year on JetBrains AI, Claude, Codex, etc.” – latchkey
“How much does it cost per day to have all these agents running?” – i_love_retros
5. Trust, reliability and the need for verification
“I don’t trust AI to give me a recipe for potato soup.” – jplusequalt
“You still have to read the code.” – tptacek
“The agent can drift and produce buggy code; you must validate it.” – EastLondonCoder
These five themes capture the core of the discussion: AI is a realistic, but not revolutionary, tool that requires skilled users, careful workflow design, budget awareness, and rigorous verification to be truly valuable.