22
Good Behaviors Rawin Viruchpintu for Developers

Good behaviors

Embed Size (px)

Citation preview

Page 1: Good behaviors

Good Behaviors

Rawin Viruchpintu

for Developers

Page 2: Good behaviors

Who I am ?

Rawin Viruchpintu Creative Technology Manager Palomar Systems / Spriiing

BlackBerry Developer Vervata

Research Assistant NECTEC

Page 3: Good behaviors

Outline • What's developer ?

• Developer Levels

• Skills

• Around Dev

• With … ?

• Conclusion

Page 4: Good behaviors

What's developer?

• A person who is involved in writing software.

It is mostly used as another term for programmer.

- ft.com -

Page 5: Good behaviors

Level of Devs

Junior developer Senior developer

Page 6: Good behaviors

Level of Devs

Senior developer

Experience Problem solving

Self learning

Communication skill

Performance

Teamwork Vision

Domain knowledge Time estimation

Junior developer

Responsibility

Page 7: Good behaviors

Skills

Wide Deep

Webservices HTML5

Java C++

database

Python Ruby

Web technology

noSQL

REST HTML5

jQuery

Page 8: Good behaviors

Around dev

$ sudo

Customers

Marketing

QA/Testers

Developers

Manager

Page 9: Good behaviors

Customers

Page 10: Good behaviors

With … [ Customers ]

• Listen to a user who complains your products.

• Any product was designed for customers, Not for developers

• Don't make them think !

– Intuitive

– Easy to learn/use/remember/ and forget!

– Fast response

• Open mind for negative feed back and smile

Page 11: Good behaviors

With … [ Marketing ]

Page 12: Good behaviors

With … [ Marketing ]

• Translate your binary logic to simple words

• Marketing can tell what is the product value

• Tell them about alternative solutions with

restrictions/conditions.

• Summarize overall concept into a (good) picture

• Deliver on time!

$

Page 13: Good behaviors

With … [ QA / testers ] ?

Page 14: Good behaviors

With … [ QA / testers ]

• Clear communication (check list will be useful)

• Defensive coding (check exception, logging)

• Good error messages

• Everything must be failed, know it early

• Failed early is cheap, Failed lately is expensive

• More code -> More tests • Mistakes are normal, correct it clever is a point

• Tester is a best friend, not your enemy !

Page 15: Good behaviors

sudo With … [ Developers ]

Programmer produces code

he believes is bug-free.

Page 16: Good behaviors

sudo With … [ Developers ]

• Find solutions first, Don't start with creating something

(Don't reinvent the wheel)

• Avoid labor-intensive techniques

• Learn good designs

• Every element needs to be (unit) tested

• Write code for reusing

• Comments

• Share your ideas, solutions, mistakes

Page 18: Good behaviors

With … [ Manager ]

• Analyze problem first

• Talk only what you know the real facts,

Not what you think you know

• Alarm first -> no Surprise!

• Always manage your time with top priority.

• Tell the facts, root cause and good solutions

Page 19: Good behaviors

$ sudo What else ?

Page 20: Good behaviors

With … [ Yourself ]

• Keep Learning

• Read, read, read and try to do

• Focus, Focus and Focus

• Summarize often Write a sentence to describe your work every day on a calendar

• Don't believe until you can prove by yourself

• TODO list with priority

Page 21: Good behaviors

Conclusion

Page 22: Good behaviors

THANK YOU

@windygallery