omoiyari-driven development

38
Omoiyari-Driven Development Kuniaki IGARASHI 28 October 2007

Upload: kuniaki-igarashi

Post on 24-May-2015

4.662 views

Category:

Technology


0 download

DESCRIPTION

In Japan, there is an excellent word "omoiyari". Omoiyari means that trying to understand other people are thinking about, or being thoughtful, or being nice.

TRANSCRIPT

Page 1: Omoiyari-Driven Development

Omoiyari-DrivenDevelopment

Kuniaki IGARASHI28 October 2007

Page 2: Omoiyari-Driven Development

In Japan,there is an

excellent word

Page 3: Omoiyari-Driven Development

“Omoiyari”

Page 4: Omoiyari-Driven Development

Omoiyarimeans that...

Page 5: Omoiyari-Driven Development

trying to understandother people are thinking about

Page 6: Omoiyari-Driven Development

or beingthoughtful

Page 7: Omoiyari-Driven Development

orbeing nice!

Page 8: Omoiyari-Driven Development

What’s ODD ?

Omoiyari-Driven Development

Page 9: Omoiyari-Driven Development

Corepractice

Page 10: Omoiyari-Driven Development

When you can’tmake a decision,you should think

from other people’s points of view.

Page 11: Omoiyari-Driven Development

That’s all !

Page 12: Omoiyari-Driven Development

It’s simple,

Page 13: Omoiyari-Driven Development

easy tounderstand,

Page 14: Omoiyari-Driven Development

anduniversal.

Page 15: Omoiyari-Driven Development

Why should wedo ODD?

Page 16: Omoiyari-Driven Development

Because, bugs often come from

misunderstandings.

Page 17: Omoiyari-Driven Development

Misunderstandings between two people.

Page 18: Omoiyari-Driven Development

Misunderstandings between different

teams.

Page 19: Omoiyari-Driven Development

I’m certainODD would be a good solution to this problem.

Page 20: Omoiyari-Driven Development

Use Omoiyari for the benefit of

code readers,library users,product users.

Page 21: Omoiyari-Driven Development

Let’s try ODD!

Page 22: Omoiyari-Driven Development

Lesson 1.when

writing code

Page 23: Omoiyari-Driven Development

When we can’t make up our

mind,

Page 24: Omoiyari-Driven Development

we should ask

ourselves.

Page 25: Omoiyari-Driven Development

Can the programmer understandthis code?

Page 26: Omoiyari-Driven Development

Can the programmer easily use this library?

Page 27: Omoiyari-Driven Development

Is the user happy with this

product?

Page 28: Omoiyari-Driven Development

Lesson 2.Bear

programming

Page 29: Omoiyari-Driven Development

to remember thinking

from a someone's point of view,

Page 30: Omoiyari-Driven Development

program witha teddy bear.

Page 31: Omoiyari-Driven Development

like this.

Page 32: Omoiyari-Driven Development

It’s a traditional method.

Page 33: Omoiyari-Driven Development

“THE PRACTICE OFPROGRAMMING”by Brian W.Kernighanand Bob Pike1999 ISBN 0-201-61586-X

It’s described in this book.

Page 34: Omoiyari-Driven Development

“Effective technique is to explain your code to

someone else.This works

remarkably well.”

Page 35: Omoiyari-Driven Development

“One university computer center kept a teddy bear near the help desk. Students with

mysterious bugs were required to explain them to the bear before they could speak to a

human counselor.”

Page 36: Omoiyari-Driven Development

Kernighanstrongly

recommendsbear programming. :)

Page 37: Omoiyari-Driven Development

Let’stry ODD!

Page 38: Omoiyari-Driven Development

Thank you all for reading!Kuniaki IGARASHI

http://igarashikuniaki.net/tdiary/[email protected]

special thanks to GOGA, Julien and Sopu.