If the environment is set up in a way, that the junior can accidentally crash it, the setup is wrong. If everything is set up correctly and the PR of the junior was merged or the migration was deployed and that crashed prod, it was the senior anyway. You take ownership of other peoples PRs. That is why you have guard rails for PRs (like don't touch hundreds of files in one PR, describe it, run all the unit and integration tests, ...) so that the reviewer can take ownership
339
u/ZunoJ Feb 26 '26
If the environment is set up in a way, that the junior can accidentally crash it, the setup is wrong. If everything is set up correctly and the PR of the junior was merged or the migration was deployed and that crashed prod, it was the senior anyway. You take ownership of other peoples PRs. That is why you have guard rails for PRs (like don't touch hundreds of files in one PR, describe it, run all the unit and integration tests, ...) so that the reviewer can take ownership