🧠Knowledge Series #39 - How do development environments work?
Everything you need to know with real world examples from Slack, Spotify and more
🔒The Knowledge Series helps you plug the gaps in your tech knowledge so that you feel more confident when chatting to colleagues. Clearly explained in plain English. One topic at a time. So far, the collection includes APIs, front end development, SDKS, mobile apps, passkeys, headless architecture and payments explained - with more topics added every week.Â
If you’re a free subscriber and you’d like to upgrade to unlock them you can do so below. Or you can learn more about what you get with paid access here.
Hi product people 👋,
One of the quickest ways to make building products more difficult is to add countless development environments. Pre-production, dev-staging1, dev-staging2…if you’ve ever had the experience of working at a company that is burdened with too many environments you’ll know how difficult it can make actually getting features released into the hands of customers!
In this Knowledge Series, we’re going to take a look at the different types of development environments that are commonly used during the product development process. We’ll explore what they are, why they exist and whether they need to exist at all.
We’ll also share some important terminology worth knowing along with some insider insights from top tier companies like Slack and Spotify so that the next time someone brings up the topic of development environments, you’re fully up to speed with the essentials.
Coming up:
What do we mean by a development environment?
How do they work?
Do you really need a staging environment? Some alternative approaches to consider.
What are environment variables? Some real world examples explained.
Case studies: lessons from top tier tech companies including Slack, Uber and Spotify
Tools and terminology - IDEs, environment variables, VCS, containers and other terminology explained
