Sure, that cheap desk that arrived in a flat box and got assembled by me and a screwdriver was mass produced in a factory. But it's design had way more expert craftsmanship put into it than would ever be feasible for a bespoke product. High upfront design cost, then mass produced at a low marginal cost.

That had been the state of art for software from the beginning. When you download Firefox, there is no expert programmer carefully building you an artisinal web browser. There is a CDN server sitting in a data center somewhere copying bytes out of its cache for you.

One of the things AI us threatening to do is replace the CAPEX craftsmanship, which has not happened at scale in other industries.

What AI has had more success at it replacing low end "artisinal" software; which is a category that has thus far been so uneconomical is essentially doesn't exist.

In short, git has a 'create_ref_symlink' function that is replaced with a macro to '-1' on some build configurations. This means that any code which is conditioned on the success of create_ref_symlink would trigger a compiler warning when built with -Wunreachable-code. NOT_CONSTANT supresses this warning by preventing the compiler from realizing the code is unreachable. It also prevents the compiler from eliminating the dead code, but presumably that has only a negligable impact.

They do need to have some form of dedinator, and tying that detonator to a Bluetooth control seems like a design that someone might come up with.

> For anyone seeking a legitimate source on the bluetooth device comments: you can listen to the KEWR Ramp/Company/Misc archive. Keep the date set to 2026-05-31 and the feed set to ramp/company/misc, but change the time to 0200-0230Z. Then, skip ahead to about 22:55

https://www.liveatc.net/archive.php?m=kewr_co

From ATC

> Do you guys know what happened with that - uh what is that a - 7-6 on the left?

> There's a security detail out there. Someone had a bluetooth they named a certain four letter word; so they have to inspect the whole aircraft including the cargo area. The passengers have to evacuate.

> That's crazy

At least for US federal taxes, losses do not need to be tied to revenue. As long as they occur in the same tax year, you can deduct. You can also carryover losses to future years, or pass them through to personal income deductions; but the rules there get more complicated.

In this case, the bankcruptcy was handled by cancelling all flights with 1 day of notice. This level of ugliness is not necessary.

These people also don't make the cards much money, so loosing them wouldn't have that much of an effect anyway.

The situation with wellness apps is that they are a product that are designed specifically to exist outside of the regulatory regime that people associate with them.

A production API key appearing on the wiki would be the second biggest security incident I have seen in almost a decade.

------

On the AI note, despite a massive investment in AI (including on-premesise models), we don't give the AI anything close to full access to the intranet because it is almost unimaginable how to square that with our data protection requirements. If the AI has access to something, you need to assume that all users of that AI have access to it. Even if the user themselves is allowed access with it, they will not be aware that the output is potentially tainted, and may share it with someone or thing that should not have access to it.

Clippy is essentially a linter; and one of its checks catches cases where different enum variants have a significantly different size; with a suggestion to Box the larger variant.

Since this is just a linter, it doesn't actually have any knowledge of how frequently each variant is actually used. It also doesn't address the situation in the article at all.

This is the same reason a bunch of the food in your pantry is certified kosher. No one is going to not buy something because it is kosher. But if paying a thousand dollars a year to put a small circle-u symbol on the back of your box can increase sales by 1% among observant Jews, most companies are going to do it.

Further, the utility's safety concerns do not require any shut off on the mains. Their safty concern is not a new backflow of current; but a backflow of current into an otherwise non-energized grid. Grid-tied inverters will not do this. If the grid goes down, they shut themselves down without any need for an upstream shutoff.

The utility's may have a reasonable business object to back-flow if their meters are such that backflow forces net-metering. Around here, that is a non-issue because net-metering is the law for residential connections anyway. Even in juristictions where net-metering is not the law, I don't find this convincing. The limited capacity of balcony solar means that it won't actually happen in any significant amount, and if it does become a problem, they can shoulder the cost of upgrading their metering equipment.