> How can something be both “usually not a bottleneck” that usually “takes a significant amount of time” ?
I dont understand what you dont understand. Is everything that takes a significant amount of time necessarily a bottleneck? That seems implied by you but makes no logical sense.
The funnel into the programming work is often more difficult/time consuming/resource intensive than the programming.
Also, sometimes its not as costly but should be. And insufficient time and resources were spent up front which caused the coding portion to take a lot longer than it should. In which case the programming time may appear to be the bottleneck but it was still really the funnel leading into it.
> Sounds like you might really enjoy a PM role
Enjoyment isn't really a factor in terms of what work needs to be done. And designing technical features isnt really a PM responsibility.
I dont understand what you dont understand. Is everything that takes a significant amount of time necessarily a bottleneck? That seems implied by you but makes no logical sense.
The funnel into the programming work is often more difficult/time consuming/resource intensive than the programming.
Also, sometimes its not as costly but should be. And insufficient time and resources were spent up front which caused the coding portion to take a lot longer than it should. In which case the programming time may appear to be the bottleneck but it was still really the funnel leading into it.
> Sounds like you might really enjoy a PM role
Enjoyment isn't really a factor in terms of what work needs to be done. And designing technical features isnt really a PM responsibility.