Hacker News new | ask | show | jobs
by jmathai 80 days ago
This is basically the same workflow I've come to adopt. I don't use any "pre-built" skills, mine are actually still .md files in the .claude/command/ folder because that's when I started. The workflow is so good, I'm the bottleneck.

I've started to use git worktrees to parallelize my work. I spend so much time waiting...why not wait less on 2 things? This is not a solved problem in my setup. I have a hard time managing just two agents and keeping them isolated. But again, I'm the bottleneck. I think I could use 5 agents if my brain were smarter........or if the tools were better.

I am also a PM by day and I'm in Claude Code for PM work almost 90% of my day.

1 comments

I like Claude, at least when the user reviews the code before asking for a PR. But gods I hate tickets/feature requests written by Opus/Sonnet (or worse: Codex or Gemini). If you know/understand your product enough it's probably less of a problem for your team than it is for mine, but each time I see a feature request automagically written in the backlog I know I will have to spend at least 30 minutes rewriting in so that it doesn't take us one hour to refine it collectively.
Is it that the tickets are too verbose?
A bit, but mostly it propose extremely well-rounded solutions that are almost never complete, and sometimes miss a major point. I would rather have my juniors work themselves to understand what is needed, or/and ask me questions rather than follow the ticket that is basically a Claude plan. Right now I am modifying and object that was incomplete and I will have to do a migration because I didn't catch the missing attribute during the PR. It isn't big, and we could have coded workaround instead of redesigning the object, but: workarounds complexify the code, the data is less intuitive, and that also means the person who wrote the original object do not really understand the goals.

With a less 'expensive' ticket, with less explanation about how things should be done, but why they are needed, we would have had discussions, in dailies or 1on1, and that could have been ironed out then.

Yeah, basically Claude generate tickets that are heavy on the 'how' and light on the 'why', and I think that should be the other way around, for multiple reasons, but I'm already long-winded.

Yup. Makes a lot of sense.