Getting better
•
3 recomendaciones•2,444 vistas
Getting better: lessons learned in software development, start-ups and life in general
Recomendados
Recomendados
Más contenido relacionado
Similar a Getting better
Similar a Getting better (20)
Más de Tom Janssens
Último
Último (20)
Getting better
- 1. Getting better Lessons learned in software development, start-ups and life in general
- 2. @ToJans
- 3. Getting better Practice, practice, practice Failure versus mistake Retrospectives
- 5. Jonathan "Fatal1ty" Wendel First pro FPS player
- 6. WHY ?
- 9. Thinking levels 0: I know nothing 1: 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 levels 0: I know nothing => learn the poker rules 1: What do I have? => Which starting hand might be profitable 2: What does my opponent have? => Which hand might be profitable assuming the range of my opponent and poker odds, postflop play 3: What does my opponent think I have? => Which hand might be profitable assuming the range of my opponent and the range my opponent assumes I have, odds and postflop play
- 11. Leveling up 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 => Learn new thing => Practice, practice, practice => Intuition => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- 12. Poker professionals play roughly 100K hands/month (5K/day or 1K/hour or 17/minute) Practice, practice, practice
- 13. Level up as a developer http://xkcd.com/1075/
- 14. Leveling up 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 => Learn new thing => Practice, practice, practice => Intuition => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- 15. GitHub
- 16. Groups
- 17. Share
- 18. Meet up
- 19. Getting better Practice, practice, practice Failure versus mistake Retrospectives
- 22. Problem A leaking faucet causes a wet floor
- 23. Fixing Problems
- 25. Problem Fixed ?
- 27. We can Fix that!
- 29. Failure!!!!!!!!
- 30. If you're not failing every now and again, it's a sign you're not doing anything very innovative. Woody Allen
- 31. Let's try Again!
- 33. "Let's use the cloud!"
- 36. Why Why Why Why Why RootCause Analysis Avoid fixing the wrong thing!!!
- 37. Failure = good Mistakes = bad http://einiverse.eingang.org/2012/08/08/persist-or-die/
- 39. Mistake
- 40. In today's knowledge economy, it is not the tech stack that will give a competitive advantage. Anyone can google, download and install a tool.
- 41. Competitive advantage from software development should come from exploring the core domain, not from infrastructure. Small baby steps providing real business value is the way to go!
- 42. 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
- 43. Things that might help: Continuous integration & deployment * TDD * BDD * CQ(R)S * Functional programming * Event sourcing * Feature branching * ... Learn, unlearn and evolve !
- 44. Learning is the first step Everything looks like a nail when you have a hammer
- 45. A simple form does not require umphteen client side validations Understand the cost and risk of adding complexity
- 46. Software architecture should be driven by the features you require, not the other way around Optimize for productivity
- 47. Do not invest when the added business value is not worth it... This is my product catalog editor
- 48. Getting better Practice, practice, practice Failure versus mistake Retrospectives
- 49. I am a great believer that any tool that enhances communication has profound effects in terms of how people can learn from each other, and how they can achieve the kind of freedoms that they are interested in. Bill Gates
- 50. Why blog? "Rubber duck" effect
- 51. Why blog? Chuck Norris. Visibility.
- 52. Why blog? Meeting other peers.
- 53. How to blog? Blog about anything I prefer "brain dumps" Try finding a new approach Avoid negativity
- 54. Getting better Practice, practice, practice Failure versus mistake Retrospectives