one was a permissions/capability issue, but the other was straight up performance. As someone said above, an AI agent drilled down on both workstreams immediately, so the pivot wasnt too rough
538 karma · joined June 28, 2015
Socials: - github.com/cdaringe - linkedin.com/in/cdaringe
Interests: Cycling, Gaming, Hiking, Investment, Mentorship, Open Source, Programming, Privacy, Robotics, Remote Work, Technology, Web Development
---
one was a permissions/capability issue, but the other was straight up performance. As someone said above, an AI agent drilled down on both workstreams immediately, so the pivot wasnt too rough
With these properties alone the virus like replication of intelligent actors isn’t hard to imagine at all.
The both sides bit is jaw droppingly ignorant if you pay attention to regional and national politics.
Told me Australia in two words
- Adding bezier curve support, adding Western duplex support, to kle-ng for keyboard fab. Wanted to build a BIG keyboard, but get ergo support and the pcb gen working for non trivially large builds
AI products can and do help make the raw models applicable to targeted domains. Think of them as a black box sure, but that doesn’t mean they dont add value.
1. How do you handle worktree merge conflicts and/or integration validation issues? 2. Can i work straight from a list of requirements? I think i saw you support it… 3. I have my variant write a minimal explainer for every satisfied spec, aka receipts. Its pretty great, because i often review the receipts, and if imperfect, mark as NEEDS_REWORK + notes, and it’ll eventually just pick that up on a future iter
Lesson learned. Sheep can wait
Very helpful for a monster repo with giant task graph
I may be the author and only user but i still use it frequently and it was worth the effort just for my own projects