FDD - Failure Driven Development

2026-05-24

We can now stop worrying about “code” and worry a lot more about “design”. That’s the main point of Failure Driven Development.

PBP is one of the tools for FDD - snap parts together like LEGO blocks and see if you like the result. If not, knock it all down and start all over again. Repeat numerous times.

I’ve been using Claude to argue with me. To be a foil that espouses the “functional approach” to writing code.

The biggest fall-out of these brain-storming sessions is the observation that PBP goes a step further than Erlang by providing “topology blindness”. It is a core term in the PBP/0D vocabulary, describing the property that components do not know their own neighbors and that wiring is controlled by the parent container rather than by the components themselves.

To implement topology blindness, it is more convenient to roll your own multi-tasking kernel, instead of relying on existing thread libraries, and, you need to create a system of two-tier “parts” that I call Container parts and Leaf parts.

See Also

Email: ptcomputingsimplicity@gmail.com
Substack: paultarvydas.substack.com
Videos: https://www.youtube.com/@programmingsimplicity2980
Discord: https://discord.gg/65YZUh6Jpq
Leanpub: https://leanpub.com/u/paul-tarvydas
Twitter: @paul_tarvydas
Bluesky: @paultarvydas.bsky.social
Mastodon: @paultarvydas
(earlier) Blog: guitarvydas.github.io
References:https://guitarvydas.github.io/2024/01/06/References.html

Paid subscriptions are a voluntary way to support this work.