In a 15-30 person engineering group, the first thing to break in an inherited, untested legacy system is rarely the build; it is the team’s ability to know which version of production exists. My position is unfashionable: scaling safety here starts with flag governance and deletion pressure, not with a…
-
-
Inherited an untested codebase What QA advice is obsolete now
You inherited an untested codebase at the worst possible moment: AI-assisted changes, dependency churn, and feature flag sprawl have made “just add tests later” more expensive than it was two years ago. My position is blunt: a QA engineer should stop chasing coverage first and should instead control change paths,…
-
Add feature flags to legacy code without rewriting everything
New development trends usually enter old codebases as slogans: add observability, adopt TypeScript, move to contracts, use feature flags. My position is stricter: a junior developer should introduce a trend first as a constraint around existing behavior, not as a replacement for it, because the old behavior is probably more…
-
Safety, Quality, and Compliance in Software Development
In modern software development, safety, quality, and compliance are no longer optional; they are fundamental to building reliable, trustworthy systems. From preventing catastrophic failures to meeting strict regulations, teams must design and implement processes that systematically manage risk. This article explores how to integrate safety, quality, and compliance into everyday…
-
Project Management Standards and Professional Bodies in Construction
Project management standards and professional bodies shape how complex projects are conceived, planned and delivered across industries. From global associations that define best practices to sector‑specific codes that regulate risk, these frameworks create a common language for stakeholders. This article explores how project management standards evolved, how institutes and professional…