The Staging Dichotomy with Senthil Padmanabhan

/*! elementor - v3.5.5 - 03-02-2022 */ .elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#818a91;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#818a91;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}

Serious software projects require several environments.  Your production environment is obviously mission critical.  A staging environment is also necessary to perform validation and regression testing before taking the risk of pushing an update to production.  Best practices and approaches for managing these and other environments vary from organization to organization.

In some sense, different software systems should be expected to have unique needs.  Yet certain commonalities and wisdom can be gained from observing high scale success stories.

In this episode, I interview Senthil Padmanabhan about how eBay turned around an impeding staging environment into its biggest asset for developer productivity.