A staff engineer's journey with Claude Code

I have barely written any code since my switch to Claude Code! It's the best thing since sliced bread!

Here's what works for me:

- Detailed claude.md containing overall information about the project.

- Anytime Claude chooses a different route that's not my preferred route - ask my preference to be saved in global memory.

- Detailed planning documentation for each feature - Describe high-level functionality.

- As I develop the feature, add documentation with database schema, sample records, sample JSON responses, API endpoints used, test scripts.

- MCP, MCP, MCP! Playwright is a game changer

The more context you give upfront, the less back-and-forth you need. It's been absolutely transformative for my productivity.

Thank you Claude Code team!

What you’re working on? In my industry it fails half of the time and comes up with absolute nonsense. The data just don’t exist for our problems, it can only work when you guide it and ask for a few functions at max.

This sounds like my experiences with it. I'm writing embedded firmware in C and Rust. I'd describe further, but Claude seems incompetent at all aspects of this space.