Comment by brookst
1 month ago
This is true.
However, your ability to write specs and validate requirements before starting to build will increase.
It’s just trading deep hand-on expertise for deep product/spec expertise.
No different than how riding the bus all the time instead of driving results in different skill development (assuming productive time on the bus).
I think there is a big difference. You could and should have both knowledge. This applies to whether you're a lowly programmer or a CEO. Knowing the details will always help you make better decisions.
That’s the credo I’ve lived my life by, but I’ve come to believe it’s not entirely true: knowing the details can lead to ratholes and blurring requirements / solutions / etc. Some of the best execs I’ve met are good precisely because they focus on the business layer, and delegate / rely on others to abstract out the details.
I can’t do that. But I’m coming around to the value in it.