DEV Community

Discussion on: The ONE chart every developer MUST understand

Collapse
 
pmneve profile image
Patrick M Neve • Edited

Have been fighting these battles for 35 years... Win some, lose most. While I currently specialize in test automation I've long championed various approaches to build quality into the project. Have seen all of the 36 mistakes and tried jawboning corrective action for each.

Am stilling hanging in there!

Superb article! Thanks!

Collapse
 
bosepchuk profile image
Blaine Osepchuk • Edited

Thanks, Patrick. Could I ask you to draw on your experience and share one or two tips with us to help devs in similar situations improve quality?

What's worked the best in your experience? Are there certain arguments or changes that have above average success rates in your experience?

Collapse
 
pmneve profile image
Patrick M Neve

Paying attention to user/customer needs and making sure they are understood helps a lot.
Not trying to do too much at one time (what I think agile really tries to address) also makes a difference.

Keeping iterations short and keeping the customers in the loop seem to be critical and cover a significant chunk of the infamous '35'.

And doing some 'design': thinking (and conversing) about what is to be delivered and about ways to do it before jumping into code. Can take ten minutes or a couple days, but is important.

If I keep going I'll rehash all 35. . .