3 comments

  • ClachDev 23 minutes ago

    It makes sense that I build Voro using itself which highlighted some issues with it.

    Firstly, some "human" tasks get stuck at the top of the priority list because the effort involved seems large relative to agent dispatched tasks. I feel like this is a common scheduling problem?

    Secondly, its sometimes hard to judge progress. When the code moves fast, it's impossible to keep it all in your mind at once. Instead I found myself focusing on the plan and making sure it was what I actually wanted and then going lighter on the review of the code, testing the desired functionality.

    I feel like agentic coding is like learning software engineering all over again. How do we take advantage of AI to write the wrote bits quickly, but keep the quality?

  • fottly 31 minutes ago

    Nice, this scratches an itch I've had for a while. Curious how you're handling attention/context persistence across sessions, local only, or synced somewhere?

      ClachDev 21 minutes ago

      Thanks! It's local only (in a sqlite db) but I've been running it 24/7 with Claude Code next to it with remote access. That means I can interact with it through Claude from my phone etc if I need to. There is a skill so claude knows how to interact with the tasks. And each claude session is named after the task so its easy to iterate on a task on the go.