Re: [extremeprogramming] The principle behind How Test-Driven Development Works

Very much this. 

1) Test-first forces you to think of the code by how it is to be used rather than how it is to be implemented.
2) It guarantees that the code is actually unit testable, thus making it safe to change the implementation.

The key is that, in general, you’re not likely to understand how to solve a new problem or the consequences of change if you don’t work in small steps with feedback.

Russ


> On Nov 20, 2019, at 1:16 PM, Slava Imeshev via Groups.Io <[email protected]> wrote:
> 
> The way I personally see it, TDD works because the test becomes the first user of the code and source of early feedback. This is especially true when a developer is building an internal APIs implementing an externally facing use case. May be just one example but I seen it work again and again. My advice to engineers stuck in tactical writer block has been to start with writing a test. They end unblocking themselves or realizing that the idea wasn’t that good in the first place and taking a different design route.
> 
> Slava Imeshev
> 
>> On Nov 20, 2019, at 5:34 AM, Steve Gordon <[email protected] <mailto:[email protected]>> wrote:
>> 
>> Me, too.
>> 
>> However, TDD works because it addresses the uncertainties that people problems create, not because it addresses any technical programming issues.
>> 
>> On Wed, Nov 20, 2019 at 5:41 AM Dave Nicolette <[email protected] <mailto:[email protected]>> wrote:
>> I could agree with that formulation without reservation.
>> 
>> On 11/20/19, Ron Jeffries <[email protected] <mailto:[email protected]>> wrote:
>> > I wonder how we'd come down on "Software is primarily a people problem
>> > rather than a technical problem".
>> >
>> >> On Nov 20, 2019, at 2:08 AM, Dave Nicolette <[email protected] <mailto:[email protected]>>
>> >> wrote:
>> >>
>> >> you write, "Software development is a people problem, not a technical
>> >> problem," I hope you're exaggerating to make a point. If software
>> >> development were *not* in any sense a technical problem, and were
>> >> *only* a people problem, then you could put a bunch of naked people on
>> >> a desert island with no technology, and they could produce software.
>> >> Such is the power of the word, "not."
>> >
>> >
>> > Ron Jeffries
>> > ronjeffries.com <http://ronjeffries.com/> <http://ronjeffries.com/ <http://ronjeffries.com/>>
>> > You never know what is enough unless you know what is more than enough. --
>> > William Blake
>> >
>> >
>> > 
>> >
>> >
>> 
>> 
>> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160262): https://groups.io/g/extremeprogramming/message/160262
Mute This Topic: https://groups.io/mt/39414677/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-