Your SlideShare is downloading. ×
0
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Getting better
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Getting better

1,538

Published on

Getting better: lessons learned in software development, start-ups and life in general

Getting better: lessons learned in software development, start-ups and life in general

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,538
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
6
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Getting betterLessons learned in software development,start-ups and life in general
  • 2. @ToJans
  • 3. Getting betterPractice, practice, practiceFailure versus mistakeRetrospectives
  • 4. PracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePracticePractice
  • 5. Jonathan "Fatal1ty" WendelFirst pro FPS player
  • 6. WHY ?
  • 7. Dreyfus modelhttp://www.leanleadershipacademy.com/lla-and-the-genesis-of-the-lean-expert/
  • 8. Example: poker
  • 9. Thinking levels0: I know nothing1: What do I have?2: What does my opponent have?3: What does my opponent think I have?4: What does my opponent think that I think they have?5: What does my opponent think that I think they think I have?=> To beat a player, play exactly 1 level above him/her
  • 10. Thinking levels0: I know nothing => learn the poker rules1: What do I have? => Which starting hand might be profitable2: What does my opponent have? => Which hand might beprofitable assuming the range of my opponent and poker odds,postflop play3: What does my opponent think I have? => Which hand might beprofitable assuming the range of my opponent and the range myopponent assumes I have, odds and postflop play
  • 11. Leveling upLearn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  • 12. Poker professionals play roughly100Khands/month(5K/day or 1K/hour or 17/minute)Practice, practice, practice
  • 13. Level upas a developerhttp://xkcd.com/1075/
  • 14. Leveling upLearn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>Learn new thing => Practice, practice, practice => Intuition =>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  • 15. GitHub
  • 16. Groups
  • 17. Share
  • 18. Meet up
  • 19. Getting betterPractice, practice, practiceFailure versus mistakeRetrospectives
  • 20. FailureversusMistakehttp://sethgodin.typepad.com/seths_blog/2011/12/the-difference-between-a-failure-and-a-mistake.htmlSeth Godin
  • 21. ProblemA leaking faucetcauses a wet floor
  • 22. FixingProblems
  • 23. ProblemFixed ?
  • 24. We canFix that!
  • 25. Failure!!!!!!!!
  • 26. If youre not failing every now and again, its asign youre not doing anything very innovative.Woody Allen
  • 27. Lets tryAgain!
  • 28. "Lets use the cloud!"
  • 29. This isA mistake
  • 30. Why Why Why Why WhyRootCause AnalysisAvoid fixing the wrong thing!!!
  • 31. Failure = goodMistakes = badhttp://einiverse.eingang.org/2012/08/08/persist-or-die/
  • 32. Failure inDevelopment
  • 33. Mistake
  • 34. In todays knowledge economy,it is not the tech stack that willgive a competitive advantage.Anyone can google, downloadand install a tool.
  • 35. Competitive advantage fromsoftware development shouldcome from exploring the coredomain, not from infrastructure.Small baby steps providing realbusiness value is the way to go!
  • 36. Focus on process,not on infrastructure.Reduce friction using automation,optimize for happiness ** http://tom.preston-werner.com/2010/10/18/optimize-for-happiness.html
  • 37. Things that might help:Continuous integration & deployment * TDD * BDD *CQ(R)S * Functional programming * Event sourcing *Feature branching * ...Learn, unlearn and evolve !
  • 38. Learning is the first stepEverything looks like a nailwhen you have a hammer
  • 39. A simple form doesnot require umphteenclient side validationsUnderstand the costand risk of addingcomplexity
  • 40. Softwarearchitecture shouldbe driven by thefeatures yourequire, not theother way aroundOptimize forproductivity
  • 41. Do not investwhen the addedbusiness value isnot worth it...This is myproduct catalogeditor
  • 42. Getting betterPractice, practice, practiceFailure versus mistakeRetrospectives
  • 43. I am a great believer that any tool thatenhances communication has profound effectsin terms of how people can learn from eachother, and how they can achieve the kind offreedoms that they are interested in.Bill Gates
  • 44. Why blog?"Rubber duck" effect
  • 45. Why blog?Chuck Norris. Visibility.
  • 46. Why blog?Meeting other peers.
  • 47. How to blog?Blog about anythingI prefer "brain dumps"Try finding a new approachAvoid negativity
  • 48. Getting betterPractice, practice, practiceFailure versus mistakeRetrospectives
  • 49. Questions?@ToJanshttp://www.corebvba.be

×