Immutable infrastructure / functional programming / crash-only code. In conjunction with lots of docker, ansible, studying FP, and trying to adopt these princip

Immutable infrastructure / functional programming / crash-only code. In conjunction with lots of docker, ansible, studying FP, and trying to adopt these principles in all my main languages (python, go, c, c++, bash) Those 3 ideas all kind of mushed together radically changed my overall approach to development. What do they all have in common? Avoiding complex state. State is hard to reason about. Each piece of state that can interact introduces combinatorially-growing complexity. Crash-only code may seem like the odd one out but think about it: if your program dying at literally any point has the potential for data corruption, you probably have some sort of issue with state management. I guess you could call it anarchy coding, because it tries to completely eliminate state ;)