# engineering-leadership

Engineering leadership is the practice of leading software engineering teams and systems through people management, delivery coordination, technical decisions, architecture, reliability, and engineering standards.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## The leadership gap when technical specialists become executives

DevFeed: [The leadership gap when technical specialists become executives](<https://devfeed.tech/articles/the-leadership-gap-when-technical-specialists-become-executives-146155.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4250886/the-leadership-gap-when-technical-specialists-become-executives.html>)

Author: Shawn Jahromi

Published: 2026-11-20T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.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>), [Finance](<https://devfeed.tech/topics/finance.md>), [Tech Lead](<https://devfeed.tech/topics/tech-lead.md>)

Tags: [business](<https://devfeed.tech/tags/business.md>), [business-management](<https://devfeed.tech/tags/business-management.md>), [business-strategy](<https://devfeed.tech/tags/business-strategy.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [capability](<https://devfeed.tech/tags/capability.md>), [capital](<https://devfeed.tech/tags/capital.md>), [career](<https://devfeed.tech/tags/career.md>), [careers](<https://devfeed.tech/tags/careers.md>), [careers-it-leadership-roles](<https://devfeed.tech/tags/careers-it-leadership-roles.md>), [code](<https://devfeed.tech/tags/code.md>), [consulting](<https://devfeed.tech/tags/consulting.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [cto](<https://devfeed.tech/tags/cto.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [data](<https://devfeed.tech/tags/data.md>), [data-systems](<https://devfeed.tech/tags/data-systems.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [develop](<https://devfeed.tech/tags/develop.md>), [developers](<https://devfeed.tech/tags/developers.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [gap](<https://devfeed.tech/tags/gap.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [specialists](<https://devfeed.tech/tags/specialists.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

Technical expertise can prepare someone to lead a function without preparing them for executive decisions. The text recommends assessing candidates against the decisions they will inherit, including strategy, finance, people leadership, organizational design, and breadth across technical disciplines. Record each capability as demonstrated, supported, or untested with concrete examples, and have peers, finance partners, and reports challenge the assessment. Develop gaps through guided exposure to real investment proposals, forecasts, and people decisions before promotion. Executives need enough technical breadth to test assumptions and weigh trade-offs, not mastery of every specialty. Build complementary teams, clarify who recommends, advises, and decides, and make disagreement safe while retaining accountability. The cited research supports caution about inferring managerial readiness from current performance and an association between psychological safety and team learning; neither directly establishes readiness for CIO or CTO roles.

### Source excerpt

A successful technical career can prepare someone to lead a function without preparing them to lead everything that comes next. Executive work brings distinct disciplines into the foreground: strategy, interpersonal leadership, business management, consulting and financial judgment. Technical expertise remains valuable, but these capabilities do not emerge automatically from it. They need deliberate development before promotion, not an assumption that the new title will produce them. Consider a hypothetical programming lead who has spent 30 years writing code and guiding junior developers. That experience can produce excellent technical judgment and valuable mentoring skills. It does not, by itself, demonstrate an ability to choose a business strategy, allocate capital across functions or resolve competing organizational interests. The executive role is not simply the same programming job with more authority. It requires different kinds of judgment. There are two gaps to assess: executive capability and technical breadth. A cybersecurity specialist moving into a CTO role might inherit responsibility for software engineering, infrastructure, architecture and data systems, depending on the organization. Security expertise does not establish equal depth across those disciplines. The CTO does not need to master every specialty, but needs enough breadth to question specialists, recognize dependencies and make informed trade-offs across their recommendations. My experience leading enterprise programs across infrastructure, security and transformation is the starting point for how I think about this transition. I believe technical specialists deserve a path into executive leadership. That path should develop the capabilities the next role requires before handing over its authority. I would assess readiness against the decisions candidates will inherit, rather than the years of expertise that earned them consideration. Laurence J. Peter and Raymond Hull gave this risk a mem

## Adopting Embedded AI Through an Innovation Team

DevFeed: [Adopting Embedded AI Through an Innovation Team](<https://devfeed.tech/articles/adopting-embedded-ai-through-an-innovation-team-145784.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.25939>)

Author: Viktoria Stray, Kristina Kantima {\\O}stvold, Agnes Hunstad Birkemo, Nils Brede Mo

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [awareness](<https://devfeed.tech/tags/awareness.md>), [build](<https://devfeed.tech/tags/build.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [case](<https://devfeed.tech/tags/case.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [development](<https://devfeed.tech/tags/development.md>), [effectiveness](<https://devfeed.tech/tags/effectiveness.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [embedding](<https://devfeed.tech/tags/embedding.md>), [explore](<https://devfeed.tech/tags/explore.md>), [financial](<https://devfeed.tech/tags/financial.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [functional](<https://devfeed.tech/tags/functional.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

A qualitative case study in a large Norwegian financial organization found that a temporary, cross-functional innovation team could explore embedded AI solutions with structural separation, in-team AI competence, senior expertise, high autonomy within a clear mandate, and flexible working. Adoption still depended on coordination with the permanent product team that would own the solution; misaligned roadmaps, prioritization gaps, and lack of co-location constrained that handoff. Based on interviews, office and meeting observations, and internal documents, the authors identify seven success factors and propose expertise awareness as an alternative to redundancy in the Agile Team Effectiveness Model.

### Source excerpt

arXiv:2611.25939v1 Announce Type: new Abstract: Software organizations are increasingly embedding AI capabilities into products that existing teams already own and maintain, but how this development work should be organized is not well understood. We conducted a qualitative case study of a temporary cross-functional innovation team in a large Norwegian financial organization, drawing on 18 interviews with 15 participants, 10 days of office observation, observations of ten meetings, and internal documents. We found that structural separation, AI competence inside the team, high autonomy within a clear mandate, senior expertise, and flexible ways of working enabled the team to explore and build embedded AI solutions. While structural separation enabled this work, it also made adoption dependent on coordination with the permanent product team that would own the solution. Misaligned roadmaps, prioritization gaps, and a lack of co-location constrained that coordination. We identify seven success factors for adopting embedded AI through an innovation team and propose expertise awareness as an alternative to redundancy in the Agile Team Effectiveness Model.

## What AI-First Engineering Means for the Future of Software Quality

DevFeed: [What AI-First Engineering Means for the Future of Software Quality](<https://devfeed.tech/articles/what-ai-first-engineering-means-for-the-future-of-software-quality-145967.md>)

Original publisher: [Read original article](<https://testgrid.io/blog/ai-first-engineering/>)

Author: Ankita Nandi

Published: 2026-11-19T10:55:22Z

Content type: article

Language: en

Sources: [TestGrid](<https://devfeed.tech/sources/testgrid-blog.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [mutation-testing](<https://devfeed.tech/topics/mutation-testing.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-generated-tests](<https://devfeed.tech/tags/ai-generated-tests.md>), [ai-testing](<https://devfeed.tech/tags/ai-testing.md>), [ai-workflow](<https://devfeed.tech/tags/ai-workflow.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bank](<https://devfeed.tech/tags/bank.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [billing](<https://devfeed.tech/tags/billing.md>), [block](<https://devfeed.tech/tags/block.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [credit-card](<https://devfeed.tech/tags/credit-card.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [quality](<https://devfeed.tech/tags/quality.md>), [rules](<https://devfeed.tech/tags/rules.md>), [software](<https://devfeed.tech/tags/software.md>), [system](<https://devfeed.tech/tags/system.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

AI-first workflows can accelerate software delivery, but when an agent derives code, tests and documentation from the same incomplete requirement, they can all reinforce one mistaken assumption. The excerpt distinguishes tests that confirm behavior inferred from buggy code from tests that correctly enforce a flawed or underspecified business rule; either can leave a green build that fails users. It recommends agreeing on expected behavior and edge-case examples before implementation, having an accountable domain expert approve them, and generating business-rule tests from those approved expectations. Validate AI-generated tests by planting known bugs. For high-risk changes, add independent security review, hands-on human testing and sign-off. Use execution evidence such as video, screenshots, logs and network traffic to investigate failures, and measure customer bugs, pre-release risks and diagnosis time rather than test counts alone. The excerpt also calls for junior engineers to practice questioning requirements and explaining conclusions. Its example is hypothetical, and the overview reflects the supplied excerpt.

### Source excerpt

Let's say you oversee a bank's credit-card billing-error system. Your product team gives an AI agent a requirement: "Accept written billing-error notices within 60 days." The agent implements the rule, generates 40 tests, and reports that every test passes. But it has started the clock on the transaction date. Under US federal billing-error rules, the [...]

## How AI Is Changing the Way Companies Hire, Manage and Measure Performance

DevFeed: [How AI Is Changing the Way Companies Hire, Manage and Measure Performance](<https://devfeed.tech/articles/how-ai-is-changing-the-way-companies-hire-manage-and-measure-performance-141288.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-ai-is-changing-the-way-companies-hire-manage-and-measure-performance?source=rss>)

Author: Alex Lashkov

Published: 2026-11-18T17:51:24Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [ai-transformation](<https://devfeed.tech/tags/ai-transformation.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [cto](<https://devfeed.tech/tags/cto.md>), [future-of-work](<https://devfeed.tech/tags/future-of-work.md>), [hiring](<https://devfeed.tech/tags/hiring.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [manage](<https://devfeed.tech/tags/manage.md>), [management](<https://devfeed.tech/tags/management.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [organizational-culture](<https://devfeed.tech/tags/organizational-culture.md>), [performance](<https://devfeed.tech/tags/performance.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [team](<https://devfeed.tech/tags/team.md>), [team-productivity](<https://devfeed.tech/tags/team-productivity.md>)

### AI overview

Manychat raises the bar for opening roles because AI agents can automate more work; leaders first ask whether the work should exist or can be changed. The company evaluates productivity through agreed, measurable outcomes rather than AI usage, tokens, or other activity counts, and avoids targets employees cannot control. It treats AI adoption as employee-led, provides tools and training, and keeps people involved in sensitive areas. In customer support, an AI agent now handles the first line: ticket volume roughly doubled while the frontline team grew by about a third, and satisfaction rose from about 84% in early 2024 to about 90% through 2025. Kushnikov expects senior engineers to own results end to end with AI agents as partners, and managers to focus more on judgment, vision, and responsibility.

### Source excerpt

Manychat CTO and COO Dmitry Kushnikov explains how AI is reshaping hiring, team productivity, management, and performance measurement in growing companies.

## How to Structure AI Adoption Teams and Measure Software Delivery Improvements

DevFeed: [How to Structure AI Adoption Teams and Measure Software Delivery Improvements](<https://devfeed.tech/articles/how-to-structure-ai-adoption-teams-and-measure-software-delivery-improvements-140474.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-structure-ai-adoption-teams-and-measure-software-delivery-improvements?source=rss>)

Author: marian kamenistak

Published: 2026-11-18T06:30:02Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI Strategy](<https://devfeed.tech/topics/ai-strategy.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [software delivery metrics](<https://devfeed.tech/topics/software-delivery-metrics.md>), [dora metrics](<https://devfeed.tech/topics/dora-metrics.md>), [Developer Enablement](<https://devfeed.tech/topics/developer-enablement.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-adoption-metrics](<https://devfeed.tech/tags/ai-adoption-metrics.md>), [ai-at-work](<https://devfeed.tech/tags/ai-at-work.md>), [ai-change-management](<https://devfeed.tech/tags/ai-change-management.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [ai-platform-teams](<https://devfeed.tech/tags/ai-platform-teams.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [ai-transformation](<https://devfeed.tech/tags/ai-transformation.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [budget](<https://devfeed.tech/tags/budget.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [code](<https://devfeed.tech/tags/code.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [dora-metrics](<https://devfeed.tech/tags/dora-metrics.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [organizational-ai-adoption](<https://devfeed.tech/tags/organizational-ai-adoption.md>), [software](<https://devfeed.tech/tags/software.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

The article recommends treating engineering AI as ongoing adoption work. It proposes taking about ten people off product work for a few months, then returning most to product teams while retaining a permanent core of three: an educator, an experimentation and evaluation lead, and a tooling maintainer. It also calls for budgeting communication and workshops, pairing builders with a hands-on communicator, and VP-level ownership. Measure first-version delivery speed alongside merge-to-production time; license counts and AI-written-code share indicate usage, not changed work. The author argues that faster coding may not improve delivery when release queues or production access remain bottlenecks. The cited evidence includes a METR study where experienced developers took 19% longer with AI despite believing they were faster; the article notes that the MIT report it cites has a contested method and 153 survey responses.

### Source excerpt

Learn how engineering leaders can structure AI adoption teams, sustain AI tooling, and measure improvements in software delivery after rollout.

## Three Months Under the Bodhi Tree: The Fivetran Research Rotation | Blog | Fivetran

DevFeed: [Three Months Under the Bodhi Tree: The Fivetran Research Rotation | Blog | Fivetran](<https://devfeed.tech/articles/three-months-under-the-bodhi-tree-the-fivetran-research-rotation-blog-fivetran-141343.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/three-months-under-the-bodhi-tree-the-fivetran-research-rotation>)

Author: Meel Velliste

Published: 2026-11-18T06:13:15Z

Content type: article

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

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

Tags: [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [after](<https://devfeed.tech/tags/after.md>), [all](<https://devfeed.tech/tags/all.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [am](<https://devfeed.tech/tags/am.md>), [apply](<https://devfeed.tech/tags/apply.md>), [blog](<https://devfeed.tech/tags/blog.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [one](<https://devfeed.tech/tags/one.md>), [program](<https://devfeed.tech/tags/program.md>), [research](<https://devfeed.tech/tags/research.md>), [rotation](<https://devfeed.tech/tags/rotation.md>), [technical](<https://devfeed.tech/tags/technical.md>), [under](<https://devfeed.tech/tags/under.md>), [unique](<https://devfeed.tech/tags/unique.md>), [world](<https://devfeed.tech/tags/world.md>)

### AI overview

At the start of each financial quarter, Fivetran selects a few engineers from anywhere in the company for a three-month Research Rotation focused on one technical problem alongside the CTO's team. Participants step away from regular sprint work, keep journals, and join daily sessions for brainstorming and guidance. Projects may span multiple rotations, and results may take a year or more to appear. The program aims to support ambitious research while bringing engineers' varied experience into the research team; participants return to their home teams with broader technical context and more practice thinking creatively. Engineers interviewed describe the experience as rewarding and say sustained work pushed their technical understanding beyond individual connector details toward how the wider system fits together. The article notes that successful solutions are not guaranteed.

### Source excerpt

A unique program allows any Fivetran engineer, anywhere in the world, to spend months pondering one interesting technical problem.

## Big News! "The Multiplier Mindset" Now Available Everywhere 🎉

DevFeed: [Big News! "The Multiplier Mindset" Now Available Everywhere 🎉](<https://devfeed.tech/articles/big-news-the-multiplier-mindset-now-available-everywhere-138517.md>)

Original publisher: [Read original article](<https://newsletter.eng-leadership.com/p/big-news-the-multiplier-mindset-now>)

Author: Gregor Ojstersek

Published: 2026-11-17T14:51:50Z

Content type: release

Language: en

Sources: [Engineering Leadership](<https://devfeed.tech/sources/engineering-leadership.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Publishing](<https://devfeed.tech/topics/publishing.md>)

Tags: [adobe](<https://devfeed.tech/tags/adobe.md>), [advice](<https://devfeed.tech/tags/advice.md>), [africa](<https://devfeed.tech/tags/africa.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [asia](<https://devfeed.tech/tags/asia.md>), [australia](<https://devfeed.tech/tags/australia.md>), [book](<https://devfeed.tech/tags/book.md>), [career](<https://devfeed.tech/tags/career.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [europe](<https://devfeed.tech/tags/europe.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [france](<https://devfeed.tech/tags/france.md>), [mindset](<https://devfeed.tech/tags/mindset.md>), [news](<https://devfeed.tech/tags/news.md>), [order](<https://devfeed.tech/tags/order.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The Multiplier Mindset argues that in an AI era where agents write much of the code, engineers create greater impact by helping others succeed, delivering projects, and advancing the organization--not through individual output alone. It covers relevant mindsets, traits, and skills; eight case studies from companies including Pinterest, Adobe, and Microsoft; and ways to use AI to become a more effective multiplier. The announcement says the O'Reilly book is available as an e-book and print edition through multiple retailers, with formats varying by country.

### Source excerpt

You can now order both the e-book and print version across many different stores!

## AI in Leadership: Managing People, Not Just Work

DevFeed: [AI in Leadership: Managing People, Not Just Work](<https://devfeed.tech/articles/ai-in-leadership-managing-people-not-just-work-135511.md>)

Original publisher: [Read original article](<https://hackernoon.com/ai-in-leadership-managing-people-not-just-work?source=rss>)

Author: Maxi Contieri

Published: 2026-11-16T04:22:53Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [meetings](<https://devfeed.tech/topics/meetings.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-augmented-management](<https://devfeed.tech/tags/ai-augmented-management.md>), [ai-employee-feedback](<https://devfeed.tech/tags/ai-employee-feedback.md>), [ai-performance-reviews](<https://devfeed.tech/tags/ai-performance-reviews.md>), [ai-team-productivity](<https://devfeed.tech/tags/ai-team-productivity.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [human-in-the-loop-ai](<https://devfeed.tech/tags/human-in-the-loop-ai.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [management](<https://devfeed.tech/tags/management.md>), [manager](<https://devfeed.tech/tags/manager.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [people](<https://devfeed.tech/tags/people.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The article argues that AI can extend a manager's capacity to coordinate people and improve decisions, while human judgment remains responsible for consequential choices. It describes using AI to select meeting attendees, draft minutes and action items, translate technical status for business stakeholders, rehearse difficult conversations, triage messages, provide delegation context, summarize stand-ups, identify recurring team issues, and support hiring, feedback, development, and salary calibration. It distinguishes automation and workflow operation from augmentation, which helps managers weigh options rather than decide for them. The examples repeatedly require human review or decisions; they also flag recording consent, hiring bias and local labor law, team level signals instead of individual surveillance, and organizational approval and least privilege before automating replies or processing confidential information. The article presents these as proposed practices and tools, not evidence of measured outcomes.

### Source excerpt

AI removes a manager's cognitive limit. Use it for meetings, feedback, and hard conversations.

## Secure Code Through Quality: Why Speed Is No Longer Enough

DevFeed: [Secure Code Through Quality: Why Speed Is No Longer Enough](<https://devfeed.tech/articles/secure-code-through-quality-why-speed-is-no-longer-enough-137221.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/code-quality-in-2027-everyone-got-fast-now-get-good>)

Author: Adam Arellano

Published: 2026-11-16T00:00:00Z

Content type: opinion

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [Code quality](<https://devfeed.tech/topics/code-quality.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Application Security](<https://devfeed.tech/topics/application-security.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [assets](<https://devfeed.tech/tags/assets.md>), [code](<https://devfeed.tech/tags/code.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [developers](<https://devfeed.tech/tags/developers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [environment](<https://devfeed.tech/tags/environment.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [frontier-models](<https://devfeed.tech/tags/frontier-models.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [internet](<https://devfeed.tech/tags/internet.md>), [kpis](<https://devfeed.tech/tags/kpis.md>), [quality](<https://devfeed.tech/tags/quality.md>), [shift](<https://devfeed.tech/tags/shift.md>), [speed](<https://devfeed.tech/tags/speed.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

The text argues that as AI makes code generation faster and flaws easier to find, organizations should prioritize code that works as intended and is safe and defensible. It recommends maintaining an inventory of software and the ability to identify vulnerability exposure quickly; restructuring systems to reduce internet exposure while preserving functionality; and shifting engineering priorities from feature deadlines toward refactoring, simpler code, and less exposure. Speed still matters for patching--PHP2Shell was reportedly exploited within hours--but the text says timely answers to leadership depend on patch management and visibility into what runs within company boundaries. It advocates governing the process from specification through production and runtime.

### Source excerpt

Shift from AI-generated code velocity to code quality by improving visibility, strengthening architecture, and prioritizing secure engineering practices. | Blog

## One-way and two-way doors

DevFeed: [One-way and two-way doors](<https://devfeed.tech/articles/one-way-and-two-way-doors-133714.md>)

Original publisher: [Read original article](<https://www.theengineeringmanager.com/growth/one-way-and-two-way-doors/>)

Author: James Stanier

Published: 2026-11-13T20:59:04Z

Content type: article

Language: en

Sources: [The Engineering Manager](<https://devfeed.tech/sources/the-engineering-manager-2.md>)

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

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [costs](<https://devfeed.tech/tags/costs.md>), [culture](<https://devfeed.tech/tags/culture.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [decision](<https://devfeed.tech/tags/decision.md>), [difference](<https://devfeed.tech/tags/difference.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [growth](<https://devfeed.tech/tags/growth.md>), [management](<https://devfeed.tech/tags/management.md>)

### AI overview

The one-way/two-way door framework speeds decisions by matching process to the real cost of reversal. Consequential, hard-to-reverse choices--such as committing to a public API or deleting customer data--call for careful consultation; reversible choices can be made quickly by people close to the work. Treating too many choices as irreversible creates approval bottlenecks, discourages experimentation, and weakens autonomy. Classification requires checking practical side effects and who would bear the cost of reversing a decision: a code change may be technically revertible, while a public API may already have users. The article recommends asking what could go wrong, using pre-mortems, deciding with roughly 70% of needed information when iteration is feasible, publishing decision guidelines, keeping decision logs, and setting a quick leadership response time for escalations. It suggests reviewing five recent consequential team decisions and testing whether their reversibility was correctly judged.

### Source excerpt

A little over a year ago, I wrote an article called Going direct. This reflected a cultural change in management style that had happened over the last few years, where everyone should be encouraged to communicate openly to anybody and everybody without passing messages through the management chain. However, making decisions is still important enough [...] The post One-way and two-way doors appeared first on The Engineering Manager.

## Podcast: Doing The Right Thing: Accountability In The Age Of AI Coding Summary

DevFeed: [Podcast: Doing The Right Thing: Accountability In The Age Of AI Coding Summary](<https://devfeed.tech/articles/podcast-doing-the-right-thing-accountability-in-the-age-of-ai-coding-summary-131629.md>)

Original publisher: [Read original article](<https://www.infoq.com/podcasts/accountability-age-ai-coding-summary/>)

Author: Hugo Venturini

Published: 2026-11-13T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [responsible-ai](<https://devfeed.tech/topics/responsible-ai.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [accountability-age-ai-coding-summary](<https://devfeed.tech/tags/accountability-age-ai-coding-summary.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [ai-risks](<https://devfeed.tech/tags/ai-risks.md>), [architect](<https://devfeed.tech/tags/architect.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [career](<https://devfeed.tech/tags/career.md>), [code](<https://devfeed.tech/tags/code.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [code-generator](<https://devfeed.tech/tags/code-generator.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [coding](<https://devfeed.tech/tags/coding.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [culture](<https://devfeed.tech/tags/culture.md>), [culture-methods](<https://devfeed.tech/tags/culture-methods.md>), [distributed-team](<https://devfeed.tech/tags/distributed-team.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-culture-podcast](<https://devfeed.tech/tags/engineering-culture-podcast.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [infoq](<https://devfeed.tech/tags/infoq.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [psychological-safety](<https://devfeed.tech/tags/psychological-safety.md>), [quality](<https://devfeed.tech/tags/quality.md>), [roles](<https://devfeed.tech/tags/roles.md>), [safety](<https://devfeed.tech/tags/safety.md>), [software-craftsmanship](<https://devfeed.tech/tags/software-craftsmanship.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [team-collaboration](<https://devfeed.tech/tags/team-collaboration.md>), [teamwork](<https://devfeed.tech/tags/teamwork.md>), [transparency](<https://devfeed.tech/tags/transparency.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Hugo Venturini argues that people remain accountable for AI-generated code and its outcomes. He says pull-request scale predates AI; his team uses trust and judgment to decide what needs review, relying on automated checks for routine work and seeking review for product-critical changes, while acknowledging that review volume remains an open problem. Recalling Microsoft's 2014 merger of engineering and testing roles, he says shared responsibility raised quality, and warns that blaming AI can undermine ownership. As AI blurs roles such as engineer, tester, architect, and product manager, he argues organizations should help people learn to ask better questions. To make that responsibility safe, he describes honest, no-blame Q&As, anonymous questions, and focusing criticism on solutions rather than individuals. He says such transparency can start within a team and spread, though cultural change takes patience.

### Source excerpt

In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Hugo Venturini about who is accountable when AI writes the code, how AI is reshaping code review and traditional engineering roles, and how leaders build a culture of transparency and psychological safety. By Hugo Venturini

## We Promised Three Months. It Took Nine.

DevFeed: [We Promised Three Months. It Took Nine.](<https://devfeed.tech/articles/we-promised-three-months-it-took-nine-131444.md>)

Original publisher: [Read original article](<https://newsletter.techworld-with-milan.com/p/we-promised-three-months-it-took>)

Author: Dr Milan Milanović

Published: 2026-11-12T16:02:49Z

Content type: article

Language: en

Sources: [Tech World With Milan Newsletter](<https://devfeed.tech/sources/tech-world-with-milan-newsletter.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [bus factor](<https://devfeed.tech/topics/bus-factor.md>), [software development triangle](<https://devfeed.tech/topics/software-development-triangle.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [modular-monolith](<https://devfeed.tech/topics/modular-monolith.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [bus-factor](<https://devfeed.tech/tags/bus-factor.md>), [conway-s-law](<https://devfeed.tech/tags/conway-s-law.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [laws](<https://devfeed.tech/tags/laws.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The billing-system rewrite took nine months despite a three-month estimate, illustrating how software laws can point in different directions because they apply under different conditions. The article recommends checking each law's assumptions, measuring outcomes with counter-metrics to discourage gaming, and diagnosing team problems by listing relevant forces, selecting three to five applicable laws, then addressing the strongest force first. Its examples include coordination costs from adding people, token boards rewarding usage rather than quality, and AI-generated services creating contract, comprehension, and integration problems. Practical responses described include agreeing on API contracts before code is written, documenting core modules, starting with a working modular system and extracting services as needed, preserving compatibility with users' observed dependencies, and budgeting time for integration, testing, documentation, handover, and deployment. In the rewrite, the author says the unrealistic deadline was the strongest force; reducing the initial launch scope to one country was the proposed correction.

### Source excerpt

What to do when software engineering laws point in opposite directions

## Technical Debt is Social; it is the Price of Learning by Doing

DevFeed: [Technical Debt is Social; it is the Price of Learning by Doing](<https://devfeed.tech/articles/technical-debt-is-social-it-is-the-price-of-learning-by-doing-130321.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/tech-debt-learning-doing/>)

Author: Ben Linders

Published: 2026-11-12T11:05:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Code Modularity](<https://devfeed.tech/topics/code-modularity.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [agentic-development-lifecycle](<https://devfeed.tech/tags/agentic-development-lifecycle.md>), [ai](<https://devfeed.tech/tags/ai.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [can](<https://devfeed.tech/tags/can.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [code](<https://devfeed.tech/tags/code.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [context](<https://devfeed.tech/tags/context.md>), [culture-methods](<https://devfeed.tech/tags/culture-methods.md>), [doing](<https://devfeed.tech/tags/doing.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [goto-conference](<https://devfeed.tech/tags/goto-conference.md>), [learning](<https://devfeed.tech/tags/learning.md>), [news](<https://devfeed.tech/tags/news.md>), [production](<https://devfeed.tech/tags/production.md>), [sign](<https://devfeed.tech/tags/sign.md>), [social](<https://devfeed.tech/tags/social.md>), [sociotechnical-architecture](<https://devfeed.tech/tags/sociotechnical-architecture.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [tech-debt-learning-doing](<https://devfeed.tech/tags/tech-debt-learning-doing.md>), [technical](<https://devfeed.tech/tags/technical.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [understand](<https://devfeed.tech/tags/understand.md>)

### AI overview

Technical debt can be a deliberate cost of learning: releasing imperfect software tests assumptions with users and businesses, and teams repay the debt by incorporating what they learn into later iterations. It becomes costly when software fails to keep pace with that learning. The excerpt recommends small batches and tight feedback loops to preserve design rationale and continuously close the gap. It also describes a tradeoff between shipping features and preserving the flexibility to adapt them, sometimes by delaying design commitments until more is known. With agentic coding, production can outpace human understanding; code records agents' decisions while people remain accountable. The resulting debt includes weakened ownership and gaps in shared understanding, making repayment a sociotechnical challenge, not only code cleanup.

### Source excerpt

Technical debt is not necessarily a sign of poor engineering. It can be the price of learning through software in use. As AI accelerates code production beyond our capacity to understand code and context, technical debt increasingly becomes a sociotechnical challenge. By Ben Linders

## The future of work is built by everyone

DevFeed: [The future of work is built by everyone](<https://devfeed.tech/articles/the-future-of-work-is-built-by-everyone-130280.md>)

Original publisher: [Read original article](<https://blog.n8n.io/the-future-of-work-is-built-by-everyone/>)

Author: Romina da Costa

Published: 2026-11-12T08:00:00Z

Content type: opinion

Language: en

Sources: [n8n](<https://devfeed.tech/sources/n8n-blog.md>)

Topics: [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [n8n](<https://devfeed.tech/topics/n8n.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automation](<https://devfeed.tech/tags/automation.md>), [building-automation](<https://devfeed.tech/tags/building-automation.md>), [business](<https://devfeed.tech/tags/business.md>), [decentralization](<https://devfeed.tech/tags/decentralization.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [enablement](<https://devfeed.tech/tags/enablement.md>), [future-of-work](<https://devfeed.tech/tags/future-of-work.md>), [guild](<https://devfeed.tech/tags/guild.md>), [learning](<https://devfeed.tech/tags/learning.md>), [n8n](<https://devfeed.tech/tags/n8n.md>), [n8n-on-n8n](<https://devfeed.tech/tags/n8n-on-n8n.md>)

### AI overview

The article argues that companies should enable employees across departments to build automations, with a central team shifting from service desk to guild: setting standards, providing shared architecture and reusable templates, and retaining ownership of high-stakes work. At n8n, AI assistants and MCP are described as lowering the barrier enough for employees to create automations that once required weeks of queue time. Decentralization still needs guardrails: understand processes before automating, prefer proven tools where appropriate, document workflows for handoff, and use data and AI responsibly. The author notes that regulated or security-sensitive organizations may reasonably keep building centralized. n8n's effort remains early: standards are inconsistent and the team still faces workflow maintenance it cannot yet hand over, so the approach requires continued prioritization, upskilling, and enablement.

### Source excerpt

Building automation is getting easier fast. So why keep it locked inside one team? A follow-up on what replaces the central automation team, and what n8n is learning as it opens building up to everyone.

## AI Is Changing Software Engineering Forever | Gregor Ojstersek

DevFeed: [AI Is Changing Software Engineering Forever | Gregor Ojstersek](<https://devfeed.tech/articles/ai-is-changing-software-engineering-forever-gregor-ojstersek-129778.md>)

Original publisher: [Read original article](<https://dataengineeringcentral.substack.com/p/ai-is-changing-software-engineering>)

Author: Daniel Beach

Published: 2026-11-11T13:25:32Z

Content type: article

Language: en

Sources: [Data Engineering Central](<https://devfeed.tech/sources/data-engineering-central.md>)

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

Tags: [advice](<https://devfeed.tech/tags/advice.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [book](<https://devfeed.tech/tags/book.md>), [career](<https://devfeed.tech/tags/career.md>), [code](<https://devfeed.tech/tags/code.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [cto](<https://devfeed.tech/tags/cto.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [developer](<https://devfeed.tech/tags/developer.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-jobs](<https://devfeed.tech/tags/engineering-jobs.md>), [engineering-leadership](<https://devfeed.tech/tags/engineering-leadership.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [fundamentals](<https://devfeed.tech/tags/fundamentals.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The episode's central takeaway is that writing code may matter less as AI changes engineering work, while engineering fundamentals, problem-solving, and leadership remain important. Gregor Ojstersek discusses how AI may affect junior through principal roles, engineering management, and the path to CTO; the risks of AI-generated code, weak engineering practices, and losing fundamental skills; and why choosing the right work matters. The excerpt also describes his journey from self-taught programmer to CTO, his book The Multiplier Mindset, and the growth of his Engineering Leadership Newsletter to over 200,000 subscribers. It lists topics and chapter timestamps but does not provide the detailed discussion or specific advice.

### Source excerpt

From Engineer to CTO

## Glue work is still harmful in the age of AI

DevFeed: [Glue work is still harmful in the age of AI](<https://devfeed.tech/articles/glue-work-is-still-harmful-in-the-age-of-ai-128963.md>)

Original publisher: [Read original article](<https://seangoedecke.com/glue-work-is-still-harmful-in-the-age-of-ai/>)

Published: 2026-11-11T00:00:00Z

Content type: opinion

Language: en

Sources: [Sean Goedecke](<https://devfeed.tech/sources/seangoedecke-com-rss-feed.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [code](<https://devfeed.tech/tags/code.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [fewer](<https://devfeed.tech/tags/fewer.md>), [gatekeepers](<https://devfeed.tech/tags/gatekeepers.md>), [hiring](<https://devfeed.tech/tags/hiring.md>), [legal](<https://devfeed.tech/tags/legal.md>), [less](<https://devfeed.tech/tags/less.md>), [llms](<https://devfeed.tech/tags/llms.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [proof-of-work](<https://devfeed.tech/tags/proof-of-work.md>), [report](<https://devfeed.tech/tags/report.md>), [reports](<https://devfeed.tech/tags/reports.md>), [ship](<https://devfeed.tech/tags/ship.md>), [status](<https://devfeed.tech/tags/status.md>), [team](<https://devfeed.tech/tags/team.md>), [teams](<https://devfeed.tech/tags/teams.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The author argues that glue work--unrewarded, informal coordination and support--is less important to companies than in the 2010s. They attribute the change to AI agents letting one engineer handle work once done by a small team, fewer difficult gatekeepers, fewer junior hires needing onboarding, and LLMs generating write-only reports. They caution that LLMs should not handle direct communication between engineers, which can damage working relationships. Their recommendation is to avoid becoming the default glue worker, let broken processes fail so they can be changed, and take on small amounts of tactical glue work when it materially helps a project, while focusing most effort on code and directing AI agents.

### Source excerpt

I am not a believer in glue work1. Processes that can only be sustained by the unrewarded sacrifice of engineers ought to die. Now that LLMs are writing most of our code, does that free human engineers up to do more glue work? No, it doesn't. I think glue work is actually less important to companies than it was in the 2010s. Let's go through four reasons why. First, AI decreases the amount of coordination needed to ship. The magnifying effect of AI agents means that any single engineer can now take on projects that would previously have needed a small team. A lot of glue work was helping with coordination: booking kickoff and status meetings, passing around internal updates, and so on. A single engineer doesn't need to do any of that. Second, engineers in the 2020s require less "careful handling". In my experience, the most important subcategory of coordination-based glue work was managing difficult people. Many companies have secret gatekeepers: engineers with outsized influence and large egos who will shoot down your project if they feel insufficiently consulted. I've written before about how some teams are structurally set up to be gatekeepers, and how some engineers could get by in the 2010s by basically saying no to everything. The end of ZIRP changed all that. Many of the prickliest gatekeepers have been forced out of the industry or coerced into changing their attitude, which reduces the amount of necessary glue work required to ship. Third, people are hiring fewer juniors. This is probably a bad thing for the industry, but it does also eliminate a big category of glue work. Experienced hires need less hand-holding, so companies don't need people to quietly volunteer to onboard new hires. Fourth, write-only reports can be automated with LLMs. A lot of glue work was what I call "proof of work": writing a report to demonstrate that you're aware of what your team is doing, or filling in a template to satisfy some legal requirement. This was often work that nobod

## Candidate Statement for the 2026 W3C TAG Election

DevFeed: [Candidate Statement for the 2026 W3C TAG Election](<https://devfeed.tech/articles/candidate-statement-for-the-2026-w3c-tag-election-129507.md>)

Original publisher: [Read original article](<https://lea.verou.me/blog/2026/tag/>)

Author: Lea Verou

Published: 2026-11-11T00:00:00Z

Content type: opinion

Language: en

Sources: [Lea Verou's blog](<https://devfeed.tech/sources/lea-verou-s-blog.md>)

Topics: [W3C](<https://devfeed.tech/topics/w3c.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Internationalization (i18n)](<https://devfeed.tech/topics/i18n.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [model architecture](<https://devfeed.tech/topics/model-architecture.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Model Routing](<https://devfeed.tech/topics/model-routing.md>)

Tags: [2020](<https://devfeed.tech/tags/2020.md>), [2021](<https://devfeed.tech/tags/2021.md>), [2022](<https://devfeed.tech/tags/2022.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [academic](<https://devfeed.tech/tags/academic.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [award](<https://devfeed.tech/tags/award.md>), [blog](<https://devfeed.tech/tags/blog.md>), [building](<https://devfeed.tech/tags/building.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [design](<https://devfeed.tech/tags/design.md>), [design-principles](<https://devfeed.tech/tags/design-principles.md>), [election](<https://devfeed.tech/tags/election.md>), [entrepreneurship](<https://devfeed.tech/tags/entrepreneurship.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [google](<https://devfeed.tech/tags/google.md>), [human-computer-interaction](<https://devfeed.tech/tags/human-computer-interaction.md>), [impact](<https://devfeed.tech/tags/impact.md>), [personal](<https://devfeed.tech/tags/personal.md>), [statement](<https://devfeed.tech/tags/statement.md>), [w3c](<https://devfeed.tech/tags/w3c.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>)

### AI overview

Lea seeks to return to the W3C Technical Architecture Group (TAG), arguing it should shape Web architecture proactively, not mainly review features after their design is set or they ship. She proposes identifying cross-group gaps, sketching coherent solutions, and bringing relevant working groups into the work without taking over their responsibilities. In her prior two terms (2021-2025), she co-led Web Platform Design Principles, started the Web Platform Gaps initiative, liaised with TC39, and took part in hundreds of design reviews. She says her work across CSS, TC39, WHATWG, web development, and open source gives her broad platform experience. She also urges the TAG to assess AI-written code and agent use of the Web through evidence and architectural principles, while upholding user agency, privacy, accessibility, and interoperability. Google, Microsoft, and the OpenJS Foundation have pooled resources to fund her participation if elected; she says they do not direct or veto her positions.

### Source excerpt

Group photo of the W3C TAG in July 2022 with me to the left of Sir Tim Berners-Lee (inventor of the Web and TAG chair emeritus). Photo credit: Dan Appelquist I had the great honor of being elected to the TAG by the W3C membership in 2020 and again in 2022, serving two terms from 2021 to 2025. After a two-year break, this year I'm running to return, thanks to Google, Microsoft, and OpenJS Foundation pooling resources to make it possible. 💙 The W3C Technical Architecture Group (TAG) is the Working Group that ensures that Web Platform technologies are usable and follow consistent design principles, whether they are created inside or outside W3C. It advocates for the needs of everyone who uses the Web and everyone who works on the Web. If you work for a company that is a W3C Member, please consider encouraging your AC rep to vote for me! (Ask me if you don't know who that is) My candidate statement follows. I'm Lea, and I'm running to return to the TAG, where I served two terms from 2021 to 2025. It was some of the most fulfilling work of my career. The only reason I did not run in 2024 is that the job takes hundreds of hours a year, which as an independent I could not sustain pro bono. This year, in recognition of my service, Google, Microsoft, and the OpenJS Foundation have pooled resources to fully fund my participation, so I can finally commit the time the job deserves while remaining independent. My work spans the entire web platform: 14 years in the CSS Working Group, active participation in TC39 and WHATWG, two decades of building for the web, and open source running on millions of websites. In 2025 the OpenJS Foundation recognized my overall impact on the web platform with its Pathfinder for Standards Award. That breadth is exactly what the TAG requires. With a PhD in Human-Computer Interaction from MIT and a 20+ year career that includes entrepreneurship and product leadership, I combine academic rigor and big-picture perspective with pragmatism, an eye for har

## How Salesforce Scaled Engineering AI Adoption Without Stifling Innovation

DevFeed: [How Salesforce Scaled Engineering AI Adoption Without Stifling Innovation](<https://devfeed.tech/articles/how-salesforce-scaled-engineering-ai-adoption-without-stifling-innovation-129311.md>)

Original publisher: [Read original article](<https://engineering.salesforce.com/how-salesforce-scaled-engineering-ai-adoption-without-stifling-innovation/>)

Author: Paul Constantinides

Published: 2026-11-10T19:17:30Z

Content type: article

Language: en

Sources: [Salesforce](<https://devfeed.tech/sources/salesforce-engineering-blog.md>)

Topics: [AI Strategy](<https://devfeed.tech/topics/ai-strategy.md>), [Developer Enablement](<https://devfeed.tech/topics/developer-enablement.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [but](<https://devfeed.tech/tags/but.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [first](<https://devfeed.tech/tags/first.md>), [hyperforce](<https://devfeed.tech/tags/hyperforce.md>), [initiative](<https://devfeed.tech/tags/initiative.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [little](<https://devfeed.tech/tags/little.md>), [platform](<https://devfeed.tech/tags/platform.md>), [practices](<https://devfeed.tech/tags/practices.md>), [resources](<https://devfeed.tech/tags/resources.md>), [room](<https://devfeed.tech/tags/room.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

Salesforce's Hyperforce Runtime Platform scaled AI across roughly 500 engineers by pairing shared distribution and governance with team ownership and freedom to experiment. A Steering Committee set guidance and quality standards; scrum teams volunteered solutions to existing pain points and owned delivery and support, while AI Champions connected teams with committee decisions and shared new capabilities. The HRPDX Claude Code plugin distributed common instructions and skills, with session-start hooks handling updates; teams could extend it or keep solutions local. SDLC and DORA metrics, including pull-request-based lead time, helped teams choose where to focus and assess results. The excerpt reports adoption near 100% in the first three months, a 26% throughput gain, 32% better inner-loop efficiency, cycle time falling from 22 to 11 days, and sprint forecast ratio rising from 66% to 90%, while maintainability remained 6.04. Plugin adoption reached 97%, while uptake differed by capability: Prizm reached 95% and shared Claude instructions lagged. Increased coding output also lengthened review cycles, prompting team-specific review skills and work on testing and deployment bottlene�.

### Source excerpt

By Paul Constantinides, Anubhav Dhoot and Jackie Chambers de Freitas Salesforce's Hyperforce Runtime Platform (HRP) engineers were already experimenting with AI. But promising capabilities remained scattered across teams, overlapping efforts competed for limited resources, and tight delivery commitments left little room for another initiative. Scaling AI adoption demanded shared practices; preserving innovation demanded team freedom. [...] The post How Salesforce Scaled Engineering AI Adoption Without Stifling Innovation appeared first on Salesforce Engineering Blog.

## Hiring Junior Engineers

DevFeed: [Hiring Junior Engineers](<https://devfeed.tech/articles/hiring-junior-engineers-129329.md>)

Original publisher: [Read original article](<https://eng.lyft.com/hiring-junior-engineers-1edc53e0fd5f?source=rss----25cd379abb8---4>)

Author: Ashley Lorden

Published: 2026-11-10T17:08:06Z

Content type: article

Language: en

Sources: [Lyft Engineering](<https://devfeed.tech/sources/lyft-engineering-medium.md>)

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

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [big-tech](<https://devfeed.tech/tags/big-tech.md>), [career](<https://devfeed.tech/tags/career.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-interviews](<https://devfeed.tech/tags/coding-interviews.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [company-culture](<https://devfeed.tech/tags/company-culture.md>), [curiosity](<https://devfeed.tech/tags/curiosity.md>), [data-structures](<https://devfeed.tech/tags/data-structures.md>), [database](<https://devfeed.tech/tags/database.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [experience](<https://devfeed.tech/tags/experience.md>), [hiring](<https://devfeed.tech/tags/hiring.md>), [hiring-engineers](<https://devfeed.tech/tags/hiring-engineers.md>), [junior](<https://devfeed.tech/tags/junior.md>), [junior-software-engineer](<https://devfeed.tech/tags/junior-software-engineer.md>)

### AI overview

The author prioritizes mindset and soft skills when hiring junior software engineers: curiosity, humility, ownership, collaboration, and the self-management to keep learning while delivering work. These traits can be hard to show in interviews, so candidates should share concrete stories. Core engineering knowledge still matters in the AI era: engineers need to choose approaches, assess tradeoffs, and prompt and review AI-generated code with sound judgment. For new hires at Lyft, the author also requires recent experience producing substantial production-quality code, which candidates can build through side projects, technical work in another role, or structured learning. The author says the role offers mentorship, resources, and room to grow.

### Source excerpt

Several people have asked me what the qualifications are for junior software engineers to be hired these days. This level is often referred to as "new grad," but people with lots of different backgrounds, not just recent university graduates, can use the entry-level software engineering role as their first job in big tech. For example, in my early career I worked as a generalist in nonprofit after studying environmental economics. Then, using experience managing a website as part of my job, coding personal projects, and going through a software bootcamp, I moved into a junior SWE role as the foundation of my career in engineering. Once you're in the SWE field, your background is not an overwhelming predictor of success in your job. So what is? The #1 qualifier I look for in hiring junior software engineers is mindset and soft skills. Curiosity, humility, and eagerness to learn is one critical area for successful engineers, and strong ownership, collaboration, and drive to create impact is another. The differentiator is self-management to find the right balance between the two, so that you're continuously both growing your skills and shipping real work. Transparently, although this is the top thing I'd like to see, it's really hard to demonstrate in interviews. If you have stories that show how you employ these skills, share them with your interviewers. For hard skills, in years past candidates have studied search algorithms, practiced using data structures, and considered optimal database patterns to pass coding interviews. In a world where AI agents write lots of our code, do prospective engineers still need to learn those core building and efficiency skills? Yes. Although you may not be writing a lot of syntax by hand, you must thoroughly know the right approach so that you can prompt and review for the correct tradeoffs. There is rarely a universal right answer; a non-optimal but easy-to-understand algorithm is sometimes the best choice, whereas in other circumst

## Customer support is the gnarliest AI problem

DevFeed: [Customer support is the gnarliest AI problem](<https://devfeed.tech/articles/customer-support-is-the-gnarliest-ai-problem-127396.md>)

Original publisher: [Read original article](<https://stackoverflow.blog/2026/11/10/customer-support-is-the-gnarliest-ai-problem/>)

Author: Phoebe Sajor

Published: 2026-11-10T08:40:00Z

Content type: article

Language: en

Sources: [Stack Overflow](<https://devfeed.tech/sources/stack-overflow-blog.md>)

Topics: [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ahmad-al-dahle](<https://devfeed.tech/tags/ahmad-al-dahle.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [airbnb](<https://devfeed.tech/tags/airbnb.md>), [balance](<https://devfeed.tech/tags/balance.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cto](<https://devfeed.tech/tags/cto.md>), [customer-support](<https://devfeed.tech/tags/customer-support.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [generative](<https://devfeed.tech/tags/generative.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [implement](<https://devfeed.tech/tags/implement.md>), [latency](<https://devfeed.tech/tags/latency.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [se-stackoverflow](<https://devfeed.tech/tags/se-stackoverflow.md>), [se-tech](<https://devfeed.tech/tags/se-tech.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Airbnb CTO Ahmad Al-Dahle describes customer support as a particularly difficult AI problem and discusses deploying multi-party AI agents to address it. He explains how evolving, rigorous evaluations help engineers balance response latency with accuracy, and argues that AI coding tools require software teams to exercise greater judgment. The supplied text gives no further details about the agents, evaluations, or engineering practices.

### Source excerpt

Ryan chats with Ahmad Al-Dahle, CTO at Airbnb, about deploying multi-party AI agents to tackle the uniquely gnarly problem of customer support, how a moving target of rigorous evaluations helps engineers balance latency against accuracy, and the ways in which AI coding tools demand an even higher level of judgment from software engineering teams.

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

## AI Removes the Manager's Cognitive Limit. Use it Wisely

DevFeed: [AI Removes the Manager's Cognitive Limit. Use it Wisely](<https://devfeed.tech/articles/ai-removes-the-manager-s-cognitive-limit-use-it-wisely-125745.md>)

Original publisher: [Read original article](<https://hackernoon.com/ai-removes-the-managers-cognitive-limit-use-it-wisely?source=rss>)

Author: Maxi Contieri

Published: 2026-11-10T06:04:09Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [acceptance-tests](<https://devfeed.tech/tags/acceptance-tests.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [ai-powered-planning](<https://devfeed.tech/tags/ai-powered-planning.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automated-status-reports](<https://devfeed.tech/tags/automated-status-reports.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bias](<https://devfeed.tech/tags/bias.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [brain](<https://devfeed.tech/tags/brain.md>), [bus-factor](<https://devfeed.tech/tags/bus-factor.md>), [business](<https://devfeed.tech/tags/business.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [human-in-the-loop-ai](<https://devfeed.tech/tags/human-in-the-loop-ai.md>), [manager](<https://devfeed.tech/tags/manager.md>), [product-management](<https://devfeed.tech/tags/product-management.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The article argues that AI can expand a manager's capacity to plan, monitor and improve software work, while people retain decisions and review. It proposes short-cycle replanning with AI constraint and prioritization skills; small, verifiable task slices; and disposable prototypes subject to human design, QA and standards reviews. AI can draft evidence-cited status reports, surface knowledge silos, assess change risk, support defect triage and testing, detect incidents, run known remediations, analyze performance, monitor releases and draft changelogs. The team decides priorities, risk tolerance, incident actions and fixes; managers review reports and unblock work. The author cautions against minute-by-minute monitoring, requiring notice and consent for AI monitoring, and says the company knowledge base needs organizational agreement and source validation. Complex business rules should live in automated acceptance tests, not only the company brain. These are proposed practices in the excerpt, not evidence of measured outcomes.

### Source excerpt

AI removes the manager's cognitive limit. You should use it to sharpen your decisions, not just to summarize emails.

## How Microsoft's Principal Software Engineering Manager Works and Uses AI

DevFeed: [How Microsoft's Principal Software Engineering Manager Works and Uses AI](<https://devfeed.tech/articles/how-microsoft-s-principal-software-engineering-manager-works-and-uses-ai-127101.md>)

Original publisher: [Read original article](<https://newsletter.eng-leadership.com/p/how-microsofts-principal-software>)

Author: Gregor Ojstersek

Published: 2026-11-09T22:52:33Z

Content type: article

Language: en

Sources: [Engineering Leadership](<https://devfeed.tech/sources/engineering-leadership.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [addition](<https://devfeed.tech/tags/addition.md>), [advice](<https://devfeed.tech/tags/advice.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [book](<https://devfeed.tech/tags/book.md>), [case](<https://devfeed.tech/tags/case.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [manager](<https://devfeed.tech/tags/manager.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [mindset](<https://devfeed.tech/tags/mindset.md>), [my](<https://devfeed.tech/tags/my.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [study](<https://devfeed.tech/tags/study.md>), [uses](<https://devfeed.tech/tags/uses.md>)

### AI overview

Microsoft Principal Software Engineering Manager Tarik Guney focuses on sustainable team value by finding bottlenecks in communication, tooling, processes, and assumptions. He tracks leading indicators such as productivity and process efficiency alongside outcomes like reliability and delivery predictability, using mismatches to spot misplaced effort. He describes multiplying others as increasing throughput without adding hours or stress, through clear goals, trust, psychological safety, and efficient tools. He uses AI within existing workflows to speed coding and information access, summarize meetings and reconstruct context, tailor communications, draft documents, explore options, and handle routine tasks such as pull requests and pipeline checks. These uses reduce repetitive cognitive work and context loss, while leaving problem framing and decisions to people. His advice is to start with practical problems, integrate AI into current workflows, and judge it by improvements in clarity, speed, and quality rather than by how widely it is used.

### Source excerpt

Case study from my book The Multiplier Mindset, published by O'Reilly.

## Building Software: Speed Counts, But Quality Matters More

DevFeed: [Building Software: Speed Counts, But Quality Matters More](<https://devfeed.tech/articles/building-software-speed-counts-but-quality-matters-more-125601.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/software-speed-vs-quality/>)

Author: Jeff Williams

Published: 2026-11-09T13:00:42Z

Content type: opinion

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [Code quality](<https://devfeed.tech/topics/code-quality.md>), [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>), [human review](<https://devfeed.tech/topics/human-review.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [atomic](<https://devfeed.tech/tags/atomic.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [counts](<https://devfeed.tech/tags/counts.md>), [curiosity](<https://devfeed.tech/tags/curiosity.md>), [development](<https://devfeed.tech/tags/development.md>), [digital-health](<https://devfeed.tech/tags/digital-health.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [first](<https://devfeed.tech/tags/first.md>), [gap](<https://devfeed.tech/tags/gap.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [i](<https://devfeed.tech/tags/i.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [matters](<https://devfeed.tech/tags/matters.md>), [more](<https://devfeed.tech/tags/more.md>), [quality](<https://devfeed.tech/tags/quality.md>), [software](<https://devfeed.tech/tags/software.md>), [speed](<https://devfeed.tech/tags/speed.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Agentic tools have spread across Atomic Spin's offices, and one team estimated that tools could have shortened an eight-week, two-developer engagement to five weeks; they used the time saved to improve quality. The harder constraint is now defining the right work and verifying results. Three of four managing partners independently raised the need for shared team practices and product knowledge. In healthcare, important workflows may be undocumented, so teams need to observe clinicians and involve people with relevant care expertise; changes also need clinical, security, quality, or regulatory review suited to their risk. More engineering capacity does not expand reviewers' limited time. The article recommends clarifying who defines and reviews work, identifying non-negotiable process steps, giving teams a practical starting point, and tracking user value, quality, and speed against a baseline. It also reports concerns about agent supervision fatigue and reduced colleague interaction, while noting that only one office raised fatigue.

### Source excerpt

This summer one of our most technical people said something that raised my curiosity. He has the Claude Code subscription. He read our process document. And when he sits down at the keyboard, he still doesn't know how to start. He wasn't complaining about the document. He was describing a gap, and I wanted to [...] The post Building Software: Speed Counts, But Quality Matters More appeared first on Atomic Spin.

[Next page](<https://devfeed.tech/topics/engineering-leadership.md?cursor=WyIyMDI2LTExLTA5VDEzOjAwOjQyKzAwOjAwIiwgImZmMzk1OWIwLTI2OTgtNGVhMi1hNjRkLWNjOWRmMGUxN2QwMyJd>)