How Complex Systems Fail(how.complexsystems.fail)
how.complexsystems.fail
How Complex Systems Fail
https://how.complexsystems.fail/
4 コメント
Aww, missed opportunity to have fun with virtual hosts as https://why.complexsystems.fail/ is currently nxdomain
I would have put up something that returned an <ol> akin to:
1. Cert expiry
2. DNS (or, is the current state of affairs a meta joke?!)
3. Firefall Rules
I would have put up something that returned an <ol> akin to:
1. Cert expiry
2. DNS (or, is the current state of affairs a meta joke?!)
3. Firefall Rules
Definitely some good reminders in there!
> But the converse: that successful outcomes are also the result of gambles; is not widely appreciated.
This statement however I would challenge: There is the whole ‘build fast and break shit’ culture that bets exactly on that outcome.
> But the converse: that successful outcomes are also the result of gambles; is not widely appreciated.
This statement however I would challenge: There is the whole ‘build fast and break shit’ culture that bets exactly on that outcome.
> There is the whole ‘build fast and break shit’ culture that bets exactly on that outcome.
Mark Zuckerberg was 13 when this was published, so I'm not sure that's accurate
Mark Zuckerberg was 13 when this was published, so I'm not sure that's accurate
Now, seeing that up close as a loner engineer gave me nightmares and inspired me in developing the technology for my startup. I’m just one guy so I limit complexity, write as little code as possible, and protect myself like a paranoid person. Basically, I see the primary value I can deliver from an engineering perspective is solving my domain as much as possible while limiting the scope as much as possible. Then when scaling, the costs/risks presented in this article are delayed as much as possible. It’s not always possible because some domains touch the real world too much but I see competitors in my field not heed this, and they’re starting to topple over in my opinion.