Re: [extremeprogramming] What has changed for you over the past 20 years?

Yep. TDD is a holly grail. Just having a policy not to check in any code without 100% unit test coverage does wonders to quality.


> On Dec 4, 2019, at 1:23 PM, Daniel Nuñez Carhuayo <[email protected]> wrote:
> 
> Hi everybody,
> 
> A 5 years ago in my work we was practice TDD on a application with a group of 4 engineers, 2 of them choosed working in one day without writing tests for new features and, effectively they made more features that day but, at next day some features begun to show problems, fix one do damage other features, results: writing test as crazy man's at 3am, next day after wroted tests all are fine again.
> 
> I don't say that others Technics not work or are wrong, I say it's important to consider the human skills, people's that can do that and Risk if they can't do, I believe in each engineer but to err is human IMHO
> 
> See you,
> 
> Daniel Núñez
> 
> El mar., 29 de octubre de 2019 9:38 a. m., J. B. Rainsberger <[email protected] <mailto:[email protected]>> escribió:
> On Tue, Oct 29, 2019 at 3:16 PM Ken Auer <[email protected] <mailto:[email protected]>> wrote:
> Thanks, JB,
> 
> I was surprised.  Let's see what happens.  The timing is interesting as I was just recently prompted to dig out some old articles/papers I've written and have some reflective time to publish updates... what is timeless since the early 2000s and what has evolved (at least for me).
> 
> This leads to a wider discussion regarding what has changed for you as an XP enthusiast and practitioner over the years. I'd like to keep the question wide open, so don't hold back.
> 
> I recently experimented with evolutionary design without tests and I found it enjoyable and illuminating.
> 
> I worked with a group of 3 people. They wanted to practise microsteps and to see a design evolve. For 3 hours, I drove while they typed. They practised the microsteps inside their IDE (elementary refactorings, keystrokes) and we went through 2 features of one of my teaching examples, "test"-driven (meaning that we wrote and ran the tests in our heads). It worked surprisingly well! They got to see some simple design evolve (albeit with no pressure from tests) and that made them happy. They could more clearly _see_ the power of evolutionary design, related to being able to defer commitment and change directions as needs change. We also just went more quickly than we would have had we written the tests.
> 
> Of course, I told them that if we got into trouble, then we'd start writing tests. Fortunately, we didn't get into trouble in just 3 hours. :)
> 
> So it turns out that after a decade or two of practise, one can live without the tests a surprising amount---at least in some contexts.
> -- 
> J. B. (Joe) Rainsberger :: https://tdd.training <https://tdd.training/> :: http://www.jbrains.ca <http://www.jbrains.ca/> :: http://www.thecodewhisperer.com <http://www.thecodewhisperer.com/>
> 
> 
> 
> 


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

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