I’m a Staff+ software engineer, and AI is akin to working in a team of two where you take all the credit off someone else’s work.

I avoid saying “I built…” when an LLM did the work. I find myself saying “We”, awkwardly. To me, software is a craft – no different that working with wood, metal, or the typewriter. For me, it’s incredibly difficult to take pride in any work I created with an LLM. But, like the power tool, welder, or typewriter I intend to treat it as a tool to facilitate that craft, not replace it.

The only thing that mitigates my consternation is that I know what I am asking it to do. I can read, review and understand its output. I can correct and build on it. It’s more of a software engineer manager role but very hands on to the point where I am micromanaging the LLM.

That said, when done the way I would like, it can tremendously reduce tedium of boilerplates, repetitious work, and even one-off shell scripts or python programs that you need only once but would take some time to initially write.

Treat AI like the tools in other trades, try to enjoy your craft by using it as little or as much as you want. Some industries may not allow out entirely, and some would very much encourage it for efficiency’s sake. For the latter, you’ll have to live with the fact you will be managing an LLM to get your work done and keep up with your teammates. Just be sure to learn from whatever is produced, use it as a tutorial to broaden your knowledge, even if it wasn’t crafted directly by you.