mpettitt

Including developer tooling in a Docker image is missing one of the really useful things about Docker: not needing all that stuff. By using a multi-stage build, you can do all the slow dev stuff at image build time, then only include the output in the image, and that includes things like building a library which wants a different set of conditions to build than your application wants to run.

It also adds an additional level of risk - if your image is compromised, but all that is running in it is your app, oh well. If it's compromised, and it's able to call out to other parts of your stack (yes, some of this is down to the specific deployment process), that's much worse.

I recently bought a WD Red HDD drive for my NAS direct from WD, and it arrived in a crushed box. Now, things do get damaged in transit, but I don't want to install a drive, start using it, then get errors which were caused by damage which occurred before I even got it.

I sent the customer support team an email asking them to confirm that the level of box damage seen wouldn't affect the drive, or alternatively to provide a return label and replacement drive. Their response was "try it out, and if it fails, we'll replace it".

Having seen quite a few stories like this about WD and sub brands, I'm tempted to just return it for a refund and go elsewhere...

Some of these don't look like checkboxes at all, and wouldn't trigger any indication that they could be changed. For example, if I saw number 44 next to a line of text, I'd think "that must be something not available for some reason" rather than "I could click that to choose it". Same with 50 and 26 (that's a stop sign!) - they look like bullet points.

Some of the others are pretty nice though!

Ever read "The Machine Stops" by EM Forster? Over 100 years old, and it's got Facebook style interactions!

Well, according to "The Rise and Fall of D.O.D.O" (Neal Stephenson and Nicole Garland), it was all about magic!

Was going to mention Interface! It's very much Cambridge Analytica vibes - you feel that there are teams as described doing pretty much the same things, just without the direct brain interface.

Personally, I think Anathem is the best of his works, although I enjoyed DODO - the sequel, which he wasn't directly involved with was less good though.

Kind of. I picture it as being a function of input to output, so if the input changes, the output does too, but the output change is based on what changes have been made by the player.

E.g. if you have a hospital which can handle X patients per day and has a reputation of 90 when doing so, increasing the number of patients to 2x would probably decrease the reputation. You don't need to model the full hospital to determine this though, just have a "max patients" value which, when exceeded, puts a fractional multiplier on the output.

Yes, I imagined that a component could provide some inputs (e.g. Grain) and outputs (e.g. Bread) with some default link between the two, and that would apply to all instances of that component within the world, unless a player took control of an instance and modified the behaviour. The nice thing there is that backing out of the instance allows for a different link between input and output to be created, without needing to simulate the full process.

Everything sim. You start with, say, Sim City. You find that your rail network isn't working properly, so you switch contexts to a kind of Transport Tycoon style game, where you can optimise the train schedules and destinations. You realise that the factory you're delivering stuff to is struggling, so you switch context to a Factorio style optimisation game. You realise that the inputs to the factory aren't pure enough, so you switch context to an Opus Magnum/SpaceChem style atomic manipulation game. You zoom back out, and find that your hospitals are struggling too. Context switch to a Theme Hospital/Two Point Hospital style sim. You need medicines, so switch to a Big Pharma drug production sim. You can optimise the machines here with the same interface as you used for the factory. Zoom out a bit, and you can see a football stadium, with the option to switch to a football management game, or to jump into a game and start playing directly. You zoom out again, and are now looking at a country where your city/region is just one part. You can context switch to a country management game. Keep going out, and you realise you're on a planet, so start working on a space program. Keep going out, and you can build a Dyson swarm and get some interplanetary government vibes going, all while being able to zoom back in on any part.

Pretty sure my original concept was for this not to be a single game so much as a common interface for basically every other game, where unoptimised parts work, but aren't great, passing a kind of middle-of-the-range set of values whenever queried. By linking multiple games together, you'd be able to control everything.

Nice - although the coverage locally is a bit spotty (I'm not talking missing shows, I'm talking missing theatres!).

I have a 5yo and play a wide range of games with her. She has various "learning games" from Orchard Toys. She has some junior versions of various mainstream games (e.g. Scrabble, Dobble) and junior versions of more gamer type games (e.g. Ticket to Ride: First Journey, Catan Junior, Concept Kids). She's got some (ok, a lot) of Pokémon cards, including the Battle Academy sets which give 3 roughly balanced decks for about £20, which give a decent introduction to the game. She can also play various other gamer type games - Zooloreto, full size Ticket to Ride, Thunderbirds co-op game, Kingdomino, etc.

Also have a 3yo who is awesome at Dragonimo and likes joining in with things like Uno.

I'm pretty sure the key thing is to teach kids that games are supposed to be fun and that there are a lot of options. There are games on my shelves which I don't plan to introduce them to for a while yet, but mostly because they are a bit too dry (hard to get kids interested in some themes) or require a bit too much in the way of reading without your opponent helping, but I'm sure they'll get introduced eventually!

This is such a good point. I've been pushing back for quite a while, and have generally had a positive response where the company revises the contract wording to a more acceptable level.

I feel that the principle of least privilege would be a good point for employment contracts to start, rather than the current approach of "try get control over everything employee might think of whilst employed, even if it's during their own time and unrelated to the business"

If you link to a page, whatever text you put in as the body of the link will remain. The link itself won't go anywhere, but the content you have added to it will remain. In this case, it's as if the link text also vanished when the target page vanishes.

That would be an interesting solution to link rot, admittedly - lots of older pages which are just empty lists formerly containing links to now defunct websites!

I was looking at this a couple of weeks ago, and compared to some alternatives (e.g. opencti) it seemed a lot less polished. It was still easier to get running than Cortex though, at least for a basic look.

The keyboard only shows the top four boards though!