It’s alright. I actually was on a similar, albeit just a month long, phase when I switched to KDE. I used VSCodium before and switched (back?) to VSCode after two weeks.
The main reason was extension support. I didn’t notice how much I leaned on those before switching. For example taking notes became more cumbersome and journaling in Typst became impossible (from the editor at least). I have been expecting a lot from my IDE that aren’t really its responsibilities.
Actually programming was a perfectly fine experience so I kept trying to make it work. But at some point a project required me to run dev containers. I had VSCode installed for that anyway so that was the end of it. Though by now I have basically completely switched to Neovim.
I recommend trying out Neovim (Maybe Emacs but I personally never tried it). Or if you prefer a GUI, or don’t want to learn their system, definitely give VSCodium or VSCode a shot. Those four have a much greater assortment of plugins so it’ll be a lot easier to get your editor to behave how you want it to. Though this comes at the cost of a higher memory and cpu footprint.
I’ve mainly been looking up some good ways to backup my Podman services. I manually copy my volumes every couple or months or so. (Which I was thankful when my hard drive started failing on me). I saw a post about Portabase here last week and figured it’s time to look into something less involved.
I also used that as an excuse to start moving my 5 mysql containers that each service ran themselves into a single mariadb container.
The updates from the last CVEs were seamless. Nothing surprising since I have very little installed on my Debian server.
I didn’t change my view on anything from the recent CVEs. I always assumed my server can be compromised, so everything sensitive is encrypted anyway, and I update all my systems/software often or automatically. The latter of which comes with its own set of risks I’m willing to take