Some days it seems every single Slashdot has a stupid typo in the first line.
Don't you have some AI / LLM machine to help with editing?

This adds costs to FLIGHTS, not FIGHTS.

Some of the reason that many Python programs are slow is because the authors choose slow, but easy to understand, algorithms.

An O(n^2) algo with still be slower than an O(n log n), no matter how its compiled or translated.

I'm sure Codon can re-write the instructions to be faster, but I'm skeptical it can transform the underlying algorithm from a slow technique to a faster technique!

If non-experts in programming (regardless of their Domain-Specific SME) keep choosing slow algorithms in Python, the resulting Codon code will still be slow, regardless of the transform that happens.

I think you just give your proper 6-months notice, then "quiet-quit", doing the bare minimum for the next 6 months, while collecting a $400K salary, and job-hunting in your remaining time?

It would be difficult for them to fire you after you've given notice, and easy for you to job hunt while still securely employed.
If you really cannot find a new job within 6 months, you can offer to stay on and there's a good chance and they might accept.

This actually sounds very favorable to the employee if you stop going "above-and-beyond" and worrying about your next annual review.
It would be a GREAT 6 months!

Zelle is not immediate in my experience.

To transfer money from my WF account to my other, CreditUnion account, I can use Zelle, which takes about 4 days.
Or, I can write myself a paper-check at my desk, deposit the check via Mobile Phone App to the other account, and have the money in less than 24 hours.

I cannot understand why the Write-Yourself-a-Paper-Check method is faster than an online system.
But after reading this, I'm thankful that it is.

I will continue to use paper-checks for both security and speed.

If Nadella and others wanted to have a bigger impact, they'd figure out how to "Democratize Executives". When executives and management can be replaced by point-n-click interfaces, then no one ever has to suffer under bad management or corrupt CEOs again.

But that's not what they're doing. They're trying to reduce the pay and impact of expert programmers to increase their own power and wealth.

It is not about making technology more universally accessible, its about making power and wealth less accessible and more protected in the hands of those who already have it.

Microsoft already has Microsoft Mathematics (https://www.microsoft.com/en-us/download/details.aspx?id=15702), that does exactly this, and a lot more.

Realistically, how much money does FB make off of showing me, personally, ads?

How much would it cost me to submit an ad-buy, targeted specifically at me, and me only, that shows nothing but blank whitespace?

"Microsoft is willing to reward anyone who reports bugs that could cause problems like earlier in the year"

Like, earlier in the year, like, January? February? How early in the year are we talking?

We really need Google Earth VR to work on The Google Pixel / DayDream headset.
Currently it only works on the HTC Vive, and thats a big shortcoming.

I completely reject the idea of a "Generic Engineer".

An Engineer is someone with extensive specialized knowledge in a specific field so that they can "engineer" solutions to problems.

Either these "laborers" have specialized knowledge in one or more fields, or they don't.
By Generic Engineer, the author seems to be implying that "they're smart people with some math skill, and therefore can do anything I throw at at them", which is simply not in line with reality.

Constant mistakes in the first sentences of stories is why I read Slashdot less and less.
For a tech-site, they sure cannot learn to use Spell and Grammar checkers.

The current "Learn to Code" movement is not (or at the very least, should not be) about turning everyone into a Professional Developer.

Rather, I think it is an understanding that most of these students will pursue other professions, but will need to interact with developers.
They'll need at least a passable understanding of what code is, what debugging is, what testing is, because they'll be associated with it to some degree.

The goal is to end managers who believe that a "Debugger" is a program that fixes your bug for you.
Or that "Testing" is "it seems to work, lets ship it!"

Very few people will end up professional programmers, but everyone else needs to be somewhat familiar with code.
(In the same way that very few people are mechanics, but everyone should have a vague concept of an engine, gas, oil, gears, etc)

I don't think it was actually 32,767 workers... I think its actually -1 on a 16-bit-system.

Does 10K vs. 200K vs. 5MB actually matter? RAM is so cheap, so small, and so ubiquitous today.

I appreciate that it doesn't need gigabytes of memory... but what does saving 190K of memory really get that wasn't possible before?

By not posting stupid tech-support questions... some random guy's hare-brained scheme... or pseudo-science that isn't backed up by common sense.