This seems to work really well in cases where you're just laying down boilerplate. A few cherry-picked comments seem to suggest that React components are an ideal use case - which makes sense, that's a lot of munging and syntax to just render some strings.
However, I find the process of writing these sorts of functions cathartic and part of the process to get into zen-mode for coding. I think I'd feel less joy in programming if all of this was just done by glorified commenting and then code-review of the robot.
I like to think of coding in terms of athletic training, which usually is comprised of difficult tasks that are interspersed with lighter ones that keep you moving (but are giving you a bit of a break). Training for soccer teams often involved lots of sprinting and aerobic exercise - and in between those activities we would do some stretching or jogging to keep our body moving. These sorts of small functions (write a function to fetch a resource, parse an input payload, etc.) are when my brain is still moving but getting ready for the next difficult task.
I hate to be a downer, but ultimately the people doing the planning and allocating budgets at non-tech companies do not care about the nuances of workflows. They'll lay as much cognitive load on you as is allowed, and they'll always have another body to bring in if you end up quitting.
The value proposition here is clear: "This tool will make it harder for your engineers to do time theft. What used to be an hour's long effort of painstakingly hand-coding boilerplate as a way of 'taking a break' will now be at most 5 minutes worth of easy code review."
> However, I find the process of writing these sorts of functions cathartic
That may be true for individual contributors, but if you're trying to build a company from scratch, any help you can get to move faster is a good thing, cathartic or not.
However, I find the process of writing these sorts of functions cathartic and part of the process to get into zen-mode for coding. I think I'd feel less joy in programming if all of this was just done by glorified commenting and then code-review of the robot.
I like to think of coding in terms of athletic training, which usually is comprised of difficult tasks that are interspersed with lighter ones that keep you moving (but are giving you a bit of a break). Training for soccer teams often involved lots of sprinting and aerobic exercise - and in between those activities we would do some stretching or jogging to keep our body moving. These sorts of small functions (write a function to fetch a resource, parse an input payload, etc.) are when my brain is still moving but getting ready for the next difficult task.