tech2

Anemoia is the term, I believe, and an almost perfect fit (nostalgia for a time you have never experienced)

Historically that was always part of the bragging rights. The harder to reach, or more risky location, the higher the cred for having achieved it.

All that's old is new again. In the late 90s there were a number of companies (eMachines, for example) which heavily discounted their machines by having integral advertising, and in some cases through internet service provision. This sounds like the same idea all over again, just with a different backing fund source.

Two major issues in my experience seem to occur.

The first is that you had a system with a given set of ownership and now lines need to be drawn between groups to grant each sub-team their own piece of the larger pie. This is where Conway's law comes to bite you because your code is likely structured around your existing team and practices. Deciding how to draw that boundary is a challenge (API-based? Separate services?). Do not skip this part, otherwise you'll have an awful mix of old and new and everyone suffers.

The second is how work is structured. With a small team, anyone can edit anything (ownership again). With multiple teams you need to accept that changes will require multiple stages of development and the rate of change can take a hit due to scheduling and prioritisation for each team. In the small team a single sprint (assuming this is your working practice) may have been sufficient, but with multiple teams those changes will need scheduling.

It's not entirely fair.

Prior to 2.3 Python didn't have booleans, just "truthiness". In 2.3 they added the Boolean class as a subclass of int (because of patterns of development it was a pragmatic choice). True and False were introduced, but they were able to be reassigned which could cause all manner of fun. 3.x made them keywords which put a stop to that but the int aspect remained.

I have to ask, because wow that's a lot of buckets, but what kind of activity requires breaching even a 1,000 bucket limit per account?

For python maybe pip-audit, and perhaps bandit for a little extra?

It doesn't have the code tracing ability that my sibling is referring to, but it's better than nothing.

I tried to do that, really did, but my TV was circa 2006 and I needed a replacement. None of the options in my region are good, there's no Scepter equivalent unless you pay 3x as much for something akin to a commercial display. So, air-gapping it is!

The one that should probably really freak you out was/is the Soviet "Dead Hand" system. Who needs people deciding whether to launch?

I had wrap from my exhaust system start to unravel at one point during a long journey far from home. I had to unwrap it by hand on the roadside sans-gloves to prevent it from ending up under a wheel and tearing components apart. The end result was that I had to find a local retailer selling duct-tape; Not for the car, but so I could apply segments of it to my skin to pull those tiny irritating fragments free from my inner forearm. Yeah, that itch is evil!

Right, but that's a follow on to regulations about increased rear and side still heights for occupant protection, and that's a follow on from increased vehicle sizes, and that's a follow on from commercial vehicles being sold to the general public instead of regular passenger vehicles due to tax breaks, etc.

One of my favourites that starts out difficult but you become fluent in by the end is Banks' "Feersum Endjinn". I love seeing people's facial expressions on first attempting to understand Bascule, or read it "normally".

The earlier model that the 25 replaced was all mechanically interlocked. The belief was that software provided that same level of assurance. They performed manual testing but what they weren't able to do was reach a level of speed and fluency with the system to result in the failure modes which caused the issues. Lower hardware costs equals higher profit...

They may not be against content restriction, instead they may be against removal of user privacy or anonymity. If the proof of age thing was some kind of zero knowledge proof such that the age verifying group has no knowledge of what you're accessing, and the site you're accessing has no knowledge of you as an individual (beyond tells like IP address etc.) then perhaps they'd be more open to it?

The issue with the lack of intermediates in the cert isn't browsers (they'll just deal with it). Sure, if they aren't already in the cache then there's a small hit first time. The problem is that if your SSL endpoint is accessed by any programming language (for example, you offer image URL to a B2B system to download so they can perform image resizing for you, or somesuch) then there's a chance the underlying platform doesn't automatically do AIA chasing. Python is one-such system I'm aware of, but there are others that will be forced to work around this for no net benefit.