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

51–60 of 75 posts

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

#51

Post by cornyhorse »

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.

Debian is an even better example

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

#53

Post by [deleted] »

phyzix5761 wrote: post #43
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?

Let the guy have something. Free and open source developers work tirelessly for free for years supporting software that billion dollar companies use to make huge profits. We don't question when scientists name stuff after themselves so why question this? At least he gets some recognition for his work.

[deleted]

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

#54

Post by pydry »

dmitry_dv wrote: post #36

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.

When I first used agentic coding I was already doing strict TDD and I just tried using it for the refactor step.

It sucked so hard I thought the idea of agentic coding was just a joke. Ive tried it periodically and it literally never stopped sucking.

I figure if it cant do that part it isnt worth using it for any part.

Ever since then whenever people tell me it's gotten better I've tried it out and nope, still sucks.

I still get gaslit about how well it works by people who just discovered TDD though, and watch it power through CRUD boilerplate getting impressed, blissfully unaware that boilerplate spew is an antipattern.

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

#55

Post by mansilladev »

toyg wrote: post #28
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 initially thought it was a pun on Pearl Jam's classic "Even Flow", then I read your comment and noticed the username... Sad.

I was really hoping this was something I could find on CPAN from the author username perlJam.

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

#57

Post by Nizoss »

conception wrote: post #52

If you’re just looking for the TDD part - https://github.com/nizos/tdd-guard - is the only project I’ve come across that actually enforces it with hooks and blocks edits rather than relying on a prompt that gets context rotted away.

Creator of TDD Guard here, thanks for the mention!

TDD Guard was built when Claude Code was the only one to offer hooks. Plugins didn't exist and the models were weaker, so the validation context and instructions took more work to get right. This is why it ended up requiring test reporters for different languages.

I have started a new project that does the same TDD enforcement, also through hooks, but without reporters. It works with any test runner, and it is vendor-agnostic, it works with Claude Code, Codex, and GitHub Copilot. The validator also sees recent session history which helps it handle cases like refactoring better.

The TDD instructions are still pretty basic compared to TDD Guard's, which have been dogfooded for a year. One thing I noticed while testing across agents is that some follow TDD a lot better than others, Codex struggled the most with the basic instructions.

Feedback welcome:

https://github.com/nizos/conduct

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

#59

Post by evanklem2004 »

girvo wrote: post #42
deaux wrote: post #38

Earlier quoted context omitted.

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

It's quite well done really, but the cadence... No x. No y. No z. Just abc. Its like nails on a chalkboard...

sometimes you gotta hit em with the ol' linkedin one two hehe

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

#60

Post by evanklem2004 »

esperent wrote: post #23

> execute → tdd How are these separate steps? TDD is how you execute, not something you tack on afterwards.

yeah that is a little confusing, tdd is actually a substep of execution. it was listed separately in the diagram because not every task uses TDD (config, generated types, etc. skip it), so the skill is invoked conditionally during execution rather than always. but the arrow notation made it look sequential when it's actually nested. updated the README diagram to show that. thanks for the nudge.
Post reply on HN