Traversing hyper driven developpement to do great technical choices and make your team happy - Worldline tech Forum keynote
Download as PPTX, PDF1 like185 views
Quentin Adam, CEO of Clever Cloud, emphasizes the importance of making informed technical choices while avoiding hype in software development. He discusses the emotional aspects of decision-making, the significance of ROI, and the collective nature of software. The document highlights that accepting weaknesses and focusing on personal integrity can lead to better leadership and innovation in technology.
Traversing hyper driven developpement to do great technical choices and make your team happy - Worldline tech Forum keynote
- 1. Traversing hype driven developpement to do great technical choices and make your team happy Quentin ADAM CEO @ Clever Cloud @waxzce on twitter
- 2. Who am I ? Quentin ADAM from the Clever Cloud @waxzce on twitter – github- soundcloud – instagram ….
- 3. https://www.youtube.com/c/MaiaMater “Interviews en toge” https://www.youtube.com/c/clevercloudplatform or search “Quentin ADAM”
- 5. 💡☁️
- 6. 💡☁️
- 7. Git push It’s free to try it out
- 8. Deploy & Application sustainability European Cloud & on premises
- 9. This morning: PaaS for AI GPU Clever Grid
- 10. Bright new day
- 11. Let’s go to fantasyland, before reality
- 12. No
- 13. Apply stuff in real life This conference goal
- 14. I do like my job, I hope you like it too
- 15. I care about
- 16. I’m proud
- 17. “I’m so sorry”
- 18. Legacy
- 19. ME
- 20. Understand the code hype paradox
- 21. Software is not a piece of art
- 22. Coders are subject to inspiration, not art vision
- 23. Software need a full Return On Investment FR https://www.youtube.com/watch?v=0ip1FoBsLB4 EN https://www.youtube.com/watch?v=OngWRJ8txps
- 24. Technical debt
- 26. What’s the question we need to answer?
- 28. How to make great technical choices?
- 29. Human is not rational And not data driven
- 30. How do we make decisions?
- 31. Choosing is an emotion
- 33. Speaking of big company…
- 35. From the role model to the vendors choices
- 36. ME
- 37. Shame is built around sadness, envy, distress... This feeling that you are behind
- 38. Do not compare your inside to others (marketing oriented) outside
- 39. Avoid tech choice drive by hello world
- 41. Accept to fail, on small projects
- 42. READ THE CODE
- 43. Free software is a collective goods, not a software costing no money
- 44. There is no rock star developer and blue collar ones: everyone can contribute
- 45. (This have to be on the budget)
- 46. Every software has dirty little secret(s)
- 48. Humans are not perfect
- 49. Sometimes we do not do good and/or well, Knowing it is self honesty and leads to becoming better Ignoring it and changing the quality standard for yourself is mediocrity
- 51. There is no Personal/Professional personality separation
- 53. Accept your weakness, never accept your mediocrity
- 54. Lowering you own standard and accepting mediocrity is crushing your leadership
- 56. No choice is the new choice
- 57. No choice is choosing mediocrity
- 58. Majority choices “this is what everyone is doing”
- 60. Planification VS Doing stuff
- 61. Be different to create value
- 62. Take responsibility peoples do not assume
- 64. And do stuff
- 65. Face to the 5 giants computer science problem
- 66. Naming things
- 67. Date/Time
- 69. Semantic = Business modeling
- 73. DATA
- 74. Programming is processing the data
- 75. Databases and event brokers
- 76. CAP theorem
- 77. Transactions
- 78. I/O
- 88. Cache invalidation TLDR; The CAP theorem, on the performance side
- 89. Tradeoffs
- 90. Embrace and document your tradeoffs
- 91. Scale your vision on real use case
- 92. Build your track record
- 93. Introduce new stuff once a time
- 94. Success cast a shadow on failures
- 97. I’m @waxzce on twitter Give CLEVER-CLOUD.COM a try Thx for listening
Editor's Notes
- #15: Love your job is important
- #34: Google, 85k employees Facebook IT is now marketing
- #41: D’abord sur la rummeur, et ensuite sur le learn
- #48: D’abord sur la rummeur, et ensuite sur le learn
- #80: 300000000/(60*24*365 = 570,7762557078 Surligner les exemples
- #81: = 1 minutes Surligner les exemples
- #82: = 15min Surligner les exemples
- #83: = 200min / 4h20 Surligner les exemples
- #84: = 208 jours Surligner les exemples
- #86: = 100 ans (pluton = 15 ans) Surligner les exemples
- #88: 300000000/(60*24*365 = 570,7762557078 an Surligner les exemples
- #90: Parler de l’exemple de lave postgres