[movpasd]

There's an "expert trap" in here I think, at least this is something I experience. When you are good at something, it's a lot less effort to draw on that stuff, and you usually get instant easy positive feedback from non-experts. So, for an engineer, that's code and tools and the like, but also productivity systems and other abstract thinking modes that are useful in programming. On the flipside, actually thinking about your product and domain is hard. So, it becomes psychologically easy to get caught up in technical things that are comparatively easy mental and social reward per unit effort, and you feel productive. But it's not always objectively the best use of time.

[Yokohiii]

Just the other day I found out about a study that measured coding productivity. They compared CLI tooling to simple actions. The CLI users _felt_ more productive, but they were not.

Then again, the question is, if the simple action needs to be changed, how hard will that be?

[skydhash]

It’s not really about speed (at least for me). It’s about mental friction. Because you’re fluent in your tooling, you don’t spend time thinking about them.