How I use AI (Oct 2026)
- Author transition & usage: Ben Stolovitz reflects on how his AI usage shifted over a year, moving to a research engineer role at Salesforce AI Research, spending ~$3,000/month on model tokens.
- Personal AI policy: Emphasizes the need for personal boundaries and norms to avoid passive over-reliance, preserve human intent, and prevent mindless delegation of thinking.
- Agentic coding workflow:
- Declares raw code-writing essentially "solved" by orchestrating 5–6 parallel agents (e.g., Claude Code) running in isolated Git worktrees.
- Tasks delegated to agents include rapid feature prototyping, reproducing bugs, and drafting PRs.
- Limits of agentic engineering:
- Argues engineering is far from solved; autonomous agents still generate over-architected, unreadable "slop" without human guidance and taste.
- Highlights a major success: hand-writing a clean tool in a few hundred lines to replace 4,000 lines of messy vibe-code.
- Mental fatigue and loss of craft:
- Managing multiple concurrent agent chats causes significant context-switching fatigue and overstimulation compared to traditional programming.
- Notes the bittersweet decline of programming craftsmanship and the loss of the meditative joy found in hand-tuning code.
- Evolution of code reviews:
- Line-by-line syntax reviews are largely replaced by system-level architectural evaluations, automated linting rules, and prompt constraints in repository guidelines.
- Search and education:
- Generative summaries have become the default search interface, despite remaining mediocre for commercial product discovery.
- LLMs excel as deeply patient personal tutors, though effective learning still demands deliberate "Type 2" cognitive effort from the user.
Hacker News Discussion
- Cognitive dissonance on "coding is solved":
- Commenters highlight the contradiction between declaring coding obsolete while acknowledging that hand-written code dramatically outperformed generated code in maintainability and conciseness.
- The debate over developer "taste":
- Skeptics argue that genuine engineering taste and architectural judgment can only be cultivated by writing and debugging code manually over many years.
- Counterarguments suggest software taste is shaped more by high-level architectural exploration and exposure to different paradigms, which agents help accelerate.
- Genuine vs. perceived productivity:
- Multiple participants question whether massive agent productivity translates into better end products, noting that user-facing software quality has not visibly leaped forward.
- Others counter that rapid turnaround enables solo developers to build complex personal applications and POCs that were previously cost- or time-prohibitive.
- Technical debt and optimization:
- Debates emerge around whether strict code reviews and optimizations are obsolete if agents can easily refactor code on demand later.
- Critics warn that ignoring architecture and relying blindly on pass/fail automated tests will lead to brittle systems, useless test bloat, and subtle runtime failures.
- Training data degradation:
- Discussion touches on model collapse fears from recursive training on synthetic AI code, countered by claims that modern progress relies heavily on reinforcement learning (RL) and synthetic verification rather than raw web scrapes.