Thread by @dparzych

Production as an experiment lab @rmn #TrajectoryConf

Shifted mentality from "I can fix it" to having to understand what engineers were doing and how pieces work together. @rmn #TrajectoryConf

Test in prod–can only verify if systems are working as intended if you are testing in prod. Don't waste cycles creating exact clones. @rmn #TrajectoryConf

Test in prod doesn't mean release without testing. It's the opposite. Test in a more real environment before you release code. Extend SDLC beyond release. @rmn #TrajectoryConf

Progressive delivery–new label of bunch of things we've been thinking about. Canary deploys, segmentation of users, control of the blast radius. @rmn #TrajectoryConf

2 threats to availability–change to software or change to the environment. @rmn #TrajectoryConf

Your job isn't just to ship correct/working software. It is to deliver business/customer value. @rmn #TrajectoryConf

Test is about verifying, confirming and integrating. Experimentation is about discovering, learning, and changing. Experiments lead to new knowledge. Tests don't. @rmn #TrajectoryConf

@rmn referencing @nora_js "We can get more value talking about the process of automation than the actual automation."

Think about how a user request moves through your systems as a foundation to orchestrate experiments and measure them. @rmn #TrajectoryConf

Production is begging for experimentation. Thank you to people like @edith_h , @mipsytipsy and @nora_js for being pioneers in this field. @rmn #trajectoryConf