To think any part of the government is efficient is laughable at best.pTo think that ANY LARGE ORGANIZATION is efficient is laughable at best. FTFY.

No, you make the move if:

r_cl r_l and
C_clo C_l

Where r_l/r_cl = risk of catastrophic loss on local config/cloud config, similar for the costs.

You can calculate the cost of keeping production and migration systems running for a migration and shakedown period, as well as the risk/cost benefit of continuing the migration or shutting it down at any point. As such, one can estimate these costs and there are some points in the mathematical domain where it makes sense to migrate.

However, I believe that we would strenuously disagree about the risk of a cloud system vs. a locally controlled system. Here's one way to think about it, though...

I'd think that the cost of a contract on your system (should anyone choose to make one thereupon) would be considerably short of $100K. On Amazon's entire system? Millions. Refute that notion of risk estimation.

It would have been much easier and cost effective to just take the first management position and work into retirement at the hospital or bank or retail corp or manufacturer or any of the other places I worked at in the past in IT.

Ha... ha.... ha, ha, ha, ha, ha.... Oh excuse me. That was droll. As if any of the folks who moved up had any more job security than you. No, you don't get that sort of security until you hit the point where you can pre-negotiate a golden ticket on the way out. And that sure as hell isn't first-level management.

I did as you proposed. I was an individual contributor who moved up into management and, honestly, only after I'd taken fifteen years moving up the IC ranks to the highest levels my company had and did some serious soul searching about my ability to do the job, having seen both good and bad managers in my career. The result? After fifteen years I still often got paid less than some of the higher-level technical folks I managed and the final layoff came regardless.

In any case, promulgating the notion that being a manager somehow insulates you from idiots higher up the chain really isn't fair. In most orgs, first level managers are seen as about on par with managers of a local Pizza Hut and have similar job security. One who likes working with the technical folk and so stays at this level finds this out eventually. It's up or out even there. I wanted to stay out of the always political shark fight higher up, so I learned enough about it to play at my level, I enjoyed working in my various jobs with a lot of great technical folks, but I got laid off the same as the rest of my teams. In fact, in my last FTE position, I and another "senior" manager were shown the door while our teams stayed on.

I'm now a contractor/consultant after my final layoff and, though I make a bit less than I did when I was an FTE and have even less job security, I choose how much I work and I work on things that are interesting to me with people I generally like. On the whole, it's a better life.

The problem is that most organizations have a variety of tasks at different priorities, many of which do not fit into a arbitrarily defined sprint length. In reality, the wider the spread of job sizes and priority, the more overhead scheduling takes. You split loads into less varying sets and tune the scheduling process for the teams that gets each set for that. Basically, if you don't control the task variance, no scheduling algorithm, agile or otherwise, will help. If you have too many jobs, the same. But ultimately, it is a relatively simple management problem to solve. Trying to pay for it though? Well, good luck with finance...

And, frankly, if you didn't already know what these were, you haven't been paying attention. Which worries me. If smart people around here are too dumb to understand what this stuff is, who the hell is watching?

Funny, when I here government inspectors, I always think incompetence.

Funny, when I think of government inspectors, I always think of corporate malfeasance. Bit maybe I've just been paying for late, over-budget governmental contracts for too long.

If family leave was decently supported in this country, we would not be having this problem.

They have neither the time nor the intelligence to actually understand why decisions were made the way they were made.

I've worked with auditors, both clueful and clueless, just like I've worked with similar people in many domains. The fact that you've only encountered poor auditors is more a reflection of the firm(s) your company is(are) hiring to do your auditing. The fact that you see no value in the process does not mean that others do not see value. Frankly, there are a lot of people (besides compliance auditors) that are quite happy that these laws are in place because we remember what brought them about in the first place. The fact that we're still getting security breaches out here means that we still can't trust companies to do the right thing.

You want to change things? Fine. Make sure businesses are doing the right thing. Until then, we have laws, motherfucker.

Well, yeah, but you won't get it if the folks who are paying for it think they're getting ripped off. Here's the thing, science or no...

People who are paying for your project have a right to audit. Period. You want to sue them after the fact for the reason that their audit fucked things up and you should still get paid, fine. But fucking play by the rules.

Frankly, half of the trouble around today is a bunch of rich folks/company that run around screaming "We don't have to obey the rules if we don't like them!" This two-years-old's style of argumentation may be amusing to watch, but in the end, its counterproductive.

Gosh. They knew about the law beforehand and ignored it. Why should the little darlings be fined? After all, if you were a kid caught with an ounce of coke, you'd be doing time and that's right! But charge a bidness a few bucks for breaking the law? Unconceivable!

Because learning from your mistakes is such a bad thing. Idiot.

Wow. Because "riding" someone is always a good excuse for them retaliating physically. Clarkson crossed a line. Period. The producer went to the fucking hospital, you moral degenerate.

They couldn't make a small enough internal combustion engine to fit in his sonic screwdriver.

Rumor had it that Clarkson's screwdriver was rather small, anyway. That's why he needed the cars.

I do write code every day (well, except the weekends - I have my boundaries). Over my 30+ year career, I've probably written quite a bit. Most of the female people I've been privileged to work with (and manage) as programmers have done the same.

However, getting back to the subject, I don't see a lot of suffering coming about as a result of this "small subset", as you call them. I mainly see inexcusable behavior called out and people who do it publicly exposed and then suffering as a result. Is this why you suffer? Maybe it's deserved.

Yeah, I'm pretty sure the extra $5 or so wouldn't be an issue in court if you could actually show increased costs. Stop being an asshat.