TalksEngineering in production50 minEarlier version
Engineering Without a Safety Net: Modernizing a 13-Year-Old System Without a Rewrite
An earlier version of this talk (PHP Tek 2027 CFP).
PHP Tek 2027 submission cut of Engineering Without a Safety Net. Reframes the case study for mature PHP/Laravel and mixed-stack maintainers, emphasizes mapping inherited risk, prioritizing customer journeys and observability, adding safeguards without a rewrite, and expands the intended session to 50 minutes. Original and JSWorld 2027 versions preserved. The talk has moved on: book Engineering Without a Safety Net: Where It Works and Where It Hurts.
The premise
What happens when a 13-year-old SaaS platform serves tens of millions of users, but the engineering safeguards you'd expect at that scale never quite caught up?
You inherit a system built under years of changing constraints. Testing gaps, undocumented assumptions, limited observability, and architectural decisions that once made perfect sense now interact in ways nobody fully understands. Meanwhile, customers depend on it, revenue keeps flowing, and the business cannot stop shipping.
This talk follows the practical challenge of improving reliability in an established production system with a small engineering team and an enormous potential blast radius.
We'll explore how to build a useful mental model of an unfamiliar architecture, distinguish tolerable technical debt from dangerous blind spots, and decide where testing, instrumentation, and safer releases provide the greatest return. Through real production lessons, we'll examine why healthy dashboards can conceal serious failures, how to prioritize critical user journeys, and how to introduce safeguards incrementally without attempting a rewrite.
Whether you're maintaining a mature PHP application, a Laravel monolith, or a mixed web stack, the challenge is the same: make the system safer while keeping the product moving.
Audience: Intermediate developers familiar with maintaining production applications. No framework-specific knowledge required.
Takeaway: A practical, risk-based approach to modernizing established software without needing a clean slate, a large team, or an unlimited budget.
Who it's for
Intermediate engineers maintaining established production web applications, including PHP and Laravel; no framework-specific knowledge required.
You leave with
- Build a useful risk model for inherited architecture and undocumented assumptions
- Prioritize observability around critical user journeys, not only healthy dashboards
- Add testing and release safeguards incrementally without a rewrite
How this talk evolved
- PHP Tek 2027 CFP
Engineering Without a Safety Net: Modernizing a 13-Year-Old System Without a Rewrite
PHP Tek 2027 submission cut of Engineering Without a Safety Net. Reframes the case study for mature PHP/Laravel and mixed-stack maintainers, emphasizes mapping inherited risk, prioritizing customer journeys and observability, adding safeguards without a rewrite, and expands the intended session to 50 minutes. Original and JSWorld 2027 versions preserved.
- JSWorld 2027 CFP
Engineering Without a Safety Net: Where It Works and Where It HurtsCurrent
Evolves the original discussion of deferred engineering practices into a production case study of a 13-year-old bootstrapped SaaS serving tens of millions of monthly users and generating tens of millions in annual revenue. Traces how reasonable decisions under earlier constraints ripple and compound into today's architecture and operational risk. Strengthens the focus on observability, critical user journeys, incident diagnosis, recovery verification, and prioritising incremental safeguards while continuing to ship. Title and abstract match the JSWorld 2027 CFP submission.
- 2025
Where it's been delivered
No sessions of this version are on record.