Not the OP, but it's pretty useful in my team, we all work on the same environment, with the same system dependencies, with no setup required on development machine (except the need for docker).
In the devcontainer you can run code snippets, use the system shell and access an execution environment close to production if well made.
It also allows to avoid (system) dependency conflicts between different projects you may work on.
As companies grow, they tend to move away from subjective performance reviews like that and toward more objective metrics. Otherwise, it's too easy for personal politics to contaminate the promotion process. Employees are incentivized to find whichever manager will give them 5 star reviews no matter what, and managers are incentivized to be that guy, because then they have access to the best employees. When a company is small, and everyone knows everyone, this is not an issue. But when 90% of the company is a stranger to you, you need more objective metrics to rely on.
I believe they already provided "Standard traceroute example", "Flyingroutes example (with protocol breakdown)" and "MTR example (with packet loss and timing statistics)".
> Google, Microsoft, Meta and Amazon all have net-zero emission targets which they take very seriously, making them "some of the most significant corporate purchasers of renewable energy in the world". This helps explain why they're taking very real interest in nuclear power.
Nuclear is indeed (more or less) zero-emission, but it's not renewable.
Thank you for the synthesis and link to the original article, it's a good read!
In the devcontainer you can run code snippets, use the system shell and access an execution environment close to production if well made.
It also allows to avoid (system) dependency conflicts between different projects you may work on.