I doubt there'd be much complaint about a dev who switched to Linux but chose Gnome over Hyprland. VS Code and other tools are going to work the same on either one.

Devs use some combination of the setup/suggested dx from their company, their own preferences/tools, and a large amount of informally socialized tools and setup that other devs at the company use.

Trying to shift deliberately towards a more collectivized experience can help a lot. When one dev goes to work with another, having a stable base to work from can help a lot. Source files tend to be in ~/code, we tend to use rvm for version management, we use Y LLM-tools with Z MCP servers.

Being able to dogfood your working environment together feels impossible & absurd, but leaving everyone out there doing whatever they cobble together feels at least as absurd.

37signals is also sort of home of Rails, where "omakase" and convention over configuration are deeply woven into the lore. The idea of them building something that just works out of the box & is tuned makes hella sense.

Beyond just cobbling together tools, having a practice can help so much. My god I've totally become such a more empowered vim user after switching to astrovim! Yeah the very amazing automatic tool config helps so much. Sure the modular lazy vim plugin experience and the slick as hell astrovim community packs have made layering in new tools & configuring existing ones mostly very easy. But holy heck, astrovim has a visual menu for the leader key. It turns vim from having an implicit depthful interface to an explicit visible interface.

Someone configured all these tools to show up somewhere, made a pattern for walking through tools. It's game changing: having folks make some sensible dev centric defaults and make them visible has made all the difference for me. https://docs.astronvim.com/#-features