20
Learning Patterns for the Overworked Developer @Ben_Hall [email protected] Katacoda.com

Learning Patterns for the Overworked Developer

Embed Size (px)

Citation preview

Page 1: Learning Patterns for the Overworked Developer

Learning Patterns for the Overworked Developer

@[email protected]

Katacoda.com

Page 2: Learning Patterns for the Overworked Developer

@Ben_Hall / Blog.BenHall.me.uk

Tech Support > Tester > Developer > Founder

Software Development Studio

WH

O AM

I?

Page 3: Learning Patterns for the Overworked Developer
Page 4: Learning Patterns for the Overworked Developer
Page 5: Learning Patterns for the Overworked Developer
Page 6: Learning Patterns for the Overworked Developer
Page 7: Learning Patterns for the Overworked Developer
Page 8: Learning Patterns for the Overworked Developer
Page 9: Learning Patterns for the Overworked Developer
Page 10: Learning Patterns for the Overworked Developer
Page 11: Learning Patterns for the Overworked Developer
Page 12: Learning Patterns for the Overworked Developer

Goals are clear

Page 13: Learning Patterns for the Overworked Developer

Feedback is immediate

Page 14: Learning Patterns for the Overworked Developer

A balance between opportunity and capacity

Page 15: Learning Patterns for the Overworked Developer

Kolb

Page 16: Learning Patterns for the Overworked Developer
Page 17: Learning Patterns for the Overworked Developer

Keep track / a journal

Page 18: Learning Patterns for the Overworked Developer
Page 19: Learning Patterns for the Overworked Developer

Summary

• Clear goals• Reflection• Experimentation• Learn By Teaching

Page 20: Learning Patterns for the Overworked Developer

Thank you!

@[email protected]

www.Katacoda.com