Loading video...

Video Failed to Load

Go Home

Morning bathrobe rant at a rainy cabin: test induced design damage.

26,842 views • 1 year ago •via X (Twitter)

11 Comments

Piotr Słupski's profile picture
Piotr Słupski1 year ago

Write a little test Write a little code

Coffee Fool's profile picture
Coffee Fool1 year ago

Got fresh coffee? We do.

Jose Canciani's profile picture
Jose Canciani1 year ago

Original @dhh article here: It's worth reading! His main point is that "Test-first units lead to an overly complex web of intermediary objects and indirection," with which I tend to agree. In my experience, TDD is ok when you have small, incremental changes in your code (which should be most of the time). But when you are trying to code something new where you don't know how the code will end up, writing tests in advance will -IMO- slow you down later when you inevitably want to rewrite it. I think the mantra of "First make it work, then make it right" also applies here, where "work" is "how you want it to be" and "right" is "tested". All in all, this is an endless debate. We've seen great products come out with and without the TDD practice. Fourtunatly in our coding world, there is more than one way to achieve our goals :) That's a good thing (most of the time hehe).

thoughtlesslabs's profile picture
thoughtlesslabs1 year ago

I love that you're leaning in on the crazy look Bob.

Leitz 💡's profile picture
Leitz 💡1 year ago

I like what Uncle Bob says here but always keep in mind one of the first principles of software development Every line of code is a future liability This applies to your tests too I love these videos

Tom Siwik's profile picture
Tom Siwik1 year ago

I was hoping for a rant about non-testers vs testers. Received more confirmation bias that I'm doing TDD the correct way.

Wm Dunton's profile picture
Wm Dunton1 year ago

As my IBMer father used to say “There’s only one thing worse than incompetence-MOTIVATED incompetence “

raddevus's profile picture
raddevus1 year ago

Fairly sure that these ARCHITECT battles are the result of two different kinds of Software Architects / Devs: 1 - Dev who writes mobile apps (or one-off web apps) 2 - Architect who writes Enterprise software I've written both & they require Two Types of Thinking Both are correct

Nohokthen's profile picture
Nohokthen1 year ago

He is not lying… this article exists (don’t get me wrong, I’m not judging too hard, I say stupid things all of the time as well 😂)

Jacques Thurling's profile picture
Jacques Thurling1 year ago

> can't do damage unless you're ignorant or stupid Well...guess I'm screwed then

Vish's profile picture
Vish1 year ago

it's almost like writing an essay for one class and thinking it's a completely different process for writing an essay for another

Related Videos