Isn't it easier to just write the code???

Depends on the algorithm. When you've been coding for a few decades, you really, really don't want to write yet another trivial algorithm you've written multiple tens of times in your life. There's no joy in it.

Let the LLM do the boring stuff, and focus on writing the fun stuff.

Also, setting up logging in Python is never fun.

Right-- it's only really capable of trivial code and boilerplate, which I usually just copy from one of my older programs, examples in docs, or a highly-ranked recent SO answer. Saves me from having to converse with an expensive chatbot, and I don't have to worry about random hallucinations.

If it's a new, non-trivial algorithm, I enjoy writing it.

For me, it's a lot easier getting the LLM to do it than browsing through multiple SO answers, or even finding some old code of mine.

Oh, and the chatbot is cheap. I pay for API usage. On average I'm paying less than $5 per month.

> and I don't have to worry about random hallucinations.

For boilerplate code, I don't think I've ever had to fix anything. It's always worked the first time. If it didn't, my prompt was at fault.

> Also, setting up logging in Python is never fun.

import logging

Not fun at all.

Configuring it to produce useful stuff (e.g. timestamps, autologging exceptions, etc). Very boilerplate and tedious.

It was really simple, just traversing a list up and down twice. It just didn't see the reason why, so it skipped it all (the reason was to prevent race conditions).