As a manager with 10-15 reports at a company you've probably heard of, I think the main question is how much they will need to contribute. I put up a PR or three a week, usually in non-critical path flows or system support, and its honestly fine. I could barely contribute to the productivity level of even one of my junior engineers, but I can debug production issues and ship code AND be a good manager (with a decent work life balance).
I feel like managers should be able to contribute. Managing a good team isn't that hard, though managing a bad team (or a good team in the midst of a ton of bad processes) is a nightmare.
Creating an additional 30%-50% on top of whatever a normal person would consider passive income in order to actually have passive income is NOT a realistic option for a huge % of the population.
I've been telling people, this is Uber in 2014, you're getting a benefit and it's being paid for with venture capital money, it's about as good as it's going to get.
I would also argue that software (and the people that write it) have a "correctness" bias that is not fully aligned with business goals.
Tech debt is real, but so is the downside of building a system that has constraints that do not actually align with the realities of the business: optimizing for too much scale, too much performance, or too much modularity. Those things are needed, but only sometimes. Walking that line well (which takes some luck!) is what separates good engineering leadership from great engineering leadership.
You pay for one or two people with real experience and 4 reasonably new hires whose job it is to answer questions posed by the senior team and to build documentation.
You want the senior people focusing on the problems, strategy, and comms and not data aggregation and power point formatting.
Half the time it doesn't actually matter who the consultant is, the business is just looking for an arbiter to provide a second opinion or justify a decision.
I think the group of people that work on this should petition for their tax data to be the first to be used. Seems to align the incentives on internal controls of PPI.
I've never this at Google, but at my company, if you pass the technical screen you're offered to hiring managers. If they don't want you on your team because they want more leadership (or less leadership), or if there were 5 senior python roles and you were the 6th person to pass the interviews, you still won't get hired.
It's not the hiring people that's the problem. Assuming those people "cost" 300k a year all in (benefits/offices,etc) which is probably high, that's $24 billion. The government spent $6.8 trillion, cutting these jobs cuts spending by .3891%.
Cutting the people without cutting the programs won't do much and is (IMO) a problem in that you should be able to access government services in a way that the writers of the laws (house/senate) have clearly agreed to. When you're cutting this widely, it's hard to believe you're not throwing the baby out with the bathwater.
In a softly held defense of those words, they basically are an escalation level.
If someone asks you for something, it could be something with undefined scope or priority. An "ask" signals "this is official". Same thing with learnings: lesson is personal, learnings means ways things are changing.
Are there dumb business terms, absolutely, but these aren't bad IMO.
I think the OP is saying that both nations are banning software because of the risks of the software/data collection posing risks to the political stability of each nation. You can obviously say "our reason is better because X", but the outcomes being the same means that there is justification.
Both sides say it's worth banning "Tiktok/Google for granting the CCP/USA the ability to algorithmically influence the views of Chinese/Americans".
I work for a company managing a team that has built this for GDPR compliance.
Customer submits a deletion request. We have a fan out process that takes the deletion request and submits it to a bunch of different data locations. All of these must respond within 2 days (though the required time is 72h). Each of those data locations will queue up a job to remove access (soft delete) the data, and schedule a hard delete for 28 days in the future. If the customer says they don't actually want the data to be deleted, we cancel the data hard deletion and revert the soft delete. If nothing happens the hard deletion goes through.
Every SaaS platform with a reasonably cheap offering deals with these. I work for a recognizable SaaS and there are checks that flag both the accounts and reports the credit cards that are used after a fairly low threshold of "add payment method attempts". High levels of fraud usage hurt your reputation with payment processors and that's bad for business.
It doesn't stop the truly determined ones I'm sure, but it does mean that it adds complexity. You don't need to be impossible to test cards on, you just need to be harder to use than someone else (like a lower resource charity). We've even debated "fake accepting" some payment methods after we're confident it's someone trying to find working credit card numbers to add some false positives into the mix.
I feel like managers should be able to contribute. Managing a good team isn't that hard, though managing a bad team (or a good team in the midst of a ton of bad processes) is a nightmare.