[WirelessGigabit]

I worked with a colleague who didn't write JS for a long while. My colleague purposefully tried to build the project with the output of ChatGPT.

One of the problems my colleague ran into is that once things don't work as expected, debugging is really hard. When you build a system yourself you have a knowledge foundation, and a process that you repeat over and over. They are intrinsic to your development process. They allow you to quickly debug problems. But not so much when dealing with this kind of generated code. Much more often did we have to resort in peeling back the layers and realize something a couple of layers down was wrong.

One example is that the generated code does not contain take age of the code into account. So all of the sudden you're mixing ESM and non-ESM packages and you get the weirdest errors.

> sometimes I would spend 10 minutes crafting a prompt, forcing me to fully understand and articulate my own line of thinking about what I was trying to achieve .

The reality is that this is one of the reasons why I actually love coding. As someone who has many times unconsciously said the wrong things and pissed off people (sorry!), using a limited grammar to express my wants feels so much safer. The grammar is limited. It is extremely explicit. There is no ambiguity. And bar a few esoteric languages, there are no emojis, and there is no need for me to be polite or offer a tip.

[wernah]

I found this to be the case as well. My out productivity declined as the project became more unwieldy. I wasn't using ES6 so would very much like to modularize things and use imports/exports next time. "Working code is working code" but I'd dread the idea of someone collaborating on top of my spaghetti. Lot of lessons learned in that respect. Having to reset ChatGPT's understanding of the latest code was tiresome.