Comment by dandano
2 days ago
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.
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.