This is what you get when you are acquired by Bain: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.powerschool.com%2Fba...
Long and tortuous history of ethics problems, "value extraction", big bonuses for do-nothing execs, etc.
- https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Ffortune.com%2Farticle%2Fba...
- https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.forbes.com%2Fsites%2Fm...
- https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Farchive.ph%2FhrjOD (https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.economist.com%2Ffinance-and-economics%2F2012%2F01%2F28%2Fbain-or-blessing)
and many more

in reality, the New York Times didn't support Stalin, it employed some columnists https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.npr.org%2F2022%2F05%2F08... who were among many fascinated by https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fdepts.washington.edu%2Fd... the "Communist" movement. however, Stalin and "Communism" was simply another brand of Fascism, which sadly https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fcambridgeblog.org%2F2023... America has always dabbled in for a long time.

Google handles transactions for millions of consumers around the world so the concern is probably something like https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.consumerfinance.go...

For example, if Google Pay on NFC-enabled phones is hackable and Google doesn't make some effort to provide security measures or compensation for exploits when they occur in the US, it's a US consumer protection concern.

FTFA the "exact scope of the CFPB's concerns is not clear, and its order does not appear to be final" so better to wait to see if they even move forward and, if so, what is that scope before jumping to any conclusions about Google's relative guilt or innocence. After all, they "do the right thing" for themselves first, everyone else second.

Specalised applications are a pain in the neck to support, the real issue here is that who ever implemented them did not fully understand what the end user requirements were. There is a real art of extracting that sort of information out of people and it requires an inquiring mind, good communication and people skills. There are application houses that milk corporations of money due to scope changes because they couldn't get the original spec right ... [sic]

I strongly agree. I recently changed positions in one of those evil corporate monoliths to do exactly that - extract the critical requirements early in the project phase so the solution winds up being more than a new set of problems. That's simply the changing nature of the landscape - the technical folks from a few years ago who have good communication skills and a willingness to listen are in an excellent position to provide consultation. I can not emphasize enough the importance of this basic tenet: you must listen to what the client wants, and not assume you have the answer simply because you know apt-get. Understand their needs and come up with a solution that a) meets them as much as possible b) within the project scope and budget c) with as minimal an impact as possible to daily operations.

But if this is not what you want to do with your background in CS, then don't do it - there are an ever-increasing number of companies that do need things built from the ground up with serious attention to low-level detail: medical research facilities, geographic planning organizations, and metropolitan governments aren't going to find all they need on a shelf somewhere. They just don't post the positions on careerbuilder.com, so you have to pound on doors, wedge your foot inside, and make yourself indispensable.

&laz;