I've been playing with it for almost two years now, and this is what gets me there. ChatGPT never got even close to it.
Ask HN: Why is my Claude experience so bad? What am I doing wrong?
121–125 of 125 posts
Re: Ask HN: Why is my Claude experience so bad? What am I doing wrong?
#122The truth is that there is a lot of hype. You need to be reasonably experienced and guide it. First, you need to know that Claude will create nonsensical code. On a macro level it's not exactly smart it just has a lot of contextual static knowledge. Debugging is not it's strongest skill. Most models don't do good at all. Opus is able to one-shot "troubleshooting" prompts occasionally, but it's a high probability that…
Re: Ask HN: Why is my Claude experience so bad? What am I doing wrong?
#123The truth is that there is a lot of hype. You need to be reasonably experienced and guide it. First, you need to know that Claude will create nonsensical code. On a macro level it's not exactly smart it just has a lot of contextual static knowledge. Debugging is not it's strongest skill. Most models don't do good at all. Opus is able to one-shot "troubleshooting" prompts occasionally, but it's a high probability that…
Am I crazy thinking that interacting with such a system is a nightmarishly frustrating way to write code? Like trying to write with a wet noodle - always off in some way. Write the code feels way more precise and not less efficient.
Re: Ask HN: Why is my Claude experience so bad? What am I doing wrong?
#124Re: Ask HN: Why is my Claude experience so bad? What am I doing wrong?
#125I got this: https://github.com/hughdbrown/visualize-grid-layouts.git
You can follow how this all happened by looking in `docs/design/`.
The SKILL.md had this description:
``` Collaboratively designs a new software feature with the developer. Explores the existing codebase to ground all technical decisions in the project's actual architecture, conventions, and dependencies. Produces two deliverables:
1. *Product Requirements Document (PRD)* — what the feature does, technical decisions, how it operates, and ordered implementation stages.
2. *Detailed Task List* — within each stage, test-first scoped steps covering tests to write, code to implement, config changes, environment variables, dependencies, and documentation.
Both deliverables are written to files in the project for reference during implementation. ```
You can get Claude to produce the skill for you, too.