I’m joining a hackathon and CC is expected to be used. I want to know all your hacks for fast development. I’ve been mostly focused on ticket -> PR automation and just reviewing stuff (and being pretty chill in between pottering about, or writing other plans) which isn’t going to cut it for this event 🫠 My current weekend improvements:
- ensure that plans are executed with parallel sonnets rather than sequentially. Expect a few breakages but with independent QA agents after it seems good
- reduce plans. Sometimes scope creeps: when a plans done, if it’s too big, refactor it back down like an actual human would to do the work. Context size reduction => faster implementation
- use haiku for any searching. Don’t be lazy and use sonnet Those that have done a hackathon, any other advice would be appreciated too. I’m not very socially confident with this kind of thing so it’s a bit daunting. submitted by /u/dev_life
Originally posted by u/dev_life on r/ClaudeCode
You must log in or # to comment.