From e1eb0ad413248ee27848f713db76fadde488c9d7 Mon Sep 17 00:00:00 2001
From: Expo on server <expo@expo.survex.com>
Date: Tue, 5 Mar 2024 16:45:25 +0000
Subject: [PATCH] Legacy Displacement - online edit of
 handbook/troggle/trog2030.html

---
 handbook/troggle/trog2030.html | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index d18be2cc3..77d19e121 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -20,6 +20,9 @@
 <p>I don't think writing our own object/SQL code is sensible:
 there is such a lot going on we would create a large volume of software even if we stick close to the metal.
 [I could well be wrong. That is Option 1.]
+  
+  <h3>[ Update March 2024 ]</h3>
+"Legacy displacement" is now a fairly mature part of software engineering, though most computer science graduates won't have heard of it. There are standard ways of partially and incrementally retiring old systems and replacing them, while maintaining a live service to users throughout. See <a href="https://martinfowler.com/articles/patterns-legacy-displacement/">Legacy Displacement</a>.
 
 <h3>Option 2</h2>
 <p>