| ▲ | toss1 9 hours ago | |
>> "the processes that led to an update with a latent defect reaching production deserve a long, hard look. " Indeed they do deserve a long hard look. Toss1's conjecture: We are now seeing the beginning of an era of latent technical debt brought about by too rapidly firing developers and switching to AI code generation (nevermind vibe-coding). Even well-prompted and well-monitored by top expert coders and architects, there is latent technical debt, and it is more diffuse, harder to find, and harder to fix, and will start showing up in outages like this. (It first seemed the ATC outage was another example, but it now seems it was merely the usual management incompetence if not an outright manipulative ploy to 'justify' more spending for a single-bid contract [0]) [0] https://ajsignalnotnoise.substack.com/p/faa-air-traffic-cont... | ||
| ▲ | nialse 5 hours ago | parent | next [-] | |
Suggested reformulation of the conjecture: "Complex systems are kept stable by organisational knowledge of their weaknesses and how to compensate for them. Organisational change erodes this knowledge while the underlying weaknesses remain. A previously stable system thus becomes increasingly vulnerable to failure." When it is said that software is a solved problem, what is ment by that is really that programming, typing up the code, is a solved problem. Software engineering, systems architecture and the complexities in distributed systems are not, while leads to confusion when not being mindful of the difference. | ||
| ▲ | toss1 an hour ago | parent | prev [-] | |
And so we now have additional mysterious banking system issues today... Hmmm | ||