When I last looked the full body scans for sale seemed to used 1.5T setup, which seems like a waste. The 3T advanced scans looks much more detailed, but it just depends on where you live - I couldn’t find any around.

In my experience, it’s best to bootstrap ArgoCD/flux, rbac and cloud permissions those services need in Terraform and then move on to do everything else can via Kustomize via gitop. This keeps everything sane and relatively easy to debug on the fly, using the right tool for the job.

I think it is because most engineers learn to use Kubernetes by spinning up a cluster and then deploying a couple of helm charts. It makes it feel like that’s the natural way without understanding the pain and complexity of having to create and maintain those charts.

Then there are centralised ‘platform’ teams which use helm to try and enforce their own templating onto everything even small simple micro services. Functionally it works and can scale, so the centralised team can justify their existence but as a pattern it costs everyone a little bit of sanity.

I’ve never looked at it before but this seems pretty solid, definitely worth keeping an eye on or testing.

I feel like the main issue with bidirectional adoption currently is the number of groups trying to maximise their profit, everyone wants a cut of the pie: the car companies, energy companies, ev charging companies, ev charging networks, solar/inverter manufactures and government standard groups. The needle won't move until California or other countries with influence force it. In Japan, from a technology perspective CHAdeMO has allowed for EVs to do bidirectional charging for years now.

Side note - I'm all for any extra safety features but I do find that a lot of the software driven features are poorly designed and implemented. I've had bad experiences with automatic braking and lane keeping when freeways driving where I was lucky to avoid having an accidents, so not being able to disable them permanently is a major annoyance to me. It seems like these features have very little real world testing.

Still that might be cheaper if a product is going eol then fixing issues blocking an eks upgrade path. Inversely it’s hard to see any justification for the price increase, I can’t see support for these versions costing 600% more but I guess this is why AWS make so much money…

My goto moat test: is there an obvious ‘death by Amazon’ route? Amazon can strike fear into entire industries with scale and capital. Very few tech companies could withstand a full frontal assault by Amazon. I can’t see how this trend won’t get worse if AGI occurs during our lifetime.

The only reason there is not more AI or robots doing the majority of the work available to humans, is either it’s cheaper to hire humans or companies just haven’t gotten around to it yet.

It has worked out great so far, some days when there isn’t much wind can be painful but overall it works out better. Even if it didn’t, I’d rather pay a fair amount than have energy companies rip me off.