THE COLLECTION
Library
Everything you’ve found. Nothing you need to save twice.
8 articlesBrowse at your own pace.
n
Battling Impostor Syndrome
This essay explains impostor syndrome among software engineers: doubting your skills even with proof of success. The author suggests reframing thoughts, comparing yourself only to your past self, and writing down daily accomplishments. Techniques include mentoring both ways, asking co-workers questions, and noting what improved your mood during highs and lows.
notes.adamlearns.com9 minbeginnerUnread
c
How the Claude Code team does code review
This article describes the code review process of the Anthropic team behind Claude Code. Agents write most of the code, so machines do most of the reading and humans approve by risk tier. The tradeoff is less human review time, but mistakes still pass, so the team needs rollback, telemetry, and clear ownership.
claude.devAddy Osmani, Morgan Westlee Lunt, Qing WangOct 15, 202615 minintermediateRead1 answer
d
How to keep enjoying programming in a world of LLMs
A Haskell developer, worried about LLM-driven burnout and skill atrophy, argues against full vibe coding: you should keep writing code yourself while delegating planning, research, review cycles, and low-risk cleanup to agents. The tradeoff is accepting modest productivity gains (roughly 2x by his estimate) instead of boasting numbers, in exchange for retaining enjoyment, codebase ownership, accountability, and independence from token limits and frontier-model vendors.
discourse.haskell.orgturionSep 18, 202615 minintermediateUnread
n
When AI writes almost all code, what happens to software engineering?
Arguing that late-2025 model releases (Opus 4.5, GPT-5.2, Gemini 3) made AI-generated code good enough to supplant hand-coding, the author blends anecdotes from prominent engineers with predictions about the profession. Specialized coding skills and hand-writing code lose value, while testing, architecture, product thinking, and verification become the engineer's core role. Tradeoffs include faster shipping at the cost of quality and accountability, though the piece rests on anecdotes and largely assumes its central claim holds.
newsletter.pragmaticengineer.comGergely OroszJan 6, 202631 minintermediateRead
G
Marketing ops as code: Automating events from planning to follow-up on GitHub
A GitHub marketing lead automated event operations end-to-end by treating each event as a GitHub Issue: issue forms capture inputs, labels act as triggers, GitHub Actions stage the event, and Copilot 'skills' (Markdown runbooks) handle planning and post-event follow-up. She argues the pattern applies to any repetitive work touching tools with an API or CLI, weighing it against packaged marketing-automation platforms: regional variation favors custom pipelines with PR-based change management, though a silent cron failure shows monitoring is still required.
GitHub EngineeringTomoko TanakaSep 11, 202611 minintermediateUnread
G
Should you read the code, is RAG dead, and did Skills kill MCP?
The article pushes back on five common AI hot takes: that you can skip reading AI-generated code, that not using AI hurts hiring, that Skills killed MCP, that RAG is dead, and that needing fine-tuning signals bad code. It argues each is oversimplified—review depth should match actual risk, AI fluency is about judgment, MCP and Skills solve different problems, and RAG still grounds answers. It closes by urging readers to test ideas by building rather than debating.
GitHub EngineeringGPSSep 18, 20267 minintermediateUnread
D
There's no point at which turning your brain off will work
The author argues that 'brain-off' LLM use—having agents write code and just relaying failures back (being a 'meat proxy')—still produces poor-quality software, failing on out-of-distribution problems and overfitting to tests or metrics. Even if it eventually yields good software, it won't benefit the employee, since a company could run the LLM loop without them and lay them off. He contends the present is the worst time to disengage, as companies are eager to cut low-contribution roles.
Dan Luu15 minintermediateUnread
A
Astra for Coding: Why Are We Doing This Again?
The author ran a fully autonomous 'software factory' with GPT 6 Astra for 35 hours (~$1200, 79 commits, 75k lines of code) and got nothing usable. His core complaint is that the model's token-efficient 'codegolf' Python for tool calls leaks into committed code, producing unreadable and bizarre output, and that it won't stop on oversized tasks. He argues training rewards local metrics over human readability, and doubts these costlier models still fit day-to-day software engineering versus other use cases.
Armin RonacherSep 7, 202616 minadvancedUnread