I miss the byte-counting assembler days of the 70's and 80's. RAM was measured in bytes or kilobytes and ROM space was almost as precious. Code was printed on paper, and computer monitors were heavy glass boat-anchors. You had to configure dip switches to get devices to talk to each other (slowly). Documentation was a bookshelf, not a web site. Persisent storage required rusty iron - ok, that's still the case, but now it can be solid state too. We configured IRQ's and I/O addresses. Sometimes we had to put the card in the 'right' slot. We had tape drives and line printers. We had RS-232 cables for serial and parallel cables for parallel. And best of all, we had clicky keyboards!

Conversely, it could be argued that matter is just an energy being that died.

During the .dot-com bust of 2001, I met a bartender in Manhattan who, just 2 years prior, was earning $90/hour as an HTML programmer. Yup, HTML programmer. If you want to know where today's "prompt engineers" will land in the coming months, check your local pub.

The IRS is about to find out why you can't lick a badger twice (https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Ffuturism.com%2Fgoogle-ai-overviews-fake-idioms)

Google says IBM's headcount at the start of the year was about 290,000. Mr. IBM says they've replaced a couple of hundred workers.

200 / 290,000 = 0.07%.

Quite tiny, in the overall scheme of things.

I think it's space snot from a sick black hole that sneezed out some dark matter. We need some space-sized fingers to roll it into a ball and flick it across the universe.

Today's software engineering graduates can't read what is arguably the most "readable" computer language ever invented? The challenge is not understanding what individual lines of code do (any junior can understand "add", "compute", and "perform), the problem is in understanding what the program(s) do, and how they interact. These are not a language-specific concerns. Automating the translation of "opaque" code with ChatGPT doesn't address the problem, because you're left with the same questions: What should this program do, and is it doing it correctly?

36 satellites in a year? At that rate, ol' Jeff will have his 1,600 in a mere 45 years. He can either make satellites faster, or get really good at asking for extensions.

Raises would have been better. Or free snacks and drinks. Or fewer meetings. Or better chairs. Or more plants. Or a fridge that doesn't stink. Or... or... or...

This smart man shouldn't play dumb, because he clearly doesn't know just how smart us dumb people are. For example, we can tell he's lying. We can also tell he's avoiding the question. AND, we can tell he's a dumb smart person because he doesn't know how smart us dumb people are. The circle of stupidity is complete.

My fridge magnet can defeat your so-called "unjammable" magnetic field inferometer. Pray I don't turn on the microwave oven.

This would be possible only if your neighbor was running an unsecured (no password required) network (which is stupid, but it happens).

I'd give Harris higher odds of pulling this off. Binden passed actual legislation (Chips Act) to encourage this. Trump promised (note: a promise is not legislation) Wisconsin a huge Foxcon plant, and they got nuttin'.

Step 1 to becoming like a startup: Cut the CEO's salary to a pittance.

Of course they're cheaper. They don't have the public service mandates that the USPS does. You're comparing apples and oranges here.