Google Tech Talks Oct 8, 2008 ABSTRACT Ever notice which we appear to outlay 80% of your time upon 20% of your tasks? Or which 80% of a decisions in a assembly appear to begin in 20% of a assembly time? Welcome to a universe of a 80:20 rule. When we design, set up as good as exam software, we have to establish where to begin as good as what we should do next. The 80:20 order helps yield an answer to these questions, whilst assisting to enlarge a capability as good as effectiveness. As good as being an flexible principle, it’s a usual thread in alternative disciplines, as good as there’s a special movement which relates to software defects. We’ll try a opposite ways testers as good as developers have been regulating a 80:20 rule. This order could be a tip part to assistance we set up software smarter! Speaker: Erik Petersen Erik Petersen has been concerned in law software development given a 1980s, right away focusing upon testing as good as quality. He has presented during some-more than twenty Australian as good as general conferences, winning multiform awards. He mixes attention knowledge with absolute ideas as good as a passion for quality, as good as has shabby a work day to day of hundreds of testers as good as developers opposite a world. Erik’s been heavily concerned in a Exploratory Testing village given before he even knew what it was called, proposing a thought of interconnected ET exclusively of Kaner as good as Bach in 2001. He is pulling brazen with investigate upon ET as good as alternative flexible methods. He has reviewed most flexible as good as testing books, as good as incidentally …
80:20 rules! – Building program smarter
You can follow all the replies to this entry through the comments feed
80% of this presentation could have been delivered in 20% of the time ^_^;
Nice Informative Video. Keep it up :)
Nice reworking of an old rule. Regards debugging, I like the test 4 times advice. i.e. review the requirements and remove 60% of the bugs. Repeat with the design, code and testing, removing about 60% of the bugs at each stage. This way you get less than 1% bugs remaining. Even very skilled people rarely remove more than 80% with any 1 stage of testing, but with the test 4 times approach most developers remove more than 99%.
Wow! Fourteen thousand views in seven months! I thought I would be lucky to get three thousand in a year. Hopefully people are using the ideas in this talk to really build software smarter!
Erik
did you ever see a security presentation ? defcon, blackhat, shmoocon, phreaknic ?
0Oooo0oO0ooOoo0,
Base down life like that: No one is perfect, so are everything else!
From my point of view, your comments (the types ) are completely irrelevant in this context.
Perhaps, you should read this quote :
“Compliments in public, make suggestions for improvement in private”
Perhaps too, you did not listen the presentation in HD ! The slides are pretty clear.
Sincerely,
Have a nice day!
The poster is requestubg this comment is being removed. It is based on a unique difference of opinion since an early version of this talk won best presentation at 2 international conferences!
To be very brief and blunt: you have excellent command of the topic, but your presentation’s quality will be improved by several orders of magnitude if you work on your delivery skills!
Boring & poorly delivered? If you pay close attention, some slides have quotes on them so they need to be read. I couldn’t see the monitor most of the time so it was impossible to read the slides!
I’m confused how a 3d color graduated slide master can be a 2D flat color Windows 3.1 master.
There was actually another speaker in that theater still speaking when I was meant to start, so I had 30 seconds prep time before the talk started so I don’t think it went too badly. Glad you stayed awake!
An emailed comment on this video:
I viewed your presentation today. It presents ideas that can make
many people more productive and hopefully happier in their work. I
have forwarded to several others who will hopefully view it. Thanks for sharing this
with us. I certainly found it timely.
The presenter obviously knows what he’s talking about, and his topic is very important to take to mind, but he has a lot to improve in terms of his delivery skills. A few things come to mind:
* That garish slide layout is over-designed and visually distracting – Windows 3.1 called, they want their colors back
* Why do you read back the slides? Either you know the slides are boring, or you consider yourself boring, or both
Still, after forcing myself awake I learned a few valuable lessons…
summary at 48:50 and 50:25