Thu Dec 29 10:23:29 EST 2011
Design for robustness
The project I'm currently working on seems to have a huge amount of
code dedicated to robustness and error handling / recovery. The main
problem being that all those little patches and tweaks are distributed
all over the code, instead of being part of the design (make the
design robust first, then make it do what you need..)
Is there a way around this? How to really design good, robust code?
I'm thinking about Erlang's "let it fail" model, but how can you take
the gist of this and make it work in a small embedded C application?