February 2009
Beginner
222 pages
5h 23m
English
Content preview from 97 Things Every Software Architect Should Know
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 65. Your System Is Legacy; Design for It
Dave Anderson is a principal software engineer at Belfast software company Liberty IT, which supplies IT solutions for Fortune 100 company Liberty Mutual. Dave has more than 10 years' experience in the software industry with many leading-edge IT companies across several different industries and countries.
—Dave Anderson
EVEN IF YOUR SYSTEM IS BLEEDING EDGE and developed in the latest technology, it will be legacy to the next guy. Deal with it! The nature of software today means things go out of date fast. If you expect your system to go into production and survive, even for a few months, then you need to accept that maintenance developers will need to fix things up. This means several things:
Clarity: It should be obvious what role components and classes perform.
Testability: Is your system easy to verify?
Correctness: Do things work as designed or as they should? Eliminate quick and nasty fixes.
Traceability: Can Ernie the Emergency Bug Fixer—who has never seen the code before—jump into production, diagnose a fault, and put in a fix? Or does he need an eight-week handover?
Try to think of a different team opening up the codebase and working out what's happening. This is fundamental for great architecture. It doesn't have to be oversimplified or documented to the hilt; a good design will document itself in many ways. The way a system behaves ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.