Who, Me?: Fake it till you make it doesn't cut it for mission-critical workloads

Why has a link to R v Sweet, a decision by a Queensland district court, been in my bookmarks bar for almost five years, probably? Two-part answer: (1) it’s one of several amusing opinions rej…

GARY: Hey Cindy, remember the other day when we were talking about optimizations?
CINDY: Yeah, I wanted to circle back on that.
GARY: Me too. You s...

I generally am uninterested in generative AI that's too close to the real thing. But every once in a while there's a modern AI thing that's so glitchy and broken that it's strangely compelling. There's this generative AI knockoff of Minecraft that fails so hard at being Minecraft that it

Microsoft product name changes collated at m365maps.com by Aaron Dinnage

Denise's company formed a new team. They had a lot of low-quality legacy code, and it had gotten where it was, in terms of quality, because the company had no real policy or procedures which encouraged good code. "If it works, it ships," was basically the motto. They wanted to change that, and the first step was creating a new software team to kick of green-field projects with an eye towards software craftsmanship.
Enter Jack. Jack was the technical lead, and Jack had a vision of good software. This started with banning ORM-generated database models. But it also didn't involve writing raw SQL either- Jack hand-forged their tables with the Visual Table Designer feature of SQL Server Management Studio.

Today's anonymous submitter spent a few weeks feeling pretty good about themselves. You see, they'd inherited a gigantic and complex pile of code, an application spread out across 15 backend servers, theoretically organized into "modules" and "microservices" but in reality was a big ball of mud. And after a long and arduous process, they'd dug through that ball of mud and managed to delete 190 files, totaling 30,000 lines of code. That was fully 2/3rds of the total codebase, gone- and yet the tests continued to pass, the application continued to run, and everyone was just much happier with it.
Two weeks later, a new ticket comes in: users are getting a 403 error when trying to access the "User Update" screen. Our submitter has seen a lot of these tickets, and it almost always means that the user's permissions are misconfigured. It's an easy fix, and not a code problem.

Imagining how we'd cover overseas what's happening to the U.S. right now

Who, Me?: Hey! Teacher! Leave our network alone!

Techie complains as biz ignores contractual working hours

On Call: Shabby admin invented 'transparent tape' – a terrible storage medium but a magic tool for unlocking IT budgets

Who, Me?: That's not even the worst part of this story, which features a flood, broken promises, and plenty of panic

His ex-wife will therefore not be required to support him in that endeavor (or any others).

Who, Me?: 'If I wasn't already taking blood pressure meds, I'm sure I would not have survived'

This is still considered bad form in the UK, apparently.

On Call: With only BASIC knowledge to fall back on, and a typing pool in tears, the OFF switch looked very attractive

Jenny had been perfectly happy working on a series of projects for her company, before someone said, "Hey, we need you to build a desktop GUI for an existing API."
The request wasn't the problem, per se. The API, on the other hand, absolutely was.

Barry rolled into work at 8:30AM to see the project manager waiting at the door, wringing her hands and sweating. She paced a bit while Barry badged in, and then immediately explained the issue:
Today was a major release of their new features. This wasn't just a mere software change; the new release was tied to major changes to a new product line- actual widgets rolling off an assembly line right now. And those changes didn't work.