debugging everything
What is debugging, really? I’ve thought about it for most of my life and never really come up with a satisfactory answer until today.
What is debugging, really? I’ve thought about it for most of my life and never really come up with a satisfactory answer until today.
A hallmark of a healthy company is keeping incentives aligned with ownership. The only way to scale this is to focus on alignment, not control.
In a small & fast engineering team, it’s challenging to quantify work being done. There’s so much to do, and it’s difficult to categorize. How can you determine your capacity for addressing your strategic roadmap when stakeholders ask about it?
Patrick O’Keefe of the long-running show Community Signal asked me to join him in a discussion that ranged from private equity buying community software, community data ownership, and the stakeholder challenges of community software roadmaps.
Building on the Web these days often feels like a game where you see how much weight you can put in a boat before it sinks, but you get $1 for every pound you add instead of how many days it stays afloat.
Software building is a team activity, and QA is an indispensable stakeholder on a well-functioning team.
Have you ever noticed nearly all Web software is feudalistic? I share three important pieces from academics that capture the issue.
Moments worthy of victory laps come from stories which have a beginning, middle, and end. If you’re not actively communicating these stories to a team, eventually startup-era victory laps fade into memory.
10% of all commits on the decade-old project are now mine from this past month. So, things are moving briskly.
A week ago I forked a decade-old open source project and Nitro Porter was born.
This is a brief technical review of open source search index products currently available, summarizing what I learned about them in a couple days of research.
A moment of conceptual breathing room by putting forward a well-articulated, divergent view could save a ton of resources later.
I recently read “Why I wouldn’t invest in open-source companies, even though I ran one” by Wolfram Hempel and started to write a very long comment, but decided I’d just publish my own counterpoint instead.
I’m lately watching The Great British Bake Off. When I thought about why you couldn’t do a similar show about programming, I realized the hurdles to televising it are the same hurdles teams face anyway.
I don’t think many of us understand what a community is or how to support one. We’ve built a lot of software to help people talk, and very little to help them build community.
Are you old enough to remember Firefox 2.0? It was a huge deal. Why did semantic versioning kill “big deal” releases and what could we do instead?
The myth of the “10x Developer” is rooted in pure technical fluency and short-term growth metrics, and it’s a dangerous narrative to sustainable teams and products.
Offering community managers a forum to build a community is like giving a project manager a kanban board. Yes, they can make it work. But is there really a “kanban market”?
What is software development really if not a sprawling, borderless puzzle for which the lid with the big picture on it is long gone? To me, it seems obvious that the biggest hurdle to team-based software development is how difficult it is to communicate well.
The greatest sin of any developer is thinking they are cleverer than the users of what they build. “I can guess what you want.” In truth, guessing what someone wants is far easier than helping them achieve what they actually want.