# Manager.dev What nobody tells you about Engineering Management. One practical idea every week from someone who's still doing the job with you. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Coding Agents Still Need Human Code Reviews DevFeed: [Why Coding Agents Still Need Human Code Reviews]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-09-15T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [AI-assisted coding](), [Code review](), [engineering-culture](), [Claude](), [Software Engineering]() Tags: [claude](), [code-review](), [code-reviews](), [coding-agents](), [software-engineering]() ### AI overview The article argues that coding-agent workflows still require human code reviews. It describes how making reviews optional caused them to drop sharply, allowing passable implementations to become templates that spread bugs, performance problems, race conditions, and confusion among agents. ### Source excerpt When my most experienced engineer got tired of our shitty code ## A switchback career move from engineering management to software engineering DevFeed: [A switchback career move from engineering management to software engineering]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-09-08T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Job](), [AI-assisted coding](), [Software](), [Tech Lead]() Tags: [agents](), [career](), [data](), [engineering-manager](), [experiment](), [software-engineer]() ### AI overview The author describes moving from engineering management back to software engineering after struggling to secure another Engineering Manager role. The article also discusses an experiment in which an engineering team worked more deliberately with coding agents and a tech lead. ### Source excerpt The perfect time for a switchback career move ## The Engineering Manager's role is under attack (again) DevFeed: [The Engineering Manager's role is under attack (again)]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-09-01T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Development](), [Artificial Intelligence](), [Large Language Model](), [Software](), [Meta]() Tags: [agents](), [ai](), [engineering-manager](), [llms](), [meta](), [organizational](), [processes](), [software]() ### AI overview A commentary on the erosion of the Engineering Manager role as companies flatten organizations and expect managers to manage larger teams while also shipping code. It argues that AI-related efficiency claims may reinforce a cycle of reduced management capacity and value. ### Source excerpt The erosion of the EM role ## When non-devs open PRs DevFeed: [When non-devs open PRs]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-08-25T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Pull Request](), [Development](), [Linear](), [Artificial Intelligence]() Tags: [ai](), [article](), [code](), [jira](), [linear](), [reviews](), [work]() ### AI overview An opinion article examines the challenges and potential benefits of allowing non-engineers, including product managers and designers, to open pull requests on a software codebase. It discusses review responsibility, boundaries, scaling concerns, and reduced communication cycles, while citing Linear usage data about non-engineer code contributions and AI feature use. ### Source excerpt What to watch out for when letting non-engineers open PRs on your codebase ## Extreme Programming remains relevant for building software teams in 2026 DevFeed: [Extreme Programming remains relevant for building software teams in 2026]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-08-18T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Programming](), [Development](), [Refactoring](), [Test-driven development](), [pair\_programming](), [Code review]() Tags: [code](), [code-quality](), [development](), [pair-programming](), [programming](), [redesign](), [tdd]() ### AI overview The author revisits Kent Beck's Extreme Programming after experiencing frustration with Scrum and the pressures facing modern engineering teams. The article argues that XP remains relevant because it combines five values, 14 principles, and numerous practices aimed at improving both software and team life, rather than reducing the methodology to TDD and pair programming alone. ### Source excerpt A method created 30 years ago is still your best guide for building software ## Engineering Managers' Involvement in Product Decisions DevFeed: [Engineering Managers' Involvement in Product Decisions]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-08-11T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Product Management](), [context](), [Claude](), [Claude Code]() Tags: [claude](), [claude-code](), [context](), [engineering](), [engineering-manager](), [product-management]() ### AI overview The article argues that engineering managers should participate more actively in product decisions and business discussions. It cites a survey of more than 950 engineering managers, finding that 45% of experienced managers were barely involved and only 16% were very involved in product decisions. ### Source excerpt Only 1 out of 6 EMs is involved in product decisions ## Why engineering managers lose hands-on coding time DevFeed: [Why engineering managers lose hands-on coding time]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-08-04T06:01:00Z Content type: article Language: en Sources: [Manager.dev]() Topics: [engineering-culture](), [Software Engineering](), [Development](), [AI-assisted coding]() Tags: [ai](), [coding-agents](), [engineering](), [engineering-manager](), [manager]() ### AI overview The article examines how engineering managers gradually lose hands-on coding time as meetings, coordination, and project responsibilities increase. It argues that this shift can become a habit and discusses the case for managers remaining connected to the codebase. ### Source excerpt Never prompted until today ## Hiring, parallelization, and code review practices for engineering teams DevFeed: [Hiring, parallelization, and code review practices for engineering teams]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-07-28T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Software Engineering](), [engineering-culture](), [sdlc](), [pull-requests](), [Job]() Tags: [code-review](), [engineering](), [hiring](), [sdlc](), [software-engineering]() ### AI overview This guest article discusses three practices the author says engineering teams should focus on: continuously improving hiring, learning to parallelize work effectively, and adapting code review workflows. It presents these ideas as based on the CTO's experience and observations of productive teams. ### Source excerpt Hiring, parallelization, and why they stopped reviewing most PRs ## Charting your team's knowledge & skills map DevFeed: [Charting your team's knowledge & skills map]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-07-21T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Graphs](), [GitHub](), [Pull Request](), [Claude](), [systems](), [Open Source]() Tags: [claude](), [collaboration](), [github](), [graph](), [process](), [scope](), [soft-skills]() ### AI overview An engineering manager describes using Unblocked's Social Graph Builder to visualize collaboration and codebase expertise from GitHub pull request history, then explains a spreadsheet-based method for mapping a team's product knowledge, technology skills, soft skills, and non-engineering skills. The article argues that expert knowledge is important for evaluating AI-assisted work with Claude and avoiding harmful implementations in unfamiliar domains. ### Source excerpt If you rebuilt your team again today, knowing what you know now, would it look the same? ## Explaining to business people why building software is still hard DevFeed: [Explaining to business people why building software is still hard]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-07-14T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Software Engineering](), [Development](), [Code](), [Large Language Model](), [Open Source]() Tags: [code](), [engineering](), [llms](), [open-source](), [software](), [software-engineering]() ### AI overview This opinion article explains why software projects can become unexpectedly difficult despite rapid early progress. Using a hackathon project built with Lovable as an example, it discusses bugs, slowness, infrastructure work, refactoring, and the gap between technical complexity and business expectations. ### Source excerpt Explaining to business people why building software is still hard ## The software engineering war DevFeed: [The software engineering war]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-07-07T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Software Engineering](), [Large Language Model](), [Code quality](), [Development]() Tags: [code](), [code-quality](), [engineering](), [llms](), [software-engineering]() ### AI overview The article discusses a recurring conflict in software teams between builders who prioritize rapid product delivery and keepers who prioritize well-built systems and code quality. It argues that the rise of LLMs has intensified this disagreement. ### Source excerpt Most of us picked a side and won't budge. Which one are you on? ## 7 reasons experienced EMs get stuck DevFeed: [7 reasons experienced EMs get stuck]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-06-30T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Job]() Tags: [career](), [engineering-manager](), [mistakes]() ### AI overview An experienced engineering manager reflects on career traps that can cause experienced EMs to stagnate, including confusing job titles or team size with impact. The article draws on the author's experience moving from a director role to an engineering manager role after a failed startup. ### Source excerpt The mistakes that stall a career, even when you see them coming. ## Building a code reviewer from your team's PR history DevFeed: [Building a code reviewer from your team's PR history]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-06-23T06:01:00Z Content type: tutorial Language: en Sources: [Manager.dev]() Topics: [Code review](), [Pull Request](), [Claude Code](), [Artificial Intelligence]() Tags: [ai](), [best-practices](), [claude-code](), [code](), [code-review](), [coding](), [how-to](), [open-source]() ### AI overview This tutorial explains how a team built an AI code reviewer from three years of pull-request comments. It describes starting with a generic pre-PR checklist and evolving it into a reviewer that reflects the team's conventions and individual engineering preferences, using a Claude Code skill. ### Source excerpt how to build a code review tool specific to your team ## How Claude Can Lead Software Engineers to Surrender Understanding DevFeed: [How Claude Can Lead Software Engineers to Surrender Understanding]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-06-16T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Claude](), [Artificial Intelligence](), [Pull Request](), [software-architecture]() Tags: [ai](), [architecture](), [claude](), [review](), [software]() ### AI overview This opinion article argues that software engineers can become overly reliant on Claude during planning, coding, and code review. It distinguishes cognitive offloading, where engineers delegate work while retaining responsibility, from cognitive surrender, where AI-generated output becomes their output without sufficient understanding or verification. ### Source excerpt When Claude drives you off the cliff ## The generalist EM's reading list DevFeed: [The generalist EM's reading list]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-06-09T06:01:00Z Content type: article Language: en Sources: [Manager.dev]() Topics: [Product Management](), [User experience (UX)](), [Framework]() Tags: [books](), [engineering](), [generalist](), [learning](), [product-management]() ### AI overview A reading list of seven books intended to help engineers and engineering managers learn the basics of adjacent technology professions, including product management, design, user research, customer experience, business, marketing, and growth. The excerpt discusses Competing Against Luck and The Design of Everyday Things. ### Source excerpt 7 books to easily catch up with non-engineering professions in tech (number 3 is a must read) ## Why Engineering Managers Need More Than AI Skills in a Chaotic Work Environment DevFeed: [Why Engineering Managers Need More Than AI Skills in a Chaotic Work Environment]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-06-02T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Development](), [tech jobs](), [Artificial Intelligence]() Tags: [ai](), [engineering](), [management](), [tech-jobs]() ### AI overview The article argues that engineering managers are facing faster organizational change, rising AI-driven expectations, increased competition, and layoffs. It says succeeding in this environment requires strong non-technical skills, especially setting realistic expectations and aligning the organization. ### Source excerpt More "AI skills" is not what you need right now ## Why software engineering teams should prioritize a sustainable pace over speed DevFeed: [Why software engineering teams should prioritize a sustainable pace over speed]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-05-05T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Software Engineering](), [Development](), [ai-coding](), [Claude](), [cursor]() Tags: [ai](), [ai-coding](), [architecture](), [engineering](), [software-engineering]() ### AI overview The article uses the idea of a negative split in distance running to argue that software engineering teams should begin at a sustainable pace instead of pursuing speed immediately. It warns that rushing can create technical debt and architectural shortcuts that eventually slow teams down. ### Source excerpt Engineering teams don't need to 'just go faster' - the technique behind the sub-2-hour marathon