I don’t see this article actually arguing against GitOps. It just argues that the policies in place for GitOps need to make sense for the environment you’re developing in.
Obviously, the level of auditing and reviewing for infrastructure changes in a Prod environment make no sense for a Sandbox environment, and there’s nothing in GitOps that implies these need to be the same.
Ideally at every phase of development, you have very legible infrastructure that can be shared and iterated on by a team. The CI pipelines backing this should offer rapid turnaround times, and things should be easy to test.
All things which the general GitOps concept still works in tandem with.
One useful thing I discovered recently about zoxide is that it has a basedir flag, so in theory you scan scope your query to the directory you’re in or based off some git root.
something like
alias zg=‘zoxide —basedir $(git rev-parse --show-toplevel)’
My current assumption is that other classes of assets, assuming technological progress continues at its current rate, will grow significantly faster than demand for land.
So the economics that once made homeownership favorable, no longer exist.
Holding the assumption that your landlord operates on favorable conditions (mine is pretty responsive and rent increases are controlled), I’m not sure I have a good reason to opt to purchase a house unless I’m planning on occupying it for the next 2 decades at minimum.
I can’t help but think purchasing is an emotional decision, unless the location you live in allows you to buy for a similar rate to the mortgage pricing, but I’ve only observed this in LCOL areas.
But this has been pretty nice for me.
https://mwitch.viraat.dev/
It’s also open source if you want to customize it for your own preferences (pinned apps, custom keybinds, etc)