# 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.

## Invisible engineering teams

DevFeed: [Invisible engineering teams](<https://devfeed.tech/articles/invisible-engineering-teams-125627.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/invisible-engineering-teams>)

Author: Anton Zaides

Published: 2026-11-10T07:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [business](<https://devfeed.tech/tags/business.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [teams](<https://devfeed.tech/tags/teams.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

The author argues that low team visibility can cost engineers recognition and promotion opportunities and leave teams vulnerable to business changes, headcount cuts, or layoffs. Signs include receiving little credit but blame, accumulating operations work, difficulty advocating for promotions, and engineers feeling disconnected from the business. To improve visibility, the author recommends sending relevant updates through channels stakeholders actually use, tailoring detail to each audience; questioning whether the work would be missed if it stopped; and bringing stakeholders and concrete examples of the team's impact into team meetings. The piece draws on the author's experience managing teams with different visibility levels and presents these as practical approaches, not guaranteed outcomes.

### Source excerpt

Dealing with the left side of the visibility spectrum

## Welcome to the Neutral Zone

DevFeed: [Welcome to the Neutral Zone](<https://devfeed.tech/articles/welcome-to-the-neutral-zone-114144.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/welcome-to-the-neutral-zone>)

Author: Anton Zaides & Suzan Bond

Published: 2026-11-03T07:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [balancing technical and leadership roles](<https://devfeed.tech/topics/balancing-technical-and-leadership-roles.md>)

Tags: [accounting](<https://devfeed.tech/tags/accounting.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [career-development](<https://devfeed.tech/tags/career-development.md>), [careers](<https://devfeed.tech/tags/careers.md>), [change](<https://devfeed.tech/tags/change.md>), [coaching](<https://devfeed.tech/tags/coaching.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [context](<https://devfeed.tech/tags/context.md>), [death](<https://devfeed.tech/tags/death.md>), [demand](<https://devfeed.tech/tags/demand.md>), [economy](<https://devfeed.tech/tags/economy.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [faster](<https://devfeed.tech/tags/faster.md>), [feelings](<https://devfeed.tech/tags/feelings.md>), [identity](<https://devfeed.tech/tags/identity.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

Engineering managers and software engineers facing rapid role and job-market changes may experience a "neutral zone": the emotional work of reorienting after an old way of working ends, before a new one is clear. The article distinguishes situational change from the psychological transition needed to absorb it, and argues that uncertainty and identity questions are normal. It offers three ways to navigate this period: separate professional identity and personal worth, examine what kind of work you actually want, and allow time for confusion while continuing to move forward. It urges leaders to help people make sense of change, and individuals to seek peers rather than handle uncertainty alone. The author emphasizes that engineering's changes are ongoing and the future shape of engineering management remains unclear.

### Source excerpt

Dealing with the identity crisis in software engineering

## An Engineering Manager's crazy year

DevFeed: [An Engineering Manager's crazy year](<https://devfeed.tech/articles/an-engineering-manager-s-crazy-year-109112.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/an-engineering-manager-s-crazy-year>)

Author: Anton Zaides

Published: 2026-10-29T18:53:51Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [build vs buy components](<https://devfeed.tech/topics/build-vs-buy-components.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [code comments](<https://devfeed.tech/topics/code-comments.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2013](<https://devfeed.tech/tags/2013.md>), [2025](<https://devfeed.tech/tags/2025.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [actions](<https://devfeed.tech/tags/actions.md>), [addition](<https://devfeed.tech/tags/addition.md>), [admin](<https://devfeed.tech/tags/admin.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [advice](<https://devfeed.tech/tags/advice.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [manager](<https://devfeed.tech/tags/manager.md>), [my](<https://devfeed.tech/tags/my.md>), [team](<https://devfeed.tech/tags/team.md>), [times](<https://devfeed.tech/tags/times.md>), [works](<https://devfeed.tech/tags/works.md>)

### AI overview

An engineering manager recounts rebuilding a seven-engineer team's workflow while launching MyCo, an AI assistant for event businesses. After rapid vibe coding helped test ideas, optional reviews faded and the codebase accumulated bugs and copied weak patterns; the team responded with stronger repository guardrails and agent review support. Non-engineers also shipped production code, with mixed results and a large designer PR requiring a day of engineering cleanup. The team first chose HoneyBook's internal Python and Temporal AI-workflows for tools, durable pauses, evaluations, monitoring and security, but later estimated its cross-repository dependencies and deployment constraints made work 50-70% slower. They migrated roughly 500,000 lines into one repository using Vercel Eve, completing the migration with minor bugs. The author argues for repeatedly revisiting engineering processes as evidence changes, while acknowledging the team is still learning how to maintain quality and support engineers through the transition.

### Source excerpt

Rebuilding how my team works three times in 12 months

## More output, less progress?

DevFeed: [More output, less progress?](<https://devfeed.tech/articles/more-output-less-progress-105392.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/more-output-less-progress>)

Author: Anton Zaides & Francisco Trindade

Published: 2026-10-28T07:00:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [future of AI](<https://devfeed.tech/topics/future-of-ai.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [human centric design](<https://devfeed.tech/topics/human-centric-design.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [about](<https://devfeed.tech/tags/about.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [align](<https://devfeed.tech/tags/align.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [approach](<https://devfeed.tech/tags/approach.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [article](<https://devfeed.tech/tags/article.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [automation](<https://devfeed.tech/tags/automation.md>), [away](<https://devfeed.tech/tags/away.md>), [balance](<https://devfeed.tech/tags/balance.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [less](<https://devfeed.tech/tags/less.md>), [progress](<https://devfeed.tech/tags/progress.md>)

### AI overview

AI can multiply team output without improving progress when product, design, and engineering are misaligned. In one stuck project, a six-person discussion stalled amid competing opinions. The team mapped a timeline from documents, Slack, Jira, and code commits, revealing a month of planning followed by a month of coding and a sequential handoff process. Sharing that evidence shifted the discussion from blame to process and led to two changes: engineers could start before designs were final, since rework had become cheaper, and product, design, and engineering leads began finalizing requirements together. The next project moved more smoothly. The team also shortened technical documents and used architecture diagrams to support shared understanding. The author suggests reconstructing a recent project's timeline with an LLM, then fact-checking it with participants.

### Source excerpt

Real alignment is now our biggest challenge

## Your engineers deserve a REAL chance

DevFeed: [Your engineers deserve a REAL chance](<https://devfeed.tech/articles/your-engineers-deserve-a-real-chance-90818.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/your-engineers-deserve-a-real-chance>)

Author: Anton Zaides

Published: 2026-10-20T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [stack-internal](<https://devfeed.tech/topics/stack-internal.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [company](<https://devfeed.tech/tags/company.md>), [concrete](<https://devfeed.tech/tags/concrete.md>), [daily](<https://devfeed.tech/tags/daily.md>), [energy](<https://devfeed.tech/tags/energy.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [engineering-talent](<https://devfeed.tech/tags/engineering-talent.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [existing](<https://devfeed.tech/tags/existing.md>), [fake](<https://devfeed.tech/tags/fake.md>), [faster](<https://devfeed.tech/tags/faster.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [goals](<https://devfeed.tech/tags/goals.md>), [great](<https://devfeed.tech/tags/great.md>)

### AI overview

The author argues managers should help engineers adapt to AI coding tools instead of relying on vague warnings or immediate pressure to leave. They describe Weave as showing engineers and managers prompt quality, one-shot success, code quality, output, and tips drawn from an engineer's sessions, making feedback more concrete. Their proposed approach is to discuss strengths and struggles honestly, spend a couple of months recognizing and discussing work that goes well rather than constantly emphasizing shortcomings, and use a PIP if expectations still are not met. For a PIP to offer a real chance, the manager should believe improvement is possible, give clear feedback with examples, and remain available for support. Goals should reflect meaningful work rather than proxy counts; for slow adoption of new tools, the author suggests having the engineer lead a project with a clear timeframe and stage expectations. The source presents this as the author's experience and opinion.

### Source excerpt

A better approach to the rising expectations

## 5 things every EM must read/listen/watch

DevFeed: [5 things every EM must read/listen/watch](<https://devfeed.tech/articles/5-things-every-em-must-read-listen-watch-85920.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/5-things-every-em-must-read-listen-watch>)

Author: Anton Zaides

Published: 2026-10-13T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [rachels-ramblings](<https://devfeed.tech/topics/rachels-ramblings.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [culture](<https://devfeed.tech/tags/culture.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>)

### AI overview

A curated list of books, articles, newsletters, and podcast episodes for engineering managers, with recommendations on team culture, leadership, organizational dynamics, and AI-assisted engineering workflows. It also highlights an open-source visualization that maps collaboration and expertise across GitHub repositories.

### Source excerpt

The timeless shortlist

## What an engineering manager misses as coding shifts toward AI

DevFeed: [What an engineering manager misses as coding shifts toward AI](<https://devfeed.tech/articles/12-things-i-miss-since-coding-died-65444.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/12-things-i-miss-since-coding-died>)

Author: Anton Zaides

Published: 2026-10-06T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [devrig](<https://devfeed.tech/topics/devrig.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>)

### AI overview

An engineering manager reflects on 12 parts of hands-on software work that feel diminished as AI coding tools take on more implementation: debugging, code review, deep technical exploration, mentoring, shared problem-solving, and the satisfaction of building something difficult. The article argues that teams should acknowledge the loss and uncertainty engineers may feel during this transition, even as new opportunities emerge.

### Source excerpt

The satisfaction of debugging, rabbit holes, and 10 more

## How to answer "Just use AI and move faster"

DevFeed: [How to answer "Just use AI and move faster"](<https://devfeed.tech/articles/how-to-answer-just-use-ai-and-move-faster-61688.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/how-to-answer-just-use-ai-and-move-faster>)

Author: Anton Zaides

Published: 2026-09-29T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>)

Tags: [building-software](<https://devfeed.tech/tags/building-software.md>), [leader](<https://devfeed.tech/tags/leader.md>), [llms](<https://devfeed.tech/tags/llms.md>), [mentor](<https://devfeed.tech/tags/mentor.md>), [software](<https://devfeed.tech/tags/software.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

A software engineering manager explains how they respond when asked to use AI to move faster. The article discusses project trade-offs among scope, time, cost and quality, prioritizing work, and mentoring engineers in their use of AI with visibility into LLM sessions.

### Source excerpt

3 simple tips

## The 4 engineering management archetypes

DevFeed: [The 4 engineering management archetypes](<https://devfeed.tech/articles/the-4-engineering-management-archetypes-57868.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/the-4-engineering-management-archetypes>)

Author: Anton Zaides

Published: 2026-09-22T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [prompt](<https://devfeed.tech/topics/prompt.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Git](<https://devfeed.tech/topics/git.md>), [jira](<https://devfeed.tech/topics/jira.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [git](<https://devfeed.tech/tags/git.md>), [jira](<https://devfeed.tech/tags/jira.md>), [management](<https://devfeed.tech/tags/management.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [slack](<https://devfeed.tech/tags/slack.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

An article presents four engineering management archetypes based on what managers prioritize: protecting an exhausted team, supporting an individual customer, maintaining technical excellence, or pursuing company goals. It also offers a prompt for readers to identify their archetype from written conversations.

### Source excerpt

What would the sorting hat say about you?

## Why Coding Agents Still Need Human Code Reviews

DevFeed: [Why Coding Agents Still Need Human Code Reviews](<https://devfeed.tech/articles/the-broken-windows-theory-of-coding-agents-32329.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/the-broken-windows-theory-of-coding-agents>)

Author: Anton Zaides

Published: 2026-09-15T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [claude](<https://devfeed.tech/tags/claude.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### 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

## The broken windows theory of coding agents

DevFeed: [The broken windows theory of coding agents](<https://devfeed.tech/articles/the-broken-windows-theory-of-coding-agents-116566.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/the-broken-windows-theory-of-coding-agents>)

Author: Anton Zaides

Published: 2026-09-15T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-coding](<https://devfeed.tech/tags/ai-assisted-coding.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cleanup](<https://devfeed.tech/tags/cleanup.md>), [code](<https://devfeed.tech/tags/code.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [theory](<https://devfeed.tech/tags/theory.md>)

### AI overview

The author argues that coding agents accelerate the spread of weak code patterns: an unreviewed workaround can become a template for later agents, multiplying bugs, performance problems and confusion within days or months. In the team's shift to a greenfield product, code reviews fell from universal review by at least two people to about 2% while daily PRs rose from 4 to 28; the author says skipping review also reduced engineers' understanding of generated code. Manual review of every PR no longer seemed practical, while eliminating review created quality problems. The proposed interim approach is optional reviews that still cover roughly 5% of PRs, plus more review of agents' detailed plans. The author has not yet tested a plan review process and says no effective solution has emerged.

### 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](<https://devfeed.tech/articles/take-that-demotion-32328.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/take-that-demotion>)

Author: Anton Zaides

Published: 2026-09-08T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Job](<https://devfeed.tech/topics/job.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Software](<https://devfeed.tech/topics/software.md>), [Tech Lead](<https://devfeed.tech/topics/tech-lead.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [career](<https://devfeed.tech/tags/career.md>), [data](<https://devfeed.tech/tags/data.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>)

### 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

## Take that demotion

DevFeed: [Take that demotion](<https://devfeed.tech/articles/take-that-demotion-116564.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/take-that-demotion>)

Author: Anton Zaides

Published: 2026-09-08T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Learning](<https://devfeed.tech/topics/learning.md>), [Bootcamp](<https://devfeed.tech/topics/bootcamp.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2020](<https://devfeed.tech/tags/2020.md>), [2025](<https://devfeed.tech/tags/2025.md>), [3](<https://devfeed.tech/tags/3.md>), [after](<https://devfeed.tech/tags/after.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [apply](<https://devfeed.tech/tags/apply.md>), [art](<https://devfeed.tech/tags/art.md>), [attention](<https://devfeed.tech/tags/attention.md>), [basics](<https://devfeed.tech/tags/basics.md>), [behavioral-interviews](<https://devfeed.tech/tags/behavioral-interviews.md>), [better](<https://devfeed.tech/tags/better.md>), [book](<https://devfeed.tech/tags/book.md>), [career](<https://devfeed.tech/tags/career.md>), [take](<https://devfeed.tech/tags/take.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

The author argues that moving down a career level can be a useful "switchback," based on two personal moves from engineering management to individual-contributor work and later from director back to engineering manager. The first move provided time to learn the company's systems and build credibility; the author later became an EM and then a director. The second offered a chance to learn from directors and better understand other EMs' challenges, though the author says promotion is not yet appropriate. The excerpt argues that flatter organizations make same-level management jobs harder to find and that ex-managers may bring valuable experience even when rusty technically. It qualifies this advice: technical interviews still matter, advancement depends on internal openings, and a demotion usually means a pay cut. The opening also describes a team experiment in which engineers who iteratively improved coding-agent context, supported by a tech lead, reached 2.1 times average team productivity with no measured quality penalty; Weave was used to track process and output.

### 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)](<https://devfeed.tech/articles/the-engineering-manager-s-role-is-under-attack-again-32332.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/the-engineering-manager-s-role-is-under-attack-again>)

Author: Anton Zaides

Published: 2026-09-01T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Software](<https://devfeed.tech/topics/software.md>), [Meta](<https://devfeed.tech/topics/meta.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [llms](<https://devfeed.tech/tags/llms.md>), [meta](<https://devfeed.tech/tags/meta.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [processes](<https://devfeed.tech/tags/processes.md>), [software](<https://devfeed.tech/tags/software.md>)

### 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

## The Engineering Manager's role is under attack (again)

DevFeed: [The Engineering Manager's role is under attack (again)](<https://devfeed.tech/articles/the-engineering-manager-s-role-is-under-attack-again-116568.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/the-engineering-manager-s-role-is-under-attack-again>)

Author: Anton Zaides & Suzan Bond

Published: 2026-09-01T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [big-tech](<https://devfeed.tech/tags/big-tech.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [career](<https://devfeed.tech/tags/career.md>), [career-development](<https://devfeed.tech/tags/career-development.md>), [change](<https://devfeed.tech/tags/change.md>), [code](<https://devfeed.tech/tags/code.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [company](<https://devfeed.tech/tags/company.md>), [control](<https://devfeed.tech/tags/control.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [em](<https://devfeed.tech/tags/em.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [environment](<https://devfeed.tech/tags/environment.md>), [manager](<https://devfeed.tech/tags/manager.md>)

### AI overview

The article argues that widening engineering manager spans while expecting managers to ship code can erode their people-management work, making them seem less valuable and inviting further cuts. It points to Google's failed 2002 attempt to remove managers and later Project Oxygen findings, plus repeated flattening at Microsoft, as examples of companies reconsidering managers' contributions. The author says flattening can build relational debt over time: weaker trust and connection, more conflict, and less collaboration. Engineering managers are advised to document specific team problems, look for patterns, and connect them to business priorities so senior leaders can make decisions with grounded evidence. The article allows that simplifying reporting structures can help, while distinguishing that from assuming managers provide no value.

### Source excerpt

The erosion of the EM role

## When non-devs open PRs

DevFeed: [When non-devs open PRs](<https://devfeed.tech/articles/when-non-devs-open-prs-116571.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/when-non-devs-open-prs>)

Author: Anton Zaides

Published: 2026-08-25T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [balancing technical and leadership roles](<https://devfeed.tech/topics/balancing-technical-and-leadership-roles.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [5-questions](<https://devfeed.tech/tags/5-questions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [backend](<https://devfeed.tech/tags/backend.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [claude](<https://devfeed.tech/tags/claude.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [communication](<https://devfeed.tech/tags/communication.md>), [content](<https://devfeed.tech/tags/content.md>), [copy](<https://devfeed.tech/tags/copy.md>), [cpo](<https://devfeed.tech/tags/cpo.md>), [css](<https://devfeed.tech/tags/css.md>), [customer-success](<https://devfeed.tech/tags/customer-success.md>), [cycles](<https://devfeed.tech/tags/cycles.md>), [data](<https://devfeed.tech/tags/data.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [design](<https://devfeed.tech/tags/design.md>), [designer](<https://devfeed.tech/tags/designer.md>), [engineers](<https://devfeed.tech/tags/engineers.md>)

### AI overview

Non-engineers opening pull requests can shorten feedback cycles, free engineers from small UI changes, and give other teams more autonomy, but the author says the practice creates substantial review, mentoring, scope, on-call, and prioritization burdens. Their tentative approach pairs each contributor with an engineer, teaches basic PR and deployment workflows, and initially limits contributions to copy, logic-free UI, and prompt changes with evals. Scope is enforced manually; the team currently owns incidents, and the author has not settled a scalable review or prioritization system. The article presents these as early, low-volume experiments, not a proven playbook.

### Source excerpt

What to watch out for when letting non-engineers open PRs on your codebase

## When non-devs open PRs

DevFeed: [When non-devs open PRs](<https://devfeed.tech/articles/when-non-devs-open-prs-32338.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/when-non-devs-open-prs>)

Author: Anton Zaides

Published: 2026-08-25T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Linear](<https://devfeed.tech/topics/linear.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [article](<https://devfeed.tech/tags/article.md>), [code](<https://devfeed.tech/tags/code.md>), [jira](<https://devfeed.tech/tags/jira.md>), [linear](<https://devfeed.tech/tags/linear.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [work](<https://devfeed.tech/tags/work.md>)

### 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](<https://devfeed.tech/articles/extreme-programming-1999-2026-32325.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/extreme-programming-1999-2026>)

Author: Anton Zaides

Published: 2026-08-18T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Programming](<https://devfeed.tech/topics/programming.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Refactoring](<https://devfeed.tech/topics/refactoring.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [pair\_programming](<https://devfeed.tech/topics/pair-programming.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [development](<https://devfeed.tech/tags/development.md>), [pair-programming](<https://devfeed.tech/tags/pair-programming.md>), [programming](<https://devfeed.tech/tags/programming.md>), [redesign](<https://devfeed.tech/tags/redesign.md>), [tdd](<https://devfeed.tech/tags/tdd.md>)

### 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

## Extreme Programming 1999-\>2026

DevFeed: [Extreme Programming 1999-\>2026](<https://devfeed.tech/articles/extreme-programming-1999-2026-116561.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/extreme-programming-1999-2026>)

Author: Anton Zaides

Published: 2026-08-18T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [pair\_programming](<https://devfeed.tech/topics/pair-programming.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2021](<https://devfeed.tech/tags/2021.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [actions](<https://devfeed.tech/tags/actions.md>), [adjustment](<https://devfeed.tech/tags/adjustment.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-slop](<https://devfeed.tech/tags/ai-slop.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [best](<https://devfeed.tech/tags/best.md>), [building](<https://devfeed.tech/tags/building.md>), [building-software](<https://devfeed.tech/tags/building-software.md>), [created](<https://devfeed.tech/tags/created.md>), [guide](<https://devfeed.tech/tags/guide.md>), [programming](<https://devfeed.tech/tags/programming.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

The author argues that Extreme Programming remains useful for software teams working amid AI adoption, but its values, principles, and practices need to be applied with judgment. XP aims to improve both software and team life, connecting five values--communication, simplicity, feedback, courage, and respect--to practical methods through principles such as humanity, mutual benefit, and quality. The author highlights cross-functional teams, team continuity, sustainable work, and direct customer contact as especially relevant. They question applying pair programming or test-first programming universally, and argue that code and tests alone may not preserve necessary project knowledge. They also describe AI as making design easier while encouraging excessive scope, and warn that AI-written code and parallel work can strain quality, review capacity, and team well-being. The excerpt presents XP as a framework for evaluating practices, not a complete prescription for current AI-era work.

### Source excerpt

A method created 30 years ago is still your best guide for building software

## The 3 product battles 84% of EMs lose

DevFeed: [The 3 product battles 84% of EMs lose](<https://devfeed.tech/articles/the-3-product-battles-84-of-ems-lose-116558.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/business-oriented-em>)

Author: Anton Zaides

Published: 2026-08-11T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amplitude](<https://devfeed.tech/tags/amplitude.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customer-success](<https://devfeed.tech/tags/customer-success.md>), [customers](<https://devfeed.tech/tags/customers.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [empathy](<https://devfeed.tech/tags/empathy.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

The article argues engineering managers should join product decisions: only 16% of more than 950 surveyed EMs said they were very involved. It lays out three practical steps: track usage metrics after release to distinguish launching from adoption; review session recordings and customer discovery calls with the team; and speak directly with customers. A route planner built for about 200 drone pilots had only six users after an announcement, but more than 60 after personal outreach, illustrating why teams should check adoption. Customer conversations can reveal workflow friction and overlooked users. Suggested ways to arrange them include observing existing discovery calls, contacting users through support, and asking customer success or account managers to connect you with power users. The author recommends listening and asking how users solve a problem, how they use a flow, and what frustrates them.

### Source excerpt

Only 1 out of 6 EMs is involved in product decisions

## Engineering Managers' Involvement in Product Decisions

DevFeed: [Engineering Managers' Involvement in Product Decisions](<https://devfeed.tech/articles/the-3-product-battles-84-of-ems-lose-32322.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/business-oriented-em>)

Author: Anton Zaides

Published: 2026-08-11T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [context](<https://devfeed.tech/topics/context.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [context](<https://devfeed.tech/tags/context.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [product-management](<https://devfeed.tech/tags/product-management.md>)

### 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](<https://devfeed.tech/articles/the-death-and-revival-of-the-hands-on-engineering-manager-32330.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/the-death-and-revival-of-the-hands-on-engineering-manager>)

Author: Anton Zaides

Published: 2026-08-04T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [manager](<https://devfeed.tech/tags/manager.md>)

### 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

## The death and revival of the hands-on Engineering Manager

DevFeed: [The death and revival of the hands-on Engineering Manager](<https://devfeed.tech/articles/the-death-and-revival-of-the-hands-on-engineering-manager-116567.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/the-death-and-revival-of-the-hands-on-engineering-manager>)

Author: Anton Zaides

Published: 2026-08-04T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [article](<https://devfeed.tech/tags/article.md>), [attention](<https://devfeed.tech/tags/attention.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [best](<https://devfeed.tech/tags/best.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [death](<https://devfeed.tech/tags/death.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [manager](<https://devfeed.tech/tags/manager.md>)

### AI overview

The author argues that engineering managers need hands-on experience with AI-assisted software work to make sound technical and organizational decisions. As coding agents change engineering practice, managers relying only on second-hand accounts risk setting poor guidance and losing engineers' trust. The author describes the tradeoff: adding hands-on work to delivery, quality, people support, customer needs, and technical direction is unsustainable, and reducing one-to-one meetings to make room for coding already caused frustration and relational debt. The recommended starting point is modest: fix a small bug or UI issue, then free up a couple of weeks to deliver one real production feature end to end. The excerpt does not claim this resolves managers' competing responsibilities; it presents first-hand experience as a way to better understand the work and judge AI claims.

### Source excerpt

Never prompted until today

## 3 things top 1% teams do differently

DevFeed: [3 things top 1% teams do differently](<https://devfeed.tech/articles/3-things-top-1-teams-do-differently-116554.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/3-things-top-1-teams-do-differently>)

Author: Anton Zaides

Published: 2026-07-28T06:01:00Z

Content type: article

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [adapting](<https://devfeed.tech/tags/adapting.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-usage](<https://devfeed.tech/tags/ai-usage.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [coding-standards](<https://devfeed.tech/tags/coding-standards.md>), [context](<https://devfeed.tech/tags/context.md>), [context-management](<https://devfeed.tech/tags/context-management.md>), [cto](<https://devfeed.tech/tags/cto.md>), [hiring](<https://devfeed.tech/tags/hiring.md>)

### AI overview

The article argues that AI coding tools call for ongoing changes to hiring, work habits, and code review. The CTO describes revising interview stages in response to hiring failures, including checking early whether candidates understand startup tradeoffs; late-stage work trials are paid and last 3-5 days. For coding agents, engineers are encouraged to experiment with concurrent sessions and find a workable load, while improving the context and guidance given to each session when results go wrong. The team makes human code review optional: AI reviewers check standards and obvious bugs, while engineers review plans earlier for direction. About 5% of PRs receive another engineer's review, plan reviews are roughly ten times more common, and around 40% are not reviewed; sensitive infrastructure changes should still get expert human review. Testing every PR outside production remains a QA bottleneck, and the team hopes to automate parts of it.

### Source excerpt

Hiring, parallelization, and why they stopped reviewing most PRs

[Next page](<https://devfeed.tech/sources/manager-dev.md?cursor=WyIyMDI2LTA3LTI4VDA2OjAxOjAwKzAwOjAwIiwgImFhYjBjNTA3LTczY2ItNDZlZi1hZWYyLTE5ZGU2ZWRiZTIyMCJd>)