Hacker News Reader

That’s a great outcome for 2 hours. If you’re willing to share, what was your rough workflow/prompt sequence (project overview → reproduce → propose patch → add tests → iterate)?

View on HN

First I basically described the project. Since it's quite small, it's easy to give a small summary. Then I started out describing my goals, that I wanted to fix some user issues. Then mostly gave the issue description, some extra information (my idea of what might be wrong). 4/5 times, it made the correct decision and I didn't have to promt any extra. I did have to review the code and polish some minor parts though.

I tried to focus on staying on the subject. For example when I wanted to embed the themes to create a theme switcher ad-hoc and that was done, it could easily generate some new themes for me without any issue at all.

After every edit, I did a `git diff`, modified if needed (using vim), then ran the program and tested it out.

My experience is that it's always easier to fix things fast/correct if you already know the codebase and can give hints to the agent.

Thanks for sharing! The "stay on subject" and git diff workflow tips are useful.

Reply on news.ycombinator.com