Just this past 12 months both my drivers license and passport have been involved in data breaches and there are no penalties or recompense for the companies at fault, so my patience for providing ID is near zero.

If I was one of these pseudo-oligarchy members, I would be a lot more worried about a large percent of the population becoming disaffected and angry.

Once this phone needs updating, I’ll be swapping carrier to one that has regular SIM cards.

Personally, I log off at 5pm friday and don’t think about anything work related until after at least one coffee somewhere in the vicinity of 9am the next monday.

My teams pick up a piece of work, check out the code, run the equivalent of docker compose up, and build their feature. They commit to git, merge to dev, then to main, and it runs through a pipeline to deploy. We do this multiple times a day. Doing that with a large monolith that combines all these endpoints into one app wouldn't be hard, but it adds no benefits, and the overhead that now we have 4 teams frequently working on the same code and needing to rebase and pull in change, rather than driving simple atomic changes. Each service gets packaged as a container and deployed to ECS fargate, on a couple of EC2 instances that are realistically a bit oversubscribed if all the containers suddenly got hammered, but 90% of the time they don't, so its incredibly cost effective.

When I see the frequent discussions around microservices, I always want to comment that if you have a disfunctional org, no architecture will save you, and if you have a functional org, basically any architecture is fine, but for my cases, I find that miniservices if you will, domain driven and sharing a persistence layer, is often a good way to go for a couple of small teams.

Not to mention, I can find AI perfectly impressive and still have absolutely no day-to-day use for it… certainly not enough to justify it taking over my operating system experience.

Where we have a need for server side, nodejs just never felt natural for us so we stuck with java springboot or flask/fastapi as appropriate.

I think the system prompt or training data probably focuses on marketing websites, it didnt manage to make a settings page or a canvas game, but did make a site telling me how to make a canvas game :)

How does it interpolate the path to make the prompt? (Havent checked the code yet…)

Australia is a tiny market but before the big american companies bought them out, our local AnimeLab offering was one of the worlds best. If a new similarly oriented offering could launch and compete I’d love to see it, but sadly only pirate operations can do so, and are doing so effectively.

In Australia, AnimeLab used to be the gold standard. It had a polished app and dedicated team, mainly because it started out as a piracy site and went legal, keeping the passionate team etc.

They got bought out by Funimation and the app was shelved in favour of Funimation’s far worse but still usable one. Then Funimation was bought out by crunchyroll and their app was also shelved for crunchy’s terrible one. I kept paying for a while after that but after a few instances of missing subs and poor releases I gave up and just kept my Japan side subscriptions going, while getting my Australian side content ‘elsewhere’.

I’m sad the market doesn’t seem big enough to support a new competitor with a focus on quality, but as mentioned in TFA, exclusivity deals make this even harder than it otherwise would be. Shame really, as lately the releases from even the various smaller anime studios have been rather excellent.

Most of my reporting tools implement similar logic to the python in the article, so handy to keep around for those use cases…

What I’m curious about is how this will affect smaller regional markets such as the ASX, if our investors who prefer American markets will return those dollars here or into larger Asian markets closer to the NYSE in volume.

Rather than the specific language, I’m more thinking of the domain, meaning ‘web devs who know go’ being a smaller cohort than ‘webdevs who know react’.