works on my machine
The classic complaint when software runs for one developer but fails elsewhere because of hidden differences between machines.
In more detail
It is almost always an isolation failure: something installed on one machine is missing from the declared dependencies. Declaring dependencies exactly and isolating them at run time removes it, and containers make the isolation cheap. A new team member should be productive with one documented command.
Related terms
- dependency declaration — Listing every dependency an app needs, with exact versions, in a manifest, and isolating the app so nothing else leaks in at run time.
- configuration drift — The slow, unrecorded way machines end up with different versions and settings from each other.
- dev/prod parity — Keeping development, staging and production as similar as possible in timing, people and tools.
Taught in
- Codebase And Dependencies — DevOps & Site Reliability Engineering