Tag
8 articles tagged #Engineering.
P.01Trunk-based development wins on speed and CI/CD fit for most teams. Git Flow still earns its keep for versioned software. The verdict, by criterion.
P.02The order you hire your first 10 engineers matters more than the headcount. How to sequence the hires, what ratios work, and the mistakes that slow teams.
P.03SOC 2 is a CPA's attestation report, not a certificate. The controls engineering teams implement, how Type 1 and Type 2 differ, and what audits typically cost.
P.04Trunk-based, Git Flow, GitHub Flow: here is the simple Git workflow that works for teams under 10, why Git Flow struggles at that size, and the mistakes to avoid.
P.05Every engineering team faces build vs buy decisions constantly. Here's a practical framework for making these decisions without analysis paralysis.
P.06Measuring developer productivity is notoriously difficult. DORA and SPACE frameworks offer research-backed approaches, but implementation is where most teams fail.
P.07Every codebase carries technical debt; the difference is whether you manage it intentionally. Here is how to identify, prioritize, and pay it down.
P.08Splitting a growing blog into its own repo, linked by a Git submodule, fixes merge conflicts and CI noise. Here is our exact setup for 130+ posts.