Uploaded April 2025 | Updated November 2026, 3 hours ago
Many developers evoke the mischievous spirit and day-to-day burden of technical debt to explain the misfortunes and troubles of their codebase and delivery. While unmanaged technical debt weighs down many codebases and exerts drag on their schedules, it is more often an effect than a cause.
In this talk, we will look at what is and is not meant by technical debt — and other metaphors — with a view to properly attributing the root and recurring cause as technical neglect than technical debt. Without seeing technical neglect for what it is, we will continue to misattribute our problems to an effect rather than a cause.
This talk was recorded at Craft Conference 2024.
The event was organized by CraftHub.
You can watch the rest of the conference talks on our channel.
If you are interested in more speakers, tickets and details of the conference, check out our website: craft-conf.com
If you are interested in more events from our company: https://crafthub.events/
Many developers evoke the mischievous spirit and day-to-day burden of technical debt to explain the misfortunes and troubles of their codebase and delivery. While unmanaged technical debt weighs down many codebases and exerts drag on their schedules, it is more often an effect than a cause.
In this talk, we will look at what is and is not meant by technical debt — and other metaphors — with a view to properly attributing the root and recurring cause as technical neglect than technical debt. Without seeing technical neglect for what it is, we will continue to misattribute our problems to an effect rather than a cause.
This talk was recorded at Craft Conference 2024.
The event was organized by CraftHub.
You can watch the rest of the conference talks on our channel.
If you are interested in more speakers, tickets and details of the conference, check out our website: craft-conf.com
If you are interested in more events from our company: https://crafthub.events/
![Designing Fault-Tolerant Software with Control System Transparency - Jon Moore | Craft Conf 2024
Teams at NASA and JPL that create mission-critical software for spacecraft take a principled approach to fault tolerance. Lets see how those same principles, centered around a concept of transparency, can help us achieve reliability in pragmatic, modern software delivery settings.
As our society continues to depend more and more heavily on software, the need for that software to be reliable also increases. At the same time, the software systems we build as practitioners continue to become more and more complex, with many moving parts and unexpected, emergent behavior. How can those systems become as reliable and robust as the Voyager 2 deep space probe that made news recently and is still in service 46 years after its launch?
In this talk, well be drawing inspiration from an architectural paper that captures experiences from the aerospace industry. GN&C [Guidance, Navigation, and Control] Fault Protection Fundamentals by Robert D. Rasmussen describes four key principles for building fault-tolerant software, involving transparency of (1) objectives; (2) models; (3) knowledge; and (4) control. For each principle, well identify use cases from well-known software or protocols (e.g. HTTP) where we can see the principle in action; or, if the principle is not commonly applied, well describe how it might look in familiar settings like invoking RESTful or GRPC APIs.
This talk was recorded at Craft Conference 2024.
The event was organized by CraftHub.
You can watch the rest of the conference talks on our channel.
If you are interested in more speakers, tickets and details of the conference, check out our website: https://craft-conf.com/
If you are interested in more events from our company: https://crafthub.events/ Designing Fault-Tolerant Software with Control System Transparency - Jon Moore | Craft Conf 2024](https://i.ytimg.com/vi/huO9kKxdtKI/mqdefault.jpg)









