4 ms·

It reduces the friction of coding tremendously. Coding was usually not the bottleneck but it still took a significant amount of time. Now we get to spend more t

It reduces the friction of coding tremendously. Coding was usually not the bottleneck but it still took a significant amount of time. Now we get to spend more time on the real bottlenecks. Gathering requirements from end users, deciding what should be built, etc.

irishcoffee 9mo ago
> It reduces the friction of coding tremendously. Coding was usually not the bottleneck but it still took a significant amount of time. I don’t think I agree. How can something be both “usually not a bottleneck” that usually “takes a significant amount of time” ? > Now we get to spend more time on the real bottlenecks. Gathering requirements from end users, deciding what should be built, etc. Sounds like you might really enjoy a PM role. Either way, LLM or not, whatever gets written up and presented will have a lot of focus on a bike shed or will make the end user realize allllll the other things they want added/changed, so the requirements change, the priorities change… So now we just don’t get to do the interesting part… engineer things. If I wanted to be a PM I’d do that.
- switchbak 9mo ago
  Just because the magical fairy helps you write things, you still need to ensure it's engineered properly. Especially at the macro level. Some day it'll handle that, but for now it's very bound to make silly decisions that you need to be on top of, especially as those compound in a large scale system.
- nonethewiser 9mo ago
  > 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.

irishcoffee 9mo ago

> It reduces the friction of coding tremendously. Coding was usually not the bottleneck but it still took a significant amount of time. I don’t think I agree. How can something be both “usually not a bottleneck” that usually “takes a significant amount of time” ? > Now we get to spend more time on the real bottlenecks. Gathering requirements from end users, deciding what should be built, etc. Sounds like you might really enjoy a PM role. Either way, LLM or not, whatever gets written up and presented will have a lot of focus on a bike shed or will make the end user realize allllll the other things they want added/changed, so the requirements change, the priorities change… So now we just don’t get to do the interesting part… engineer things. If I wanted to be a PM I’d do that.

switchbak 9mo ago
Just because the magical fairy helps you write things, you still need to ensure it's engineered properly. Especially at the macro level. Some day it'll handle that, but for now it's very bound to make silly decisions that you need to be on top of, especially as those compound in a large scale system.
nonethewiser 9mo ago
> 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.