Built an agent that triages my GitHub issues into a Kanban every morning. 40 lines + a cron.
You came from Radar. This view is tuned for discover intent.
You're exploring as a guest
Everything here is public to browse. Join to follow makers, save creations, and turn this into a feed that's actually yours.
Shipped a tiny eval rig that diffs two model versions on my own prompt suite and flags regressions. Writeup soon.
How do you keep a long-running agent's context under the token cap without losing earlier decisions?
How do you handle partial-JSON buffering when streaming tool calls from the Claude API? My parser chokes when a tool_use block spans multiple SSE chunks.
Nj
I haven't found anything in life for the past 20 years that excited me more than Runescape, Fortnite, and my kids!
this is the exact pattern I keep coming back to. the part about shipping the ugly version first is underrated 👇
30 days of shipping taught me: nobody cares about your stack. They care if it works and if it made them feel something.