Games

A lot of it is about how it's used. I think the second point is the most important. A lot of [software] engineering is familiarity with the topic and tools used. The mental map of the architecture of how everything fits together is powerful, and giving that all up to an LLM is a huge loss if you are using it to write anything more than a basic function.

In my practice in use it in a couple spots:

• rewrite this section in a more readable, standard manner (when ive laid down some real slop of my own). For me this is as much a learning opportunity of copying something out of stackoverflow. I take a moment to understand what change was made so I can use the same pattern in the future where appropriate.
• read this file and add docstrings and comments (which will be like 75% correct and at least save me the time of formatting everything. I obviously need to make corrections and add context about how the functions are used that the LLM doesn't have access to.

Using it more than that feels like a heavy risk of brain drain to me.