Writing · Nº 041065 essays
The writing
Ideas from inside the work. Explore technology, entrepreneurship, and the practice of building things that last.
8 essays found · Page 1 of 1
Clear filtersStrategyWho Should Do Technical Due Diligence on a Code Acquisition?Your own engineers, a third party, or both? Here is who should do technical due diligence on a code acquisition, and the conflict of interest to avoid.StrategyWhat a Code Audit Cannot Tell YouA code audit reads the code, not the team, the roadmap, or the business. Here is what a code audit cannot tell you, and why buyers over-trust it anyway.AITechnical Due Diligence on an AI Codebase Is DifferentAuditing an AI or ML codebase in due diligence means checking data, models, and notebooks, not just code. Here is what technical due diligence must add.EngineeringAutomated Scan vs Expert Review for Code Due DiligenceShould code due diligence be an automated scan or a human expert review? The answer is both, in order. Here is how to sequence automated scan vs expert review.EngineeringHow Long Does a Code Audit Take? A Realistic AnswerHow long a code audit takes depends on scope, access, and depth. Here is a realistic breakdown from a one-day scan to a multi-week deep review.EngineeringGit History Red Flags in Vendor Code You Are About to BuyThe final snapshot hides the truth. Here are the git history red flags in vendor code that tell you what the seller does not want you to see.EngineeringHow to Review Contractor-Delivered Code Before You Accept ItAn agency or contractor hands you a repo and an invoice. Here is how to review contractor-delivered code before you accept it and own the mess.EngineeringHow to Review Code in a Data Room During M&AYou get read-only access, a deadline, and no git clone. Here is how to review code in a data room and still find what kills the deal.