From 8bf6ae1488155dc1b61723604e05c0621409925e Mon Sep 17 00:00:00 2001 From: Philip Date: Tue, 7 Jan 2025 20:16:32 +0000 Subject: [PATCH] link to Mistakes engineers make in large established codebases - online edit of handbook/troggle/trognotes.html --- handbook/troggle/trognotes.html | 1 + 1 file changed, 1 insertion(+) diff --git a/handbook/troggle/trognotes.html b/handbook/troggle/trognotes.html index 54f7aa6c0..bd3478e64 100644 --- a/handbook/troggle/trognotes.html +++ b/handbook/troggle/trognotes.html @@ -67,6 +67,7 @@ the 2030 plan, architec the characteristics of code and of organisations that mean that it is a good idea to give up, and if so how to manage the rewrite. The answers are "almost never" and "don't": as explained in this summary of the book 'Kill it with Fire'. +

"...you cannot split up a large established codebase without first understanding it. I have seen large codebases successfully split up, but I have never seen that done by a team that wasn’t already fluent at shipping features inside the large codebase. You simply cannot redesign any non-trivial project ... from first-principles", Mistakes engineers make in large established codebases, Sean Goedecke.

Replacing old systems, and changing their architecture, while keeping them operating continuously, is now a well-understood