Legacy Systems: Document Before You Change

Legacy Systems: Document Before You Change

Legacy systems often become difficult to change for one simple reason: nobody has a complete picture of how they work.The platform may be stable enough to run every day, but the knowledge needed to modify it is spread across old diagrams, scripts, support tickets,...
Legacy Systems: Document Before You Change

HLD vs LLD: What Each Document Should Do

High Level Design and Low Level Design are often discussed together, but they serve different purposes. Confusion between the two can lead to documentation that is either too vague to build from or too detailed to help decision-makers understand the architecture.A...
Backups Are Not the Same as Disaster Recovery

Logging and Monitoring: Design for Evidence

Logging and monitoring are often added after a system is built. That is backwards. If a service is important enough to run in production, the design should define what evidence is needed to operate it, secure it and investigate failure.Good observability is not about...