loading...

Discussion on: Template Driven Development: Why it doesn't work

Collapse
devcamilla profile image
camilla

Very timely article. Thanks for the read.

"You let the patterns emerge to help you express the problem you're solving, you don't force them to appear."

I totally agree. Though, isn't Test Driven Development a way to solve this? Satisfy the requirements first then incrementally refactor the code, eventually producing a pattern that suits and satisfy the requirement.

Making small PRs sounds promising! Though this encourages the fail fast discipline, some may argue for the stability of the code base. I need to do more readings on this. Thank you for sharing. :)

Collapse
barryosull profile image
Barry O Sullivan Author

Hi Camilla, thanks for the comment, glad you enjoyed the article.

I completely agree with your statement, TDD is a fantastic way to let patterns emerge rather than forcing them. Your tests give you feedback on what's working and what isn't, this can guide you to a better design.

I'd definitely encourage you to look into small PRs. Over the last year I've been focussing on writing small PRs that also leaves the codebase in a stable state. It's challenging initially, but it teaches you to mark incremental, stable changes that are easy to review. I've also found it encourages the use of feature flags, but that's a discussion for another time. :)