Depends on the business you’re in. Sometimes an “environment” is a rack (or 2) of servers and that might be 100k-400k/rack before space & power & bandwidth.
I agree /lives/ aren’t directly at stake, but depending on what your business is, /livelihoods/ are.
When you’re an entrepreneur and have a small team, each of them may have a family. As the leader you are responsible for running a profitable company that can pay its employees so their families can eat.
At the large company I work for my team’s product is B2B. When we go down, other businesses go down. The number of people affected is very high. Treating every incident like someone’s business is dependent on you and they have put their trust in you to support them is very sobering.
Genuinely curious: What’s the reasoning behind “unrestricting” this ahead of its 90 day window? (It’s tagged Deadline-90, Reported-2019-Apr-18 On Project Zero, so that’s July 18th?)
I’ve seen scripts get checked in and deployed just like you would a new service (code). Same Code Review process and same release pipeline.
In this particular case, commands that were run on a Production machine were by-design limited to what they can do and affect (mostly just the physical host they’re run on or a few hosts in the logical group of hosts they belong to).
The Stasi would have still found out that he fled the republic as long as he entered in West Germany under his real name. His girlfriend would still have been interrogated etc, perhaps a little less since it would have been easier to feign unawareness with her boyfriend just disappearing out of the blue.
The real beneficiaries would have been the students helping him and the teachers. They would have been able to travel to the GDR (to see their friends/family) since they likely wouldn’t have been connected to the escape.
The bravery the girls displayed was for defying the East German dictatorship. It could have ended much worse for them had they been found out before crossing the border. They did put their fellow students and teachers at risk, no doubt. But after the fact it seems pointless to punish them for helping a fellow human being escape dictatorship. Aside from maybe discouraging future travelers from such actions.
The book “The Dictator’s Handbook: Why Bad Behavior is almost always Good Politics” explains this fairly well. It’s a great read, maybe a bit depressing.
TLDR: it’s cheaper to pay off a small group (family) rather than a big group (populace).
[disclaimer: I haven’t been a people manager for too long, so take it with a grain of salt]
I block off some time each day to do ‘something technical’. Sometimes it’s making something pretty that was ugly before. Sometimes it’s learning a new tool my team is considering to pick up. Generally these are things that are important, but not urgent.
For larger projects, I often attend the design reviews. Sometimes I help on the designs, especially if it’s a new product altogether.
All managers on our team are also required to participate in the on-call rotation.
Between those three, I feel like I am still “in the trenches” enough to not forget what it’s like.
Dr Seuss wrote a book using only 50 words, which went on to sell millions[1]. A great artist can produce great work without being constrained by the medium. That does not mean the medium can/should not be improved further.
That said, depending on the majority use cases, the iPhone 8 camera is plenty.
I’ve been at my current company since 2005. I’ve changed disciplines twice, business groups (1000s of employees) three times, teams four+ times, roles at least three times (IC, Tech Lead, Manager). Many smaller re-orgs occurred in between and a few too many office moves.
In short, in a huge company there are challenges at all levels of the technology stack and that’s completely forgetting about areas like finance, marketing, business development, legal and HR.
It’s hard to get bored if you try to keep learning and challenging yourself every day.