u/OfficialLeadDev

Most engineering leaders have learned to advocate, tenaciously, for the projects their teams work on. They tightly couple their team’s success to the success of every project they ship. That instinct is right, but only to a point. Left unchecked, it becomes a trap.

Their job is to be the strongest advocates of our teams. Not of projects. It took the loss of a project defended for years to teach one leader the difference.

https://leaddev.com/leadership/killing-a-project-is-every-engineering-leaders-hardest-call

https://leaddev.com/ai/engineering-managers-ditch-cloud-ai-for-local-llms

Technical proficiency is no longer optional for engineering managers. It gives you credibility, protects your team’s focus time, and enables sound decisions without pulling engineers away from their work.

Staying technical requires deliberate investment.

You don’t need to be the best coder in the room: the goal is to understand what your team is building, why decisions were made, and what’s at stake – not to out-code your engineers.

You can read the full article on LeadDev: https://leaddev.com/career-development/how-to-stay-technical-as-an-engineering-manager

https://leaddev.com/ai/your-ai-agent-just-blamed-the-network-team-now-what

Every week brings another AI layoff headline, but nearly half of companies report AI-driven job creation. FDE postings grew 8.5x in a year. The U.S. Bureau of Labor Statistics projects 300,000 net new software developer jobs by 2033.

The real story isn't replacement. It's redistribution.

Same headcount. Different role mix. Faster cycle times. New roles — eval engineers, AI integration architects, forward deployed engineers — are emerging faster than old ones disappear.

"AI doesn't eliminate seats one-for-one. It shifts where the leverage sits."

If you're making hiring or career decisions based on the layoff narrative alone, you're working from bad data.

https://leaddev.com/ai/the-ai-talent-story-everyone-is-missing

https://leaddev.com/career-development/the-engineering-manager-role-is-splitting-in-two

First impressions can kill AI adoption... https://leaddev.com/ai/why-engineers-lose-trust-in-ai-coding-tools

https://leaddev.com/career-development/inside-bloombergs-flat-engineering-culture

https://leaddev.com/leadership/when-to-kill-a-software-project

https://leaddev.com/career-development/reality-being-principal-engineer

Translate tech debt into business risk https://leaddev.com/technical-direction/translate-tech-debt-into-business-risk

Something counterintuitive is happening: engineering managers are becoming the most sought-after individual contributors in the agentic coding era... https://leaddev.com/career-development/demand-for-engineering-managers-is-surging-in-the-agentic-coding-era

A new developer productivity system claims to be game proof by design. A leading researcher on metric failure isn’t so sure... https://leaddev.com/reporting/is-microsofts-engthrive-framework-immune-to-goodharts-law

Open-source abandonware isn’t new. Repositories have always accumulated half-finished projects and good intentions. But there’s growing evidence that AI-generated code is making the problem significantly worse. https://leaddev.com/software-quality/ai-generated-abandonware-is-hollowing-out-open-source

After rolling out an AI coding assistant, most teams see the same pattern: PRs get bigger, cycle times drop, sprint records fall. Feels great. Then a few months in, the on-call rotation gets brutal.

This isn't coincidence. The DORA 2024 report confirmed it across the industry: teams with significantly higher AI adoption also showed higher change failure rates.

Three failure patterns explain most of it, and none of them are new problems — they're old ones running faster:

1. Polished code fools reviewers. AI-generated code looks right. It follows conventions, reads cleanly, gets approved faster. But a model can produce a wrong implementation with the same fluency as a correct one. Reviewers pattern-match to familiar structure and skip the hard reasoning.

2. The model grades its own homework. When the same model writes the code and the tests, it tests its own assumptions — not your requirements. Coverage goes green. Edge cases nobody described stay untested.

3. AI can't see the whole system. The model only knows the code it's shown. It has no awareness of the shared retry queue, the upstream producer, the implicit guarantee held together by a three-year-old design decision. Clean-looking refactors quietly remove something critical.

The fix isn't slowing down AI adoption. It's redesigning the delivery process so it's worth amplifying:

• Write the spec before you write the prompt
• Tier changes by risk — anything touching payments or auth requires human business-logic review and a contract test against the live API
• Treat observability as a release gate — no monitoring dashboard, no merge

Teams that had strong practices before AI got faster. Teams that didn't started getting paged at midnight.

Full write-up with a FinTech case study (wrong field placement silently dropped disbursements during peak load, every unit test green): https://leaddev.com/ai/ai-coding-made-us-faster-why-did-incidents-increase

Model Context Protocol (MCP) was introduced by Anthropic in November 2024, and it has undergone tremendous development since then. The rapid evolution of Large Language Model (LLM) based agents has pushed MCP from experimental curiosity to the center of production at a speed faster than most developers anticipated.

As of Q1 2026, many big tech companies who own enterprise Application Programming Interfaces (APIs), like Google and Microsoft, have launched official MCP servers.

Transitioning from enterprise API to MCP is more than just prototype swapping or shallow interface wrappers. MCP demands the same rigor as enterprise APIs as both are essentially production infrastructure. MCP developers should also take careful considerations of MCP interface design.

Read the full article on LeadDev: https://leaddev.com/ai/an-engineers-guide-to-model-context-protocol-mcp

CTOs, engineering managers, and staff engineers are rushing to deploy autonomous AI agents across their businesses – either through their own volition or because of the clamor of demand from rank-and-file workers. However, they should think twice, a new study shows.

Enterprise large language model (LLM) agents are likely leaking company secrets, and throwing more compute at the problem is only making it worse, the study finds.

In part, that’s because of the AI’s ability to retrieve and synthesize vast amounts of internal data, from Slack messages to board transcripts, to automate tasks. By gathering that information, they also create issues with contextual integrity.

When retrieving dense corporate data, these agents routinely fail to disentangle essential task data from sensitive, contextually inappropriate information. Higher task completion rates often directly correlate with increased privacy violations.

Read the full story: https://leaddev.com/ai/frontier-ai-models-haemorrhage-sensitive-data