shared_children

code for talk

Think of it as a controlled experiment. If the new hire (me) deploys a new feature and then sees the staging (or production) server “break” first hand, they gain valuable insight into how to fix problems in the future. With deployments happening continuously (automatically as soon as code is pushed), rather than a big-bang approach planned at 6:00 pm on a Friday when everyone might not be immediately available, things work (or break) fast. It is always easier to do quick fixes and deliver value incrementally. This “learning by doing” is the kind of knowledge that is extremely important but hard to learn from documentation or examples. No amount of training or simulations can compare to the real deal of deploying live code to really get a sense of how to handle a “crisis mode” situation.