Stage 2 · Lesson 10 of 10
Environments, releases, feature flags and incidents
Code usually moves through several , which are separate copies of the product. It starts on a developer's machine. It then goes to a shared staging environment for testing.
Finally it reaches production, where real users see it. A feature flag is a switch that lets a team code but turn a feature on only for some users. So "shipped" and "available to everyone" can be weeks apart.
Some teams release continuously, others on a schedule, and mobile apps also wait for app store review. An incident is an unplanned outage or serious bug that the team handles urgently. Afterwards they write a , a short report on what happened and how to prevent it.
Your role depends on all this: launches, published docs and announcements must match what users really see.
Common trapannouncing or documenting a feature because its merged, when most users still cannot use it.
A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock
Resources for this stage
Start with· follow one of these
- VideoFreeCrash Course Computer Science
CrashCourse · Beginner
Short free videos on how computers, networks and software work, pitched at beginners
- CourseFreeSelect Star SQL
Zi Chong Kao · Beginner
A free interactive SQL tutorial on real data, enough for product and docs analytics