This sounds more like "Nvidia Executive hints that the most cost-effective rendering option is about to become your brains in a jar."

Tinfoil brain-protecting hats about to gain another use case!

The new skill paradigm shifts technical skills that were typically prioritized, such as proficiency in STEM, which was the most critical skill in 2016, to the least priority in 2023. The reason is that now tools like ChatGPT allow workers to do more with less knowledge, as noted by the report.

By all means, let us replace subject matter experts with large language models and encourage doing more with less knowledge. True innovators will be able to apply this technique in fields that were previously ossified with enormous overhead in safety assurance and risk management, allowing us to finally begin addressing the problem of surplus workforce from the supply side rather than the demand side.

It's not that programming is hard per se. It's that most of these 'introductory' CS courses are designed and paced for students who have significant prior programming experience and familiarity, yielding the same kind of results that you'd get from making an 'intro' calculus class that has no testing or prior coursework requirements.

Sure, students who have had experience with most of the foundational bits will do fine, but the vast majority of the students that don't hit it bounce and never come back. CS departments are just terrible at handling anyone who doesn't want to devote their life to CE/CS.

The vast majority of Gelsinger’s compensation, however, is from stock awards and options. Gelsinger’s base pay was $1.25 million, according to his offer letter, or just under 0.7% of his nearly $179 million in total compensation for 2021

Total employee wages for Intel's ~120,000 employees are ~$12B, chopping the CEO's compensation would allow for a 1.5% raise across the board. For 120,000 people. Gelsinger made 1800x the pay of an average employee last year, anyone who doesn't think this is insane is part of the problem.

it is absolutely adorable that your estimate starts with CEOs only making 10x as much as an average worker. Maybe 60 years ago... ...but definitely not any time since the 80's.

Sure, SWA could be argued to be still a financially stable airline. But how long does that hold when there are now hundreds of thousands of former customers who will never consider flying SWA again? Or worse, if the scheduling system falls apart again in a month or two before the root causes can be addressed?

All in all, a particularly egregious example of entirely legal self-dealing, extracting every possible dollar of the value created by others with complete confidence that someone else will end up paying for the results.

Southwest USED to be a well-run corporation, with stable, steady growth and providing a reliable product, with employees that were generally treated decently and provided with the resources they need to do their jobs. Then Gary Kelly took over as chairman and president in 2008 from the original founder, and decided to play accounting games instead. In the last decade, Southwest repurchased more than eight billion dollars of stock, out of about nineteen billion dollars pre-tax operating income. Kelly bailed out last year with the ~hundred million dollars he personally extracted, and left behind... this.

The previous generation of self-dealing executives made ridiculous sums of money bleeding the company dry to juice their stock options. Corporate stock buybacks should never have been legalized -- and as long as there's cheap fast money in it, grifters and private equity vultures will be happy to suck the money out of anything that moves and leave failing companies and massive layoffs behind.

systemd is oriented toward linux on the desktop and starting up quickly... which nearly nobody who actually does things cares about.

I could not give fewer shits about starting up a headless server quickly, but it irritates the living fuck out of me when systemd does something like just GIVING UP on mounting a flaky nfs share (from an admittedly shitty appliance, which my services are constrained to use regardless) one time in ten because network services aren't really ready yet, or the first attempt timed out, or what the fuck ever, and then continues merrily through startup, until all of the downstream dependencies fail terribly and I have to take manual action to fix it.

systemd's focus on being a desktop/gui solution is worse than useless from the perspective of a sysadmin who needs to ensure things like dependencies, y'know, actually being FUCKING available before services start.

OAuth single sign-on login flow. "Sign in with Twitter" / "Sign in with Facebook". Ask.FM needs to have a record of which 3rd-party identity provider user is linked to an Ask.FM account.

On the plus side, if they're using an OAuth flow to sign in with Twitter/FB... Ask.FM doesn't necessarily have a password for them to begin with, and the entire point is that Ask.FM doesn't get access to any user attributes beyond what is explicitly released as part of the login transaction.

Also applies in this case with instragram and vkontakte based on the user table, but the get-off-my-lawn crowd doesn't recognize those instantly from iguid and vkuid.

There are many groups who have a vested interest in promoting NFTs as real enough for fools to spend money for, but unlikely to ever be real enough to attract sustained attention from government agencies interested in financial transactions. A quick assessment includes:

First Mover Ponzi Scheme Profits!

Money laundering as a service! [MLaaS]

Bubble opportunities for money managers fresh out of innovative financial instruments to dump untaxed billionaire profits into! Er, invest. Yeah, it's an investment.

As long as NFTs remain a thing that anyone takes seriously, all of the groups above have an interest in at least some people continuing to take them seriously.

It is important to remember that trust is generally inherited. Code signing certificates with time stamping 'solve' the problem of expiring code-signing certificates by instructing the software to check with that the code-signed certificate was valid at the time it was signed. So, someone with the original private key needs to be answering where the software checks.

In order to trust what the server of the original signing party says, a valid chain of trust is still required. The end-use public certificate generated to establish specific attributes like "I am the code-signing server of the COMODO RSA Certification Authority" is itself signed by the private key of an intermediate public certificate, continuing in a chain of trust back to a root certificate which signed by the key of a public certificate on a relatively short list trusted by the environment a program is running in -- generally the root certificate trust store of the OS or a specific root trust store built in to that software.

A timestamped code-signing certificate still requires that a chain of trust is established in communicating with the party who has the private key of the time-stamped code-signing certificate. The intermediate and root certificates are generally created with a much longer validity period (in the 10-40 year range), but over a long enough time frame all currently-available trust chains will expire unless the root trust store is updated.

Since your trust store is not generally filled with very new root certificates, this is also a moving target and it is not uncommon for an OS only a few years old to begin to encounter trust chain problems unless updates are installed. This is why Safari on say, your relative's 2016-vintage macbook running OSX 10.12 Sierra that has been EOL since 2019 will say a lot of websites are untrusted -- Safari is looking at a stale trust store from 2019 or earlier.

Certificate expiration really only matters to sysadmins. End users don't know what to do or who to tell if something is expiring.

To solve this problem, I wrote a python script that iterates over the set of certificates that have been issued to my organization (easily available from the CA) and attempts to https handshake with all of the CNs and SANs associated with certificates that are approaching expiration. This runs as a recurring jenkins job that notifies my team for anything that replies with a certificate that is expiring soon.

This has saved my ass several dozen times since I inherited responsibility for a couple hundred random virtual hosts along with my current position, some of which were legacy services that nobody still employed knew about until the alert popped up.

The real problem is oddball/backend services that use TLS but don't answer incoming https connections on 443-- https handshakes don't find those.

MacOS Sierra was end-of-life in 2019.

This means Apple has not been updating the associated certificates... since 2019.

EOL OS = no updates for root/intermediate certs. If you want to use a device that is out of support, expect bad things to happen. Expiring certificates is by far the most benign outcome...

hate speech: noun

abusive or threatening speech or writing that expresses prejudice against a particular group, especially on the basis of race, religion, or sexual orientation.

One argument would be that the problem lies in the abusive or threatening nature of this 'speech'?
Another argument is that the historical roots of hate speech are strongly correlated with hate action, applied to the unfortunate and the vulnerable alike.

OTOH, your straw man may be more convincing with different straw. What forms of 'hate speech' do you personally support?