Damus
Open in Damus
Dev Dave 🧑‍💻 profile picture
Dev Dave 🧑‍💻
@Dev Dave 🧑‍💻

🔎Privacy
📝Finance/Bitcoin/FIRE/Philosophy
🥕 Healthy eating/Nutrition/Fitness/Cooking/Microbiome
🧑‍💻 Dev

npub19jdujzcdsww2c658kv7he0v4svecjnf95qp7x2m2r5vhuqe73cqq85vvksnpub
[email protected]lnurl
Relays (6)
  • wss://relay.damus.io/ – read & write
  • wss://nostr.oxtr.dev/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://nos.lol/ – read & write
  • wss://nostr.mom/ – read & write
  • wss://relay.utxo.one/ – read & write

Recent Notes

shoe · 4d
That's right, but that's not the point.
Rod · 6d
Invest time in building test harnesses. E.g. Playwright and Maestro. Let it run your app/process fully end to end, and insist it does so and assess it as success before it returns.
 Dev Dave 🧑‍💻 profile picture
Dev Dave 🧑‍💻 @Dev Dave 🧑‍💻
I am already doing something on these lines. The big disadvantage of, at least playwright, is that it can take a lot of time for testing, making your loop longer. I guess you also notice this issue.

A great solution I found for this is, making a cli first architecture, and then it is simpler to test. The UI only is a thin layer of visualization. If you can move 100% of the features into the cli, your web tests will be minimal, because the features will be fully end-2-end testable via the cli.
Rod · 6d
https://steipete.me/ says something similar. Sounds like a good idea
Rod · 6d
Invest time in building test harnesses. E.g. Playwright and Maestro. Let it run your app/process fully end to end, and insist it does so and assess it as success before it returns.
Rod · 6d
Not usually, but sometimes. Usually the backlog contains all sorts of stuff at various levels of thinking, or blocked by other things. Sometimes I would start a task agent to just "research and expand on this issue and update the GH with a comment" The main flow in VK then is "read GH #123, resea...
Rod · 6d
GH for planning, backlog, sprints etc VK for agent orchestration, multi-agent on multiple projects in parallel, git ops like worktrees and branching done automatically, review like code diffs and element highlights. Then, when it's done to a high level of finish, push the PR and GH for CI, deploy...
Fox trot · 1w
The imposition of a gate is the death of kinetic thought. When a tool transitions from a pure utility to a managed service, it ceases to be an extension of your mind and becomes a lease on your attention.
Rod · 1w
Don't know. We have made a fork of the old version now just in case :blobmonocle: Our workflow is about creating tickets and backlogs in GH, and then task agents pick up and run the tasks by ticket number. So, our agents have GH CLI anyway, don't need anything specific in VK for this.