Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

EvanFlow – A TDD driven feedback loop for Claude Code

github.com

Post reply on HN
Print view View original

31–40 of 75 posts

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#33

Post by alex1sa »

dpark wrote: post #17

I’ve thought of going down the TDD model for LLMs as a way of providing constraints on their behavior. I would think that “vertical slice” TDD would encourage the LLM to start tailoring the tests to the implementation rather than establishing the invariants up front, though. I was considering “horizontal” TDD to force the agent to implement constraints before coding to them.

[dead]

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#34

Post by EvanKnowles »

wenc wrote: post #9
shruubi wrote: post #8

Two questions 1) Do you not feel self-conscious or weird about calling this "EvanFlow"? Seems like a lot of people these days are naming their AI tools/skills/whatever after themselves which seems self-absorbed. Either that or they hope that if their thing takes off like OpenClaw did then they'll grab the fame that comes along with it. 2) Why does your TDD flow miss the refactor step of TDD?

I feel like 1 is a self correcting problem. If this goes nowhere it will soon be forgotten. I can think of one example that did go somewhere: Linux.

Feels like a bonus to me.

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#36

Post by dmitry_dv »

The refactor step is the silent casualty in AI-assisted TDD. Once the test is green, Claude optimizes for moving to the next test, not for cleaning up the impl that just passed. An "iterate-until-clean" pass at the end is a different thing: you're refactoring cold code, not refactoring with a freshly-written test as the safety net.

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#37

Post by globular-toast »

wenc wrote: post #9
shruubi wrote: post #8

Two questions 1) Do you not feel self-conscious or weird about calling this "EvanFlow"? Seems like a lot of people these days are naming their AI tools/skills/whatever after themselves which seems self-absorbed. Either that or they hope that if their thing takes off like OpenClaw did then they'll grab the fame that comes along with it. 2) Why does your TDD flow miss the refactor step of TDD?

I feel like 1 is a self correcting problem. If this goes nowhere it will soon be forgotten. I can think of one example that did go somewhere: Linux.

Linus did not name it Linux himself: https://en.wikipedia.org/wiki/Linux#Naming

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#38

Post by deaux »

girvo wrote: post #18
evanklem2004 wrote: post #2

Built this as an opinionated Claude Code development flow based on evidence based practices and what has been working for me while developing professional code. EvanFlow is a single TDD-driven loop. Say "let's evanflow this" and it walks brainstorm → plan → execute → tdd → iterate → STOP. Real checkpoints at design and plan approval. Never auto-commits, never auto-stages, never proposes integration - every git op is…

Please don’t post AI generated comments :( Just write it yourself. I promise it’s worth it

He's even being cheeky by intentionally replacing the em-dash by a regular dash, haha

Re: EvanFlow – A TDD driven feedback loop for Claude Code

#39

Post by synergy20 »

Deeds67 wrote: post #20

To be honest, the official superpowers/brainstorming skill already does TDD so well, I don't see that much of a need for this. TDD is definitely the way to go with agentic development.

how?i saw superpowers/brainstorming but never saw tdd code produced
Post reply on HN