1,009 karma · joined January 30, 2013
At the end they could choose to let the team be less productive. Business should already assume that they may lose an employee at anytime, or roadblocks may come up, so if they're assuming the teams are always going to be at 100%, that's probably not realistic.
The business could also: hire another manager, or promote someone whose been looking for an opportunity to learn to manage. If they do want to shift the load to other existing employees, ideally the business is structured so that other managers aren't at 100% capacity and can help fill-in temporarily. That's still a form of "picking up the slack", but if it's planned for, it's usually less an issue.
That might change if there was more dedicated bike lanes.
Except that could kill your Nintendo switch, and it's not like Nintendo is going to change how their hardware works on something that's already been released to the masses.
For languages like Python for example, this is a big issue, and reason why alternative concurrency patterns to async/await haven't made much progress.
I think your challenge for virtualenvs would be that virtualenvs generally are not relocatable, as they hardcode absolute paths within the generated scripts (eg: venv/bin/activate`).
It used to be bandits raiding caravans, and now it's criminals raiding trains, front porches, etc.
It all depends on what the actual "airplane" (product) that's being built is.