Please log in to watch this conference skillscast.
But she also has good news - production can contain multitudes, including features you aren’t ready to turn on or activate yet. You can hide in the dark and do integration testing at the same time.
It's simplistic to say that you should just kill the idea of a staging server and do everything in production. There are obviously problems with that - you need to do unit testing, you need to avoid things that will take down a service, you may need to do essential cutovers. But it's worth examining what benefit you're getting from staging and whether you could re-allocate that effort.
Join Heidi for an exploration of the ways that you might be able to kill staging and perform better.
What is the actual value of a staging environment?
What are some questions to ask about why we have staging?
How can I re-engineer releases to save costs?
YOU MAY ALSO LIKE:
- Go Faster, Be Safer: Release Velocity and Psychological Safety (SkillsCast recorded in February 2021)
- Accessibility Testing: Why and How to involve People with Disabilities (Online Meetup on 28th October 2021)
- Who Tests Their Cloud Code Anyway? (SkillsCast recorded in September 2021)
- TPP: From Dumb, to Specific, to Generic (SkillsCast recorded in July 2021)
All The World’s A Staging Server
Heidi Waterhouse is Transformation Advocate with LaunchDarkly. She delights in working at the intersection of usability, risk reduction, and cutting-edge technology. One of her favourite hobbies is talking to developers about things they already knew but had never thought of that way before. She sews all her conference dresses so that she's sure there is a pocket for the mic.