I take a hybrid approach. I will describe a simplified problem to the LLM, have it generate a well commented and reasonable approach for the problem. I then use that as a cheat sheet for implementing my actual code. This still gives me hands on codi and more control, without needing to agonize over the details of each coding technique.

This is me also.

I know if I leet code ground myself into the dirt, I’d get better, and more importantly: faster.

But there’s never been any payoff to me full-time coding.. not when the pay is close to coding, and my role wants me to address test tech debt or Nice To Haves tooling, and (until Go) I had to do my 9-5 work in a scripting language…

There’s now more days behind me than ahead, and I no longer want to understand low level details and theories about the kernel or TTY.

All progress is built on abstraction. It has to be.

I'll often get it to write failing tests for me and write the actual code myself.