jolaflow
Joined 6 months ago
Karma
77
Submissions
57
Member since
Apr 25
Recent submissions
Comment · 24 days ago
They went woke. Never seen anyone resembling the average dev in their promotion… You can see the correlation in their downtime graph.
Comment · 26 days ago
When code becomes easy to shape, internal rigidity remains a challenge.
Some reflections from the project I'm working on. Does this resonate?
Comment · 29 days ago
I think that strictness will be the most important feature going forward. Whichever framework creates the safest boundaries for agents to work within will gain traction. That's why I think Effect has a bright future.
Comment · 1 month ago
That's great!
Comment · 1 month ago
I wish the MCP protocol supported push notifications from the app to the model. That'd make for a much nicer integration, with less overhead for this kind of interaction.
Comment · 1 month ago
For this to work, you'd need to be able to replay the workflow after the fact. Spent last year and a half building an issue tracker that let's you replay the board and code. It lives in your repo and syncs via Git.
https://ljtn.github.io/epiq
I sometimes leave it on before going to sleep, instruct it to tag any deviations from the plan with a fork tag, and if needed a "human-input-needed" tag that I can filter for and review in the morning.
Comment · 1 month ago
Got it! I am not up to speed on Claude cloud sessions yet. Interested to hear how that works out for you. Let me know if you figure out what's getting in the way, I'd be happy to look into it.
Comment · 1 month ago
You might have use for an issue tracker I've been building the past year and a half. It lets you inspect diffs inline in the ticket, and replay the board to see how the workflow evolved over time via a timeline scrubber.
It stores issues as an immutable event log in your repo, so you can go back and inspect the context behind a change without having to litter the code with comments. Helps with traceability of intent.
Comment · 1 month ago
Curious to hear how you find it after trying it!
Comment · 1 month ago
I think it works well for tracking intent. I tell my agents to use a "human-input-needed" tag when there is a high stakes decision fork, and then I just filter on that tag, immediately highlighting blocked workflows. I think you can get a long way with clever tagging, filtering + time travel.
Comment · 1 month ago
You are totally right in that it makes no sense. It seems like the skill.md had regressed as I had updated it via agent proxy. Thanks for pointing it out, the skill has been brushed up.
https://ljtn.github.io/epiq