Thanks! That'll be useful to keep my ad-hoc degug files out of the git status list
That seems to be US specific. I've been pestered by recruiters since late 2025, almost to the 2022 levels.
From the docs in GitHub: "The size of the dots corresponds to the number of reviewed papers for literature reviews (non-reviews have the smallest size)..."
In k8s, being able to use things like External DNS and automatically and declaratively manage DNS entries with code saves so much time you won't want to go back once you get used to it.
It takes a while to get your head sorted around it and also to deploy but automagically having your DNS entries, your certificates, et etc sorted feels great.
You hired this guy to do new things, let him do them (as a PoC)
Congratulations!
Oracle ...
I see this as the EU moving pieces to influence the UK people to revert brexit in a generation (Bregret? Breback?). It benefits the demographic that was already against brexit and keeps the idea od Europe in their minds.
I doubt is for cheap labor. I work in London and in a team of 20 we have a single British, and the few in the company tend to have an easier path for leadership, so why leave? That has been similar in all my previous jobs.
If I could be bothered to sit and write down a distilled version of my last decade at work it would be something very similar. Any junior SRE can benefit from this.
I like helm and I think the main reason is that I have way less exposure to helm internals than you.
Helm seems to be designed to follow the write-once-apply-everwhere principle. My experience is
- find a promising k8s tool
- get the chart
- read the values file
- apply (as a flux helm release object)
I almost never need to untar and check the templates, helm for me is an easy to use high level abstraction.
I guess that's why they sell it as a package manager. The experience of writing the chart sounds dreadful, but using it is mostly trivial.