None of the walkaround time is saved from other things I'd say. I don't work through lunch, my lunch break has gotten longer because I make food instead of eating in the canteen, and lunch is one of the enjoyable times when I do not feel guilty for not working. The 'enjoyable because I do not feel guilty for not working' is somewhat true for the meetings now as well.
While working in an office, I considered myself one of the more productive members of my team, and one colleague called me the most productive team member. Now, working from home, I am often standing up, walking around and dreaming for hours. I am glad I was allowed to return to an office alone this Monday. I am not 100% sure it is all due to WFH because my assigned project changed at about the same time but I can only hope I'll recover when I'm in an office again, even if nobody else is there to watch over me.
We used the ansible module at work but we had to fork it internally and extend it heavily. I would suggest you try https://github.com/mrparkers/terraform-provider-keycloak instead, because terraform cleans up after itself (it deletes resources that you deleted from code, rather than leaving them behind) and terraform is also much faster, because it auto-parallelizes according to the dependency graph. The terraform provider also seems much better maintained than the ansible module.
They are currently auctioned almost nowhere. Instead, they are permanently owned by incumbent airlines who never paid for them. Additionally, incumbent airlines lobby against slot auctions, see e. g. https://airlines.iata.org/analysis/the-dangers-of-slot-aucti...
The fact that slots are not available to newcomers is a valuable moat for incumbents.
The trick of using more compile-time knowledge to avoid diffing the tree of elements seems similar to svelte (https://svelte.dev) in the Javascript world.
I have great respect for your work. Do you have ideas or plans how to automatically delete objects in the cluster after they were deleted from the code? Terraform and pulumi are notable for maintaining their own state outside of the cloud provider or kubernetes, and this state can go out of sync, but `kubectl apply --prune` should not need that.
Isopod is notable for allowing the fetching of remote data that can then be used to configure the kubernetes objects. Terraform and pulumi are the only other ones that allow this. Bad about isopod is that the tool does not appear to automatically delete resources in the cluster after they are deleted from the code, and instead, a delete function must be called manually. That is a conceptual weakness compared to terraform and pulumi, and also a weakness compared to `kubectl apply --prune`.
The track is instead clamped so strongly that it can maintain its alignment even under thermal stress.
https://en.m.wikipedia.org/wiki/Track_(rail_transport)#Conti...