I wrote a blog post about how I've set up VS Code, primarily for Haskell, primarily for work.
Studying the tools I use and getting more effective with them is something I've neglected for the past few years, with the notable exception of getting better at filtering email (when I left PayByPhone I think I had north of 200 Outlook rules putting things in the right places). Mostly I've been working with VS Code and fitting it to my habits, but I also took some time to write templates for common tasks in Roam.
Customizing tools can be high-value, but not all tools are as easy to configure as (say) VS Code, so the payoff is hard to identify up front. I should probably err on the side of trying more, though.
Studying the tools I use and getting more effective with them is something I've neglected for the past few years, with the notable exception of getting better at filtering email (when I left PayByPhone I think I had north of 200 Outlook rules putting things in the right places). Mostly I've been working with VS Code and fitting it to my habits, but I also took some time to write templates for common tasks in Roam.
Customizing tools can be high-value, but not all tools are as easy to configure as (say) VS Code, so the payoff is hard to identify up front. I should probably err on the side of trying more, though.