Humans are notoriously worse at tasks that have to do with reviewing than they are at tasks that have to do with creating. Editing an article is more boring and painful than writing it. Understanding and debugging code is much harder than writing it etc., observing someone cooking to spot mistakes is more boring than cooking etc.
This also fights with the attention required to perform those tasks, which means a higher ratio of reviewing vs creating tasks leads to lower quality output because attention is depleted at some point and mistakes slip in. All this with the additional “bonus” to have to pay for the tool AND the human reviewing while also wasting tons of water and energy. I think it’s wise to ask ourselves whether this makes sense at all.
To make sense of that, figure out what pays more observing/editing or cooking/writing. Big shekels will make boring parts exciting
Think also the amount of people doing both. Also writers earn way more than editors, and stellar chefs earn way more than cooking critics.
If you think devs will be paid more to review GPT code, well, I would love to have your optimism.
I’m too unfamiliar with the cooking and writing/publishing biz. I’d rather not use this analogy.
I can see many business guys paying for something like Devin, making a mess, then hiring someone to fix it. I can see companies not hiring junior devs, and requiring old devs to learn to generate and debug. Just like they required devs to be “full stack”. You can easily prevent that if you have your own company. If … Do you have your own company?
