[JP44]

I wouldn't call that cursed but useful tooling usage. Had the same scenario where I wanted to work on a tool for a project written in Go, of which I know next to nothing. Claude code was able to spit out 100's line of code that worked and I (almost) understood and could explain what was happening where and why, but I had no chance of debugging or extending it on my own.

I've limited myself to only use Claude's webchat to do almost exactly as you've mentioned except creating snippets, it can only explain or debug code I enter. I prompt it to link relevant sources for solutions I seek. Plus it assists me subdivide, prioritise and plan my project in chunks so I don't get lost.

It has saved me a lot of time this way while still enjoying working on a project

[Harsha_Jaya_13]

Yeah it actually is beautiful, because we get the brainstorming ideas so that ,sometimes we lack the experience in coding to get that idea to be converted into a powerful working application ,we need the artificial intelligence so that ,we can always enjoy the process , only if we are loving the work we are doing ,I mean there is a lot of difference between blind pasting and completing a work ,just my opinion of what I have been through

[dandano]

Interesting how you write the code first then put it into claude. What's the reason there? I guess that is where I find the most benefit is not writing out the syntax, even though I could I just can't be bothered. I often start with the snippet then refactor to the style of code I like. For code I don't know that well like c++ I like to get a snippet so I can then research into those functions that is used and go from there.

[JP44]

Mostly because I learn the best by doing, reiterating and then expanding, especially with programming. Essentialy, building a form of context or mindmap if you will.

When I was testing Typescript/React I followed the docs and some guides and got thrown in the deep end, I could follow and understand the steps but not reproduce or adapt them because the (or my) scope was limited, also, libraries; so many libraries used..

By starting with a HelloWorld and expanding it step by step, going back and forth. Using forums/blogs to see available functions or similar oss projects for what I wanted to do, then use the docs to read about the used functions.

Kagi already helped save me a lot of time by reducing spam posts and using language shebangs etc. With Claude I either give a snippet that I cannot translate or am stuck on, like you do, or I'll prompt something like: 'describe steps used to get from input=.. to output=.. in go, this/that needs to be done/transformed, do not output actual code'.

I guess the main thing is that I want to be engaged in my personal/hobby projects and think about the problem and solution and not just copy/paste because that takes the fun away (in case of work, if it makes me more productive I'll take it. Just need to remember I'm the one who is responsible). It's like buying a pre-assembled puzzle.