Downvoted because it didn’t end with /s.

“All female shark tank” is my new band name.

*removed externally hosted image*

Technology replacing people has been a pretty consistent theme of the last hundred years or so—how many actual people does it take to build a car? What about all those skilled engineers? Humans have been building tools in order to put in less effort since the stone age. I don’t think we’re going to argue our way out of this one…

Except models trained on medical images are actually pretty good at diagnosing some disorders. Models trained on random samples of the internet, not so much.

John McCarthy was right—AI is a terrible term.

Just started running Arch + KDE on a Kingston Traveller to experiment with setup. Installed from live usb iso and then ran archinstall to the same device.

Runs nicely on my dell xps laptop and my desktop with 3 monitors connected to an Nvidia 1070Ti.

Looks like it’s time for a little refresher: https://m.youtube.com/watch?v=AKx5xDVMpW0

How often did you catch it disappearing?

New Order—Blue Monday. Broke my first hifi listening to it too loud.

Yes, all bets are off this year. Plus we now have a ‘claim’ even though it was all paid by the other party. No idea how much difference things like that make but certainly not comparing like with like.

Not true—at least didn’t used to be. For 3 years, Tesco renewal was cheaper for us than any online comparison site (same excess, options etc). That included Tesco new quote.

But definitely never take a renewal without checking.

Narrowly missed out on spending the day with Patrick Stewart at an event in London. My wife went instead and she doesn’t even like Star Trek. She said he was very nice though.

We’ve got some. Pop round.

Who keeps a Costa wrap long enough to see a recall?

“Starlink was not meant to be involved in wars. It was so people can watch Netflix and chill and get online for school and do good peaceful things, not drone strikes.”

https://m.youtube.com/watch?v=Skl71urqKu0

We’ll of course it depends on the scale of the changes. Depending on how your calling them, the version could be in the url, such as zooms api including /v2/ in the urls. Then you can introduce /v3 with many changes whilst leaving /v2 in place for some amount of time.

If /v3 also means a complete change of database and other underlying infrastructure (eg removing the concept of a zoom meeting), then you’ve got different challenges. Those are probably about overall design, not api.

One approach I’ve seen (from a user pov, not dev, so I’ve no idea of the code bloat it might cause) is to pass the API version number in the call. Then your api can be backwards compatible for 2 or 3 versions, giving other users time to upgrade their code. It de-couples things to give you all a bit of slack for both rapid iteration and stability.

But it also depends on the ‘contract’ between you and the users so be very clear how long / how many versions will be available. Probably will involve a ‘use by’ date.