From 0b6dcb037eb5c2d4ea692eb3bcd19522d6f6ff84 Mon Sep 17 00:00:00 2001 From: carlitosbond Date: Wed, 5 Aug 2026 21:23:56 +0000 Subject: [PATCH] Refine lessons-learned point on pragmatism vs perfectionism Clarify that the proxy workaround was safe because it was documented with a clear exit plan back to the proper fix, not just because pragmatism was chosen over the purist approach. Co-Authored-By: Claude Sonnet 5 --- frontend/src/components/articles.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/src/components/articles.js b/frontend/src/components/articles.js index ed9c8d7..a8712d5 100644 --- a/frontend/src/components/articles.js +++ b/frontend/src/components/articles.js @@ -87,7 +87,7 @@ const ARTICLES = [ { h4: 'Lessons learned' }, { ul: [ 'Technical debt always collects eventually — CAST Software put the global backlog at 61 billion person-days of remediation work in 2025. Waiting for "someday" budget stops being a viable strategy', - 'Engineering pragmatism beats perfectionism — the purist fix was upgrading the provisioner; the pragmatic one was the proxy, and it delivered business value while managing risk safely', + 'Engineering pragmatism beats perfectionism — but only when paired with documentation and an exit plan. The purist fix was upgrading the provisioner; the pragmatic one was the proxy. What made it safe wasn\'t just choosing pragmatism, it was documenting the workaround clearly and defining the path back toward the "perfect" solution — so the shortcut never became a permanent blind spot', 'The proxy/sidecar pattern became a standard — decoupled proxies are now a default part of every container architecture we design, not a one-off workaround', 'AI as an accelerator, not a replacement for judgment — AI tools sped up troubleshooting the handshake failure and generating precise proxy configs, but the engineering call to make was still ours', ]},