Work loudly
In an office, some visibility is free. Go remote and it's gone. Working loudly shows your impact as you do it, not in a status update nobody reads.
In an office, some visibility is free. Go remote and it's gone. Working loudly shows your impact as you do it, not in a status update nobody reads.
Most 1:1s waste your team's only protected synchronous time on status updates. Here's how to run ones worth showing up for.
My book has a linter, ~5,500 automated checks, and a Pandoc pipeline that rebuilds five formats (EPUB, Kindle, paperback ×2, and web) on every git push. For a book one person wrote. Here's how I built and published it the way I ship software.
Call it taste, culture, or zen. Every organization has shared assumptions that guide decisions and resolve ambiguity in pursuit of its mission.
How GitHub used issues and chat for async communication: fifteen rules that eliminate the 'you had to be there' problem in corporate workflows.
No coding required. A plain-English guide to GitHub issues, pull requests, Markdown, and notifications for product managers, designers, legal, and ops.
How I used Docker Compose, Ansible, and Caddy to re-over-engineer my network setup for easier maintenance, treating my Raspberry Pi like cattle, not a pet.
When knowledge lives in people's heads and inboxes, it doesn't scale. Giving decisions and processes URLs makes context discoverable, async, and opt-in.
Async is what makes remote work actually work. It produces better outcomes, improves work-life balance, and makes room for flow by moving past Cold War-era workflows.
Out now
OpenandAsync
The collaborative software development playbook for remote and distributed teams. Drawing on over a decade at GitHub. On Kindle, Apple Books, Kobo & more.
Buy it for $9.99 (opens in a new tab)Surprises break trust faster than setbacks. If something would surprise someone when they find out later, tell them now, not once you have a fix.
AI tools are only as good as the docs you feed them. Bold text isn't a heading to a model. Here's the fix, plus two free converters.
The ebook meets the Web Content Accessibility Guidelines (WCAG 2.1 Level AA): Markdown won't let me fake a heading, and a browser audits every build. axe-core under Playwright catches what Markdown can't check, like color contrast, and nobody had to schedule a week for it.
Like what you read? Subscribe via RSS to get notified when new posts are published.
In thirteen years at GitHub I was part of 25 reorgs, almost one every six months. Reorgs are a constant in tech, not a crisis. Here's how to navigate them.
AI-augmented program management grows out of async-first, engineering-inspired workflows. It amplifies human judgment instead of replacing it.
Nobody's tracking your wins for you. How to keep a brag doc in five minutes a week, what makes a good entry, and how it builds your promotion case.
Announcing noagendanomeeting.net, a single-page site arguing that every meeting deserves an agenda and most meetings should be a document instead.
I asked Copilot to add agentic workflows to my repo. It wrote this post instead: AI coding agents work best through pull requests and code review.
When I joined GitHub in 2013, I found a company that had rethought how work happens. Thirteen years later, those lessons still shape how I work.
Set up LanguageTool as a free, open-source Grammarly alternative that runs locally on your Mac. No subscription required.
Silencing dissent erodes trust, invites negativity, and stifles learning. The best leaders embrace transparency instead.
What if we applied open source's cathedral vs. bazaar metaphor to management? Cathedral managers control; bazaar managers empower.
How GitHub turned its guiding communication principles into prescriptive practices to manage internal signal-to-noise ratio.
Like Toyota's andon cord, transparent collaboration lets anyone stop the line when they spot a problem in knowledge work.
Async communication is like gzip compression for humans: more processing up front, but greater throughput with fewer packets.
Pull requests record what changed, who changed it, why, and what else was considered. Treat every PR as a time capsule for future contributors.
Write dates unambiguously, include time zones, and build in breaks. Small scheduling choices make distributed teams feel included.
Most meetings are just information downloads that could've been a doc. Treat them as an escalation based on complexity, not the default starting point.
A battle-tested template for handing off your work before extended leave, so your team stays unblocked and nothing falls through the cracks.
If issues, pull requests, and project boards are the best way to develop software, should they not also be the best way to manage software development?
How to build 404 pages for Jekyll and GitHub Pages that suggest the closest valid URL, using Levenshtein distance and your sitemap.
Seven core responsibilities that define the corporate Chief of Staff role, from tactical office management to strategic advising.
Great leaders don't just communicate decisions. They explain how and why. Without that context, every decision sounds like "because I said so."