What’s wrong with SOLID and Test Driven Development | Coding Over Cocktails Podcast

While SOLID is the known standard when it comes to software design and architecture, it may be hard to apply for some as it limits developers to specific techniques in going about it.
In this episode, Daniel Terhorst-North, originator of Behaviour-Driven Development (BDD)and Deliberate Discovery, presents his arguments on why SOLID isn't exactly the best bet when if comes to design principles, offering an alternative that can help against the misapplications of various agile practices.
Episode outline:
• Daniel Terhorst-North answers why he challenges the principles of SOLID and presents his arguments.
• How does CUPID improve on the principles of SOLID?
• Despite Test-driven Development being considered an "evolutionary approach to development," what are the problems associated with it?
• What is Behaviour-driven Development (BDD)?
• How has the development community responded to SOLID and BDD?
Read the full transcript: www.torocloud.com/podcast/wha...
Learn more about Toro Cloud and our products: www.torocloud.com

[@jacobstamm]

Great interview! Could you describe the distinction between C and U? To me, they seem like nearly identical synonyms for “small and focused enough”

[@paikesitics]

C-omposable
U-nix Philosophy
P-redictable
I-diomatic
D-omain Based

[@minjaekim184]

Well this channel seems deserve more subscribers

[@PaulSebastianM]

I have found another great mentor!

[@DavidRodenas]

Sadly, nowadays BDD has been converted into a technobabble for QA teams.

[@majucamex08]

And the developers who buy what the QA’s say…

[@lucasterable]

1. Bash on a popular discipline
2. Come up with an acronym
3. ???
4. Profit!

[@T0m1s]

A lot of crappy stuff was once popular, buddy. It's ok to bash crappy stuff. SOLID and TDD are some of the crappiest "disciplines". What you should be asking yourself is "how come I haven't bashed SOLID and TDD? How did SOLID and TDD become popular? Was there any scientific basis to these, or is it just someone's opinion?". Maybe start thinking with your own head instead of saying "oh they're popular, so they must be good".

[@banatibor83]

@@T0m1s you must have eaten something bad which messed up your brain. Maybe those are not the golden principles and TDD is not the ultimate method, but not following them is a straight way to hell.

[@T0m1s]

@@banatibor83 - prove it.

[@forevernoob97]

@@banatibor83 You forgot "for me". The fact that YOU cannot fathom development outside these "principles" does not mean it doesn't exist.

[@forevernoob97]

@@T0m1s I wish I could like this comment twice.

[@banatibor83]

Fascinating that somebody with so much experience misses the point so much.
Composable = Dependency inversion + easily testable code
Unix philosophy = that is Single responsibility p.
Predictable = well tested. If you do not think about an edge case when you are writing tests you can miss those cases just as easily during writing the code.
Idiomatic, ok, has nothing to do with SOLID or TDD. Means your colleagues can code in the given language, maybe clean code.
Domain based, DDD again has nothing to do with SOLID and TDD.

[@forevernoob97]

"Composable = Dependency inversion + easily testable code" .... what??? So I guess when the Gof said "prefer composition over inheritance", years before Bob Martin proposed the "Dependency inversion" principle, they must have been confused or something. To suggest composition is a function of Dependency Inversion is just absurd.