“the cost of trying ideas had collapsed”

This is a critical observation of the vibocene.

Nice post, one more thing to keep in mind with your StatefulSets is how long the service running in the pod takes to come back up. Many will scan the on disk state for integrity and perform recovery tasks. These can take a while and mean the overall service is in a degraded state.

Manage these things and any stateful distributed service can run easily in Kubernetes.

This makes a completely valid point when you constrain the meaning of Big Data to “the largest dataset one can fit on a single computer”.

At companies I've worked at "Big Data" was often used to mean "too big to open in Excel" or in the extreme case "too big to fit in RAM on my laptop"

Annoyingly medium data is my term for this.

Around 0.5 to 50 GB is such an annoying area, because Excel starts falling over on the lower end and even nicer computers will start seriously struggling on the larger end if you're not being extremely efficient.

Databases do fantastic with this amount of data, and even quite a bit more. If we would stop using Excel where it makes no sense then the world would be a happy place.

Good find, I think those would be books written in English published by German publishers. The blog post discusses how ISBNs are allocated ... specifically the ones you picture are published by Springer, which is a German company that publishes in the English language.

Considering a specific example: "Forecasting Catastrophic Events in Technology, Nature and Medicine". The website's use of "Group 978-3: German language" is a bit of a misnomer, if they had said "Group 978-3: German issued" or "German publisher" it would be clearer to users.

The names of the groups are taken directly from the official allocation XML from the International ISBN Organization. This is what they call it, I assume to distinguish it from "Germany". Maybe "German language publishers" would be appropriate.

This is really exceptional work, and still works on my ten year old iPad. Great job!

Using helmfile (yet another layer of abstraction on top of helm) lets you get diffs between current and new releases. And it’s all templated so could be dynamic.

At a previous employer they were using helmfile. I don't remember what exactly I needed to do but I needed a value to be templated by helm _after_ helmfile had done its work (iirc) and ended up having to write along the lines of "{{ `{{` }} .Values.something {{ `}}` }}" but actually had more levels of nesting which required use of `printf` iirc and I don't remember how I actually solved it.

My point is though that using string templating for YAML creation is IMO always a bad idea and using helm for anything more complicated than the most basic application always makes me sad in the end. helmfile adds another templating layer and my limited exposure to it made me really dislike it.

edit: I remember now that this was for rendering config for vector, which itself has templating support with the famous `{{ .key }}` syntax. So not entirely helmfile's fault, but I still stick to my point as I needed to get through 3 levels of templating.

Yes, that sucks.

> Using helmfile (yet another layer of abstraction on top of helm) lets you get diffs between current and new releases

Of the config, not of reality. What if someone made a change in the meantime? Or something is in a half or fully broken state?

> And it’s all templated so could be dynamic.

Not dynamic based on things external to that Helm deployment. You can't have two Helm charts referencing each other dynamically, or anything else external for that matter.

This claims to bypass the telematics functionality:

https://www.autoharnesshouse.com/69018.html

> Note for customers retaining OEM headunit: This adapter can also be used for those wishing to remove/disable the OEM Subaru Telematics functions. This is done to eliminate the tracking cabability that Subaru has built into these vehicles. If this is you, we will need to add an additional part to this adapter to re-enable the bluetooth microphone. Please purchase the option 2 adapter near the bottom of this page for this situation.

Is there anything like this for Toyota DCM?

We bought a second-hand 2021 Highlander and thus did not sign any contract allowing our family to be tracked by Toyota. I went on a hunt recently for information on neutering the DCM but have thus far only found speculation and contradictory info.

Yeah it's bad out there. Don't do what the yahoos hacking up their harnesses have done. The Toyota DCM I'm familiar with has 3 coax antenna lines coming in. The outer 2 are cell and the inner is GPS. Pull the cell antenna cables out of the DCM and you should be good to go. Best to hunt down your vehicle's service manual and verify the procedure first.

Awesome, thank you. Seems pretty straight forward.

There's an even more recent post

https://subseacables.blogspot.com/2024/10/facebooks-semi-sec...

hyperscalers are amazing, it's hard to comprehend what's the inflection point financially for them to undergo such a massive investment. Just a matter of time I suppose given all the other things you do at that incredibe scale.

Many of these cable projects are less about saving money on buy vs lease, and more about wanting to have more data transmission capacity between the points on the cable.

It is about expense. It is cheaper to own than to rent if your traffic is great enough. And ownership provides control and better management.

This is exceptionally cool work. I’d love to see it running.

I would definitely approach this problem by having the LLM write code to scrape the page. That would address the cost and accuracy problems. And also give you testable code.