New stuff, or important features, are scary, and that means we move slower to avoid failing.
The fix is to embrace failure, fail fast, and often and then have systems to correct.
Making a payment system is much easier if you know QA, tests, code reviews will verify it for you, or if you do gradual deployment with monitoring, at least only a few customers will experience the problem.
I’ve always measured this as confidence.
New stuff, or important features, are scary, and that means we move slower to avoid failing.
The fix is to embrace failure, fail fast, and often and then have systems to correct.
Making a payment system is much easier if you know QA, tests, code reviews will verify it for you, or if you do gradual deployment with monitoring, at least only a few customers will experience the problem.
let’s make systems were we can be fearless. :)
Yes, good point! It's easier to get started with something if you know that things won't fall apart the second you make a mistake :)