Hacker News new | past | comments | ask | show | jobs | submit
I have observed this in myself when I began to over-leverage AI in my workflows. I've since become more deliberate with what kinds of tasks I will use it for, although I still slip up.

With writing:

Things like brainstorming a plot line for a book with a custom GPT or Claude project that has all of my prior books in its knowledge? Works great.

Things like asking it to write a paragraph or chapter for me - I can rapidly feel my own writing skill, motivation, vocabulary, and ability to grasp/remember the resulting plotlines deteriorating. I don't use it for that anymore.

With studying:

I've been taking a couple of evening uni courses and the thing I found so great is that I've been forcing myself to think through the problems, and take my own notes in every lecture. I may then still get ChatGPT to help explain and reason through some of the concepts with me. And I have it review and 'grade' my assignments. But I refuse to ask it to start drafting answers.

With programming:

This one is tougher. When I am not very personally invested in a problem or codebase it becomes too easy to offload more parts to Claude, and when the company encourages 'vibing' to speed up velocity and you're reviewing and writing a higher influx of lower quality PRs, investment goes down. I still sometimes catch myself committing solutions I only _mostly_ grasp and the rest is hand-waving. A big part of it is a work culture thing.

For my own projects I make sure to understand and have a back-and-forth with the planning agent for each task, or write the first plan myself to go off of. When it comes to producing the code, I have to admit it is much easier to properly review parts of the codebase I am extra interested and knowledgeable in (backend in my case). The frontend I'm less well versed in and also admittedly less interested in, so I do sometimes fall into the trap of "Ehh it works, just commit it" with the goal of doing a thorough quality pass before actual release.

With all of the above, I can feel my ability to think, plan, reason, focus (and my vocabulary) suffer if I go over the line too much into agent offloading. For me keeping that balance is as much about maintaining my own long-term brain health as it is about producing good output. I imagine younger people growing up with AI today won't even know what that more capable (in my opinion) brain state feels like - to them, the AI-using brain will be the norm.

The place I've come to with AI for writing is to have an idea for a chapter/article/etc, which I take to AI, and tell it to either ask me a bunch of clarifying questions, or try to blow holes in it/challenge it. I'll keep talking to AI and answering questions/handling challenges until the AI runs out of steam, then I'll ask the AI to write out a condensed outline with all the pertinent details of the conversation.

Once I have the condensed outline, I'll re-order stuff, clean it up/tune it up, then do the final writing. This keeps my voice and logical train of thought while avoiding blank page syndrome and some of the organizational mess of condensing notes into an outline manually.