MATT NIGH'S BLOG
Home
Writing
Home
Writing
Archive
Writing.
Every essay, note, and external piece I've published. Filter by tag.
All
30
engineering
18
ai
11
management
6
copilot
3
favorite
2
personal
2
neurodiversity
2
future-of-work
1
prompts
1
template
1
productivity
1
resources
1
reading
1
chief-of-staff
1
Run multiple agents at once with /fleet in Copilot CLI
↗
APR 2026
ai
engineering
copilot
TL;DR ↗
/fleet dispatches multiple sub-agents simultaneously, with an orchestrator planning work decomposition and coordinating parallel execution
Well-structured prompts with specific deliverables and clear file boundaries enable effective parallelization
Sub-agents share a filesystem but lack direct communication — declaring dependencies and partitioning files prevents conflicts
Custom agents defined in .github/agents/ can be specialized for different tasks with different models and tool access
Fleet maximizes efficiency for multi-file refactors, documentation generation, and feature implementations spanning API, UI, and tests
How to write a great agents.md: Lessons from over 2,500 repositories
↗
NOV 2025
engineering
ai
copilot
TL;DR ↗
A great agents.md file is the key to getting useful output from AI coding agents
Analyzed over 2,500 repositories to find what makes instruction files effective
Successful files are specific about architecture, conventions, and testing expectations
Clarity and structure in your instructions directly correlates with agent output quality
Playbook series: Right-fit tooling
↗
NOV 2025
ai
engineering
TL;DR ↗
The right AI tools match your team's actual workflows, not the latest hype
Evaluate tools against real use cases, not feature checklists
Start narrow with one tool well-integrated, then expand based on feedback
Tool selection should involve the developers who will actually use them
Playbook series: Executive support
↗
NOV 2025
ai
engineering
TL;DR ↗
Executive support is the single biggest predictor of AI adoption success
Leaders must visibly champion AI, not just approve budget for it
Exec sponsorship creates psychological safety for teams to experiment
Top-down and bottom-up alignment accelerates meaningful adoption
How Copilot helps build the GitHub platform
↗
NOV 2025
engineering
TL;DR ↗
GitHub uses Copilot coding agent internally to build and maintain the GitHub platform
AI-assisted development has shifted how GitHub's own engineers work day-to-day
Real-world internal usage surfaces insights that shape the product for all developers
Dogfooding at scale proves the value and reveals the friction points
Playbook series: Creating clear AI policies and guardrails
↗
OCT 2025
ai
engineering
TL;DR ↗
Clear AI policies remove ambiguity and give teams confidence to move fast
Guardrails should enable experimentation, not block it
Address data privacy, IP, and acceptable use upfront to prevent paralysis
Policies should evolve as the technology and your team's maturity grow
Playbook series: Why you need a DRI for your AI program
↗
SEP 2025
ai
engineering
TL;DR ↗
AI adoption without a dedicated owner drifts and stalls
A DRI (directly responsible individual) keeps the AI program focused and accountable
The DRI bridges the gap between executive vision and on-the-ground execution
Ownership clarity prevents duplication of effort and conflicting initiatives
Playbook series: Fostering AI learning opportunities
↗
SEP 2025
ai
engineering
TL;DR ↗
AI fluency requires ongoing learning opportunities, not a one-time training
Create safe spaces for experimentation where failure is expected
Pair structured programs with organic peer-to-peer knowledge sharing
Learning is most effective when tied to real work, not hypothetical exercises
Playbook series: Activating your internal AI champions
↗
AUG 2025
ai
engineering
TL;DR ↗
Internal champions are your secret weapon for AI adoption at scale
Find advocates who are already experimenting with AI organically
Empower champions with resources, visibility, and a feedback loop to leadership
Grassroots enthusiasm drives adoption faster than top-down mandates
GitHub’s internal playbook for building an AI-powered workforce
↗
JUL 2025
engineering
TL;DR ↗
GitHub scaled AI fluency by focusing on people and culture, not just deploying tools
Successful AI adoption requires executive sponsorship, a DRI, and internal champions
Clear policies and guardrails give teams confidence to experiment with AI
Continuous learning and right-fit tooling beat one-size-fits-all mandates
The art of engineering team focus: less is more
↗
FEB 2025
engineering
TL;DR ↗
Teams that try to do everything end up shipping nothing well
The key to shipping more is ruthlessly reducing work-in-progress
Leaders must protect focus by saying no to low-impact requests
Less parallel work means faster delivery and happier engineers
Why developer satisfaction is your best productivity metric
↗
DEC 2024
engineering
TL;DR ↗
Developer satisfaction is the strongest proxy for engineering productivity
Happy developers ship faster, stay longer, and produce higher-quality code
Measure satisfaction directly instead of relying on output metrics like lines of code
Friction, tooling gaps, and unclear priorities are the biggest satisfaction killers
Technical Stewardship: A Must-Have for Engineering Managers
↗
NOV 2022
engineering
TL;DR ↗
Engineering managers must act as stewards and architects of their areas of responsibility
Technical stewardship means owning the health of your systems, not just your people
Managers who ignore technical debt create compounding problems for their teams
Stewardship bridges the gap between business priorities and technical sustainability
How to Create User Personas for Data Engineering
↗
NOV 2022
engineering
TL;DR ↗
Data engineering teams benefit from creating user personas for their stakeholders
Understanding who consumes your data pipelines shapes better design decisions
Personas clarify priorities when competing requests come from different teams
Treat internal consumers with the same rigor as product teams treat external users
I’m an Engineering Manager who can’t code
↗
DEC 2021
engineering
favorite
management
TL;DR ↗
You don't need a software engineering background to be an effective EM
Being 'technical' means systems thinking and understanding complexity, not writing code
Focus on what makes work visible — you can't ignore reality when everything is written down
Managed 50+ developers directly and oversaw 450+ without ever writing meaningful code
Your first 90 days as an Engineering Manager
↗
NOV 2021
engineering
management
TL;DR ↗
Your first 90 days set the tone for your entire tenure as an engineering manager
Listen first — understand the team's pain points before proposing changes
Build trust through 1:1s, transparency, and following through on commitments
Quick wins build credibility, but avoid making sweeping changes too early
How COVID-19 Has Changed the Future of Low-Code
↗
JUN 2020
engineering
TL;DR ↗
COVID-19 accelerated low-code adoption as organizations needed to build solutions fast
Speed-to-market became critical when traditional development timelines were too slow
Low-code democratized development, empowering non-engineers to solve urgent problems
The crisis proved that pragmatic tooling choices matter more than technical purity
3 Common Pitfalls of New Engineering Managers
↗
FEB 2020
engineering
management
TL;DR ↗
New engineering managers often fall into avoidable traps in their first year
Avoid doing the work yourself instead of empowering your team
Don't skip 1:1s or treat them as status updates — they're for your people
Recognize that the skills that got you promoted aren't the skills you need now