4 ms·
These seem like a good set of rules to follow. I would also add that in my experience once you get burned a time or two in production you start to develop a hea
by tudelo 6y ago
These seem like a good set of rules to follow. I would also add that in my experience once you get burned a time or two in production you start to develop a healthy level of paranoia and skepticism towards the code you write. I'm not sure if that step can be skipped, realistically we all create a dumpster fire here and there anyways. A healthy code review process helps as well.
- twy30 6y agoThank you. I like your idea. Let me try putting it into a bullet point form: * Get/give healthy feedback to mitigate against tunnel vision or unknown unknowns. * Learn from failures and mistakes.