LeoStehlik

5 ms·

1.
by LeoStehlik 5mo ago
thank you so much mate!
2.
by LeoStehlik 5mo ago
Started working on WrenLore, a Knowledge Base / Knowledge Management system built for both humans and AI agents. Humans review, use the nice clean UI, AI work on writing the documentaion, keeping it up to date, summarize, syntetize, ha
3.
by LeoStehlik 5mo ago
Exactly. How much % coding represent in designing, building, shipping, deploying, integrating, maintaining and evolving software? My take is 20-30%. Still great to have the coding part solved, it now democratizes software / ideas to
4.
by LeoStehlik 5mo ago
same, but that follows. Why I wanted a proof first is so that I don’t waste time running tests on code that was far from finished yet. Especially early days this year, I’d get agent confirming to me “I did this” whilst later I uncovered it
5.
Show HN: Proof Loop – I make my coding agents prove they finished the task(github.com)
2 points by LeoStehlik 5mo ago|2 comments
6.
by LeoStehlik 6mo ago
Back in 2011 at Fujitsu, I ran one of the earliest Azure production subscriptions outside Microsoft. Windows Azure, mid-2011. I've watched this platform for 15 years from the outside. Part 1 barely scratches the surface. Read parts 2 t
7.
by LeoStehlik 6mo ago
Both, as it proved neither is enough on its own. The structural fix is the obsession about separating roles: the agent that builds is never the one that verifies. I run a reviewer agent (I call her Iris), and a tester (Rex) — they live in s
8.
by LeoStehlik 6mo ago
This is what I've been missing running multi-agent ops through OpenClaw. The opacity problem is the one I hit hard: when a coordinator spawns 3-4 agents in parallel (builder, reviewer, tester, each with their own tool calls), the only