LeadDev
Online/Digital
We are a community of software engineering leaders that come together to learn and get inspired on all things team, tech, process, and personal development.
LeadDev has become an essential destination for anyone in tech and engineering who wants to scale themselves and create impact. When you plug in to LeadDev, you gain access to inspirational knowledge and thought-provoking advice on both perennial challenges and the issues of today. From practical ideas you can implement immediately, to future trends that will give you an electric advantage.
We provide this via a range of content that includes articles, thematic content series, video talks and panel discussions, written and delivered by the best voices in engineering. Source
Actions
Media Outlet details
| Scope | International |
|---|---|
| Language | English |
| Country | United Kingdom |
Similarweb UVM
|
Request pricing |
Comscore UVM
|
Request pricing |
Recent Articles
Search ArticlesStop asking engineers how many machines they need
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 8 minutes Key takeaways: Reasonable buffers, stacked across hundreds of teams, inflate total demand massively and untraceably. Ask product teams about growth, not machine counts, then translate that automatically into hardware. Tying forecasts to durable products and not projects cuts the process from months to about a month.
We built the platform. Nobody used it
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 7 minutes Key takeaways: Low adoption can be a trust problem and not just a communication issue. Training doesn’t fix broken trust. The real question is ‘what would make a skeptical engineer choose this again?’ Trust can come back through observing teams, opening the roadmap, and owning the failure, not new features.
How to lead a technical discussion
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 8 minutes Key takeaways: Leading a discussion means facilitating and not having all the answers. The real skill is making tacit knowledge visible then finding alignment, even on what nobody knows. Strong emotions carry real information. Objections become testable predictions. Most people picture building software as writing code, but it never was.
The engineer’s guide to building a software factory
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 7 minutes Key takeaways: Individual agents plateau at 20-30% gains, not the 2-3x teams expect. The fix is to use multi-agent loops with separated objectives, not one agent checklisting. Three loops lead: PR→merge, Ticket→PR, Alert→resolution, each with major measured gains. In conversations with hundreds of engineering leaders, I keep hearing the same pattern.
Returning to the IC track in the age of AI
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 7 minutes Key takeaways: A third of engineering managers are considering returning to IC work. The EM role has changed: more compressed, more expected, no consistent definition. Demand favors ICs with judgment plus AI fluency. Pick which seat you navigate the shift from.
We’re on call for code nobody wrote
You have 1 article left to read this month before you need to register a free LeadDev.com account. Key takeaways: Authorship, memory, and comprehension are gone. Only runtime behavior tells the truth now. Patching now accelerates exploitation: disclosure-to-exploit time dropped from 771 days to 4 hours. Stop gating for comprehension. Invest in detection and blast-radius containment instead. In 1563, Pieter Bruegel the Elder painted the Tower of Babel.
Cut AI-coding costs without slowing down
You have 1 article left to read this month before you need to register a free LeadDev.com account. Key takeaways: Budget caps don’t work, and most engineers never hit them anyway. A one-hour cache (not five minutes) can cut AI-coding costs by 10-15%. Show engineers their spend and measure cost per unit of shipped work. AI coding is amazing, but costs have really surprised all the engineering leaders.
28x more AI spend. Zero new innovation
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 2 minutes Key takeaways: AI spend jumped 28x in a year. Feature work stayed stuck at 58%. Only 6% of execs can identify AI ROI: faster output just piles up elsewhere. The fix? Track the innovation ratio, and deliberately reinvest freed-up capacity, or the org absorbs it. AI investment is accelerating far faster than engineering innovation.
We halved our continuous integration pipeline
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 8 minutes Key takeaways: A 64% CI speedup didn’t hold. Growth in tests, merges, and AI-assisted development outpaced the fix within months. Offloading the right tests beats chasing raw speed. Splitting critical from deprecated end-to-end tests cut runtime and flipped the pass/fail ratio almost overnight. CI speed needs an owner and a target, not a one-time fix.
Meta tried to shrink engineering teams around AI
You have 1 article left to read this month before you need to register a free LeadDev.com account. Estimated reading time: 3 minutes Key takeaways: Meta’s AI “pods” boosted code changes 220%, but shipped features rose just 36% while incidents jumped 40%. Across 500+ orgs, PR throughput rose 37% while developer experience actually fell. Right-sized teams are five to eight people, not smaller, and shrinking should come last, not first.