shortimer

This is only personal experience, but multiple/many data points in that personal experience. I'm familiar with government departments where 20%+ of the employees do essentially no work whatsoever. Their assigned work languishes indefinitely, until it eventually looks bad enough on some chart that it gets assigned to someone else.

That "someone else" is often a hardworking, loyal employee who does their best to earn their pay (thank you, to those people!!). But their attitude is ground down over time by watching those other people do literally nothing, and eventually get promoted "because seniority."

So I fundamentally disagree with your premise that you could transplant that population into a business. I'm certainly familiar with freeloads in business, but I'd struggle to come up with an example company where 1/5 or more of employees do no work at all over multiple decades and then retire with a pension.

At our place, we put a redirect on the front end networking device that detected if a browser couldn't support more modern encryption protocols, and sent them to an HTTP information page (instead of to the application itself) if so. This allowed us to update the core app to force newer protocols, while still providing some sort of UX for those left behind. We used Piwik to track the hits on the redirect page to get a sense for how many users were left behind.

Being another person giving you advice may be irritating, but on the off-chance it helps, in my area (Northeast USA) there are places where people who need help "living" can do just that. They get a room, food, help with transportation, and "recovery" (life) planning assistance, and it is "free" (their Medicare/Medicaid). They are free to get jobs, and some do, either at partner facilities where they do small repetitive tasks, or in a traditional job in the community.

The #1 challenge is quality - as a parent, you'd have to be and stay involved, as even within a single organization, the quality of each "house" can vary really significantly based on the people who work there, and further, can drift over time as the staff evolves.

Anyway, here's to you; parenting is never easy.

edit: grammar

The guideline doesn't say "don't call people names"; they say "don't call names." Here's the text:

When disagreeing, please reply to the argument instead of calling names. E.g. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."

New fintechs who want to move money have to obtain a Money Service Business license in every state where they operate. In almost all cases, that means they have to get 48ish MSB licenses (a state or two don't require them). Each one can be both complicated and expensive to obtain and maintain.

This new license would let those fintechs instead obtain a single license (and set of rules, and costs, etc) for nationwide use.

Isn't the underlying assumption here that the team members know everything they need to know to make a decision?

While that may be true for, say, algorithm selection, I would argue that, at least in larger organizations, there are overarching architecture or standards that need to be considered, and that it may be a waste for the individual team members to constantly keep track of.

We had a super-smart team come in a few years ago, and work very independently to come up with an awesome standalone solution that worked in no way, shape, or form with the millions of lines of installed code. There's an argument to be made that perhaps that's great and they were not constrained by legacy code, but decisions like that should be made purposefully, not based on how a few smart people who know almost nothing about the broader business or technology feel.

We're using Delphix too. Complements an approach like this, doesn't replace it. We use Liquibase to support the schema-as-code concept; it's enforced by no one outside Sr. DBAs being able to make such changes directly in anything other than Dev (lower-than-QA) environments.

Delphix is terrific for having production-like data in your test environments ("like," because you'd better be masking sensitive information from prod before it gets written in test.

The issue we've had with Delphix is performance. It absolutely pounds on the storage system, and tends to suck up all available bandwidth and CPU that's made available to it. If you resource it properly, it's amazing.

I've watched Groundhog Day probably 100 times. For six or so months, I left it on repeat on the main house TV (I lived alone at the time).

Can the original poster just try putting a sheet of cardboard in front of the flash and see if it affects the 'scope results?

Seconded. This seems like a way-too-dramatic writeup of private company which comes to the same conclusion folks have been coming to for a while, based on my 30 second Google search.

I guess it's relevant for musicians and Bain Capital, but he does come across as a hyper quack.