addie

Android has a massive built-in library of supporting functions that abstracts away most of the differences between devices, including support libraries for older versions of Android, and Flappy Bird is almost the "hello world" of gamws writing.

"Register bit twiddling." Setting all the modes that all their various cards can operate in, with the associated code for sending the bit updates over the connection bus. Tedious stuff that's very prone to copy-paste errors if written by hand.

At some point you have to take AMDs word for it that these codes = this functionality, but if the right graphics come out then it can't be so wrong.

Might just be one girl, but she is very cute. Quality, not quantity.

Fake mews, surely? And yeah, this looks better than my Monday.

September 16 is a relatively common day for birthdays; 7% more common than the annual average. So I make the expected value about 3.1. Happy birthday to you, and fuck them.

The one with Timothy Olyphant and Olga Kurylenko in it? It was fine, had a few good action sequences in it. Managed to both not be much of an adaptation of the game, but also trying to be enough of an adaptation that it frequently makes very little sense. Probably have been better if they'd cut loose a little more, had some more fun with it. Gets a completely OK / 10 from me.

It has the finest atmosphere and world-building of almost any game. It does however have a whole slew of issues that are fixed in DS2, improved in DS3, and perfected more-or-less in Elden Ring.

• levelling up: there's a nearly-worthless stat, the endgame is either very easy or very hard depending on your character build and you won't know what you're doing the first time you play, and you can't respec. The other games have respec items and a better choice of weapons for any given stat spread.

• getting lost: you can go the "wrong way" from the start of the game, and leave yourself very badly screwed over. (In fact, the "right way" is kind of the least obvious.) The other games let you warp between rest points from the very start, which spoils the atmosphere a bit, but respects your time a lot better.

• useless weapons: some of the weapons are a trap - they have really bad scaling or some other misfeature that means it would be a mistake to build your character around them. One of DS2's best features is that nearly every weapon is viable for the right build.

• weapon upgrades: the weapon upgrade path is the fever dream of a madman; I've completed Dark Souls several times and I'd still need to look at a graph of how you actually do it. You need specific blacksmiths for some upgrade paths, and a couple of them are a real bastard to get to. The "back of an envelope" system is present in all other games, and they've a warpable bonfire near their blacksmith(s).

Dark Souls has a bit of a paradoxical position as one of the best games ever to play for the second time - bit like Morrowind in that it'll happily let you screw yourself over, but that makes it great to replay. I might be tempted to look up a "my first hour in Dark Souls" video or something like that to get you off on the right foot; doesn't need to be full of spoilers, just not set yourself up for a headache.

Because if you disable browser autocomplete, what's obviously going to happen is that everyone will have a text file open with every single one of their passwords in so that they can copy-paste them in. So prevent that. But what happens if you prevent that is that everyone will choose terrible, weak passwords instead. Something like September2025! probably meets the 'complexity' requirement...

A bit like when we renamed all the master/slave terminology using different phrasing that's frankly more useful a lot of the time, I think it's about time we got rid of this "child" task nonsense. I suggest "subtask". Then we can reword these books into something that no-one can make stupid jokes about any more, like "how to keep your subs in line" and "how to punish your subs when they've misbehaved".

Well now. When we've been enforcing password requirements at work, we've had to enforce a bizarre combination of "you must have a certain level of complexity", but also, "you must be slightly vague about what the requirements actually are, because otherwise it lets an attacker tune a dictionary attack against you". Which just strikes me as a way to piss off our users, but security team say it's a requirement, therefore, it's a requirement, no arguing.

"One" special character is crazy; I'd have guessed that was a catch-all for the other strange password requirements:

• can't have the same character more than twice in a row
• can't be one of the ten-thousand most popular passwords (which is mostly a big list of swears in russian)
• all whitespace must be condensed into a single character before checking against the other rules

We've had customers' own security teams asking us if we can enforce "no right click" / "no autocomplete" to stop their users in-house doing such things; I've been trying to push back on that as a security misfeature, but you can't question the cult thinking.

You joke, but that thing is invaluable on an SL1 run - gives some small but essential stat boosts. Had either that thing or the work hook in my off-hand straight the way through Scholar; the worthwhile stat-boosting shields come very late in the DLC.