My bet is that we'll see a second layer of harness emerge, as self-driving codebases become the target. There will be an application facing harness, orthogonal to the agent facing harness. The app harness will represent the software factory that is emergent for the specific application being developed.
I’ve definitely had a hunch about a software factory harness kind of thing.
Your thoughts on the matter seem clearer than mine.
I’m kind of relieved to see so many stages; that’s something I’ve grappled with conceptually. The volume of (sometimes optional) stages has made it hard to resist the temptation to hack something together with a GHA workflow.
I salute your choice to support distributed; that’s a requirement in my book.
rrook · · focus · HN ↗
Anyway, here's mine, still wip:
<a href="https://hale-lang.org/docs/dna/" rel="nofollow">https://hale-lang.org/docs/dna/
<a href="https://github.com/hale-lang/hale/issues/690" rel="nofollow">https://github.com/hale-lang/hale/issues/690
tdg5 · · focus · HN ↗
Your thoughts on the matter seem clearer than mine.
I’m kind of relieved to see so many stages; that’s something I’ve grappled with conceptually. The volume of (sometimes optional) stages has made it hard to resist the temptation to hack something together with a GHA workflow.
I salute your choice to support distributed; that’s a requirement in my book.
I look forward to trying it out.
rrook · · focus · HN ↗
- a workflow is a series of steps
- a step is one or more tasks that can be done in parallel
- a step is complete when all of its tasks are complete
- a task can be a unit of work, or a pointer to another workflow