Good due diligence looks boring from the outside
A due diligence review that reads like a list of everything wrong with a codebase isn't doing its job. The actual question is narrower: can this team, this candidate, or this system support the outcome someone is about to bet money, equity, or a hire on?
That question matters the same way for startups, agencies, hiring teams, and acquirers. It's also why I keep public artifacts up in the first place — blog, open source, projects, and journey each cut down on ambiguity in a slightly different way.
What a useful review actually checks
Architecture quality measured against the actual business ambition and team size, not an abstract best-practices checklist.
Delivery maturity: how an idea actually gets from a ticket to production, and what breaks along the way.
Evidence of ownership and judgment. Can this person explain a decision, not just defend it.
Whether the system or the candidate can grow without quietly accumulating fragility nobody notices until it's expensive.
How public work helps
Projects show whether someone can connect architecture decisions to outcomes that actually mattered.
Writing shows how someone reasons when nobody's grading them for it.
Open source shows interface taste, and whether they stuck around to maintain what they shipped.
That overlap is why this topic connects to What Makes Open Source Packages Useful Instead of Decorative and Mentoring Engineers Through Code Review Without Slowing Delivery.
What weak diligence gets wrong
It collects keywords instead of testing judgment.
It mistakes a polished deck for a system that actually holds up in production.
It ignores whether the work in front of it even matches the scale of the opportunity.
It treats hiring, advisory work, and architecture risk as three separate reviews when they're really one.
What good diligence buys you
Due diligence exists to produce a better decision, not a longer document. A review that's done its job leaves everyone clearer on fit, risk, and the next step, not just more cautious. If you need that kind of read on a role, project, or partnership, contact me directly.
