That sounds 💯 like a developer workflow 😅

Can you check again?

Feel free to send my contact details to your employer. I’m used to having these conversations and can definitely help build a plan to do this more maturely.

I completely understand how you feel and this is a challenge for a lot of developers around the world at the moment. Expecting all these efficiency gains without of the box AI tools without investing in the people is setting this evolution up for failure.

I’ll have a look as I upgraded Hugo from an ancient version yesterday 😅 Thanks for the heads-up!!

My advice? Do not oppose this evolution but learn how to use it reliably. If you know about worktrees, I’m sure you know about engineering excellence as well. Leveraging AI effectively needs people like you teaching these habits to others, and AI can be your best buddy in achieving these results.

I’m with you on this 100%. As I state in the post, this workflow isn’t new, it just got supercharged with the use of agentic AI.

That’s what it’s about really. I want to find a way to work on this more structurally instead of taking up more family time. Shouldn’t be a crazy ask, yet here we are.

That’s my worry indeed. Now, I couldn’t theoretically stop anyone without legal action, but I’m afraid it would have this side effect.

🤞🏻

Wait, I misinterpreted your reply. That could work for local files, but not remote nor extended configs. So in the end it’s a lot more reliable to add the ability to always live reload.

That’s not the problem. You still need the data. So by using that format in the cache, it’s just 4x times faster to load the configuration file compared to parsing the JSON again.

The only downside is that this no longer allows to edit and and see changes on the fly which is why you’ll also get an oh-my-posh enable edit CLI command to force parsing the configuration every time.

I know 🫣