HN user

shnpln

9 karma
Posts0
Comments17
View on HN
No posts found.

This is what I do when using AI to read anything I write. Some prompt like "I am going to share with you something I have written and I don't want you to change my voice at all. Can you look for structural issues, grammar or punctuation errors, and things like that". Claude is an amazing editor and I never feel like my writing has been taken from me doing this.

I am in my 30s, my wife and I enjoy collecting the cards still. We go to conventions and try to track down cool cards and trade for them. It is a fun side hobby that we do from time to time to get out of the house and meet new people. I have long since lost my love for the games, and I don't particularly care about the rarest cards. I just like tracking down cards that look cool to me and meeting people along the way.

Yeah, this is a good idea. I will have a Claude chat session and a Claude Code session open side by side too.

Like a manual sub agents approach. I try not to pollute the Claude code session context with meanderings to much. Do that in the chat and bring the condensed ideas over.

Oh yes, I commonly add something like "Use a very granular todo list for this task" at the end of my prompts. And sometimes I will say something like "as your last todo, go over everything you just did again and use a linter or other tools to verify your work is high quality"

I have used Claude Code for a variety of hobby projects. I am truly astounded at its capabilities.

If you tell it to use linters and other kinds of code analysis tools it takes it to the next level. Ruff for Python or Clippy for Rust for example. The LLM makes so much code so fast and then passes it through these tools and actually understands what the tools say and it goes and makes the changes. I have created a whole tool chain that I put in a pre commit text file in my repos and tell the LLM something like "Look in this text file and use every tool you see listed to improve code quality".

That being said, I doubt it can turn a non-dev into a dev still, it just makes competent devs way better still.

I still need to be able to understand what it is doing and what the tools are for to even have a chance to give it the guardrails it should follow.