I want to be an efficient developper. Mix-IT version
Download as PPTX, PDF21 likes10,528 views
This document outlines tips for becoming a more efficient developer. It recommends optimizing code and processes to promote developer happiness, which leads to better work. Developers should modularize and split their code into independent services that communicate through event queues. They should also focus on shipping working apps quickly by releasing early and often through continuous integration and deployment.
I want to be an efficient developper. Mix-IT version
- 1. I WANT TO BE A MORE EFFICIENT DEVELOPER TALK BY @WAXZCE – QUENTIN ADAM AT MIX IT 2014
- 2. MY DAY TO DAY WORK : CLEVER CLOUD, MAKE YOUR APP RUN ALL THE TIME
- 3. And learn a lot of things about your code, apps, and good/bad design… KEEP YOUR APPS ONLINE. MADE WITH NODE.JS, SCALA, JAVA, RUBY, PHP, PYTHON, GO…
- 4. DEVELOPERS ARE MORE AND MORE CREATIVE
- 5. DEVS LEADS A LOT OF BUSINESS
- 7. VALUE IS ON PEOPLE MARKET KNOWLEDGE, TEAM MANAGEMENT, PRODUCT OWNERSHIP…
- 10. HAPPY PEOPLE PRODUCE BETTER WORK
- 11. OPTIMIZE CODE AND PROCESS TO BE HAPPY OF WHAT YOU ARE DOING
- 12. OPEN SOURCES WORK PROCESSES ARE BETTER
- 13. PEOPLE WRITING CODE BECAUSE THEY JUST WANT TO DO IT THINK ABOUT
- 14. BECAUSE THEY CAN SOLVE PROBLEM OF THE WORLD
- 15. BUILD A FRAMEWORK TO PRODUCE CODE EASILY AND SHOW IT EASILY
- 18. FOCUS ON YOUR OWN ADDED VALUE
- 19. DEPLOYMENT HAS TO BE EASY !
- 20. BE FOCUS WHEN YOU CODE
- 23. OR NOT ;-)
- 24. ALL THE TEAM HAVE TO BE READY TO DEPLOY
- 25. YOU HAVE TO DEPLOY YOUR APP SEVERAL TIMES A DAY
- 26. SPLIT YOUR APP
- 27. SPLIT THE CODE : MODULES
- 28. SMALLEST CODE BASE POSSIBLE FOR EACH PROGRAM
- 29. EACH MODULE IS VIEWED AS A SERVICE BY OTHERS HTTP OR AMQP COMUNICATION OR AS A CLIENT
- 30. USE EVENT BROKER TO MODULARIZE YOUR APP • AMQP • Celery • 0MQ • Redis • JMS • Some case : hadoop, akka… • … CRON is not an event queue
- 31. FOCUS ON THE BEST TOOL TO SOLVE YOUR PROBLEM
- 32. DON’T BE THAT GUY
- 33. DO NOT USE A TECHNOLOGY BECAUSE YOU <3 IT OR BECAUSE IT’S HYPE : USE IT BECAUSE IT FITS YOUR NEEDS BALANCE YOUR LEARNING CURVE WITH THE TIME SAVED
- 34. DO NOT CREATE MONSTERS
- 35. LEAR NEW THINGS & INNOVATE
- 36. {P, DB, S} aaS USE OPS FREE SOLUTION TO LEARN AND START
- 37. USE ONLINE DATABASE / BE READY TO TEST IN JUST A FEW MINUTES NO NEED TO TRASH YOUR COMPUTER
- 38. MAKE ALL DEPLOYMENTS ASYNC MODULE BY MODULE
- 39. Statelessness everywhere AVOID HOST SPECIFIC THINGS
- 40. DO NOT USE FILE SYSTEM TO STORE SOMETHING • It doesn’t scale • It’s hard to expose as a service • It’s a SPOF • There is ALWAYS a better option
- 41. SCALE YOUR TEAM MODULARIZE YOUR TEAM
- 42. SOA IS BACK
- 43. TIME WILL TRASH YOUR CODE
- 44. THE POWER OF REWRITE EVERYTHING
- 45. SMALL CODE BASE + MULTIPLE TECHNOLOGIES = LEGACY KILLER
- 46. REWRITE IS QUICK BECAUSE YOU KNOW ALL THE PROBLEMS BEFORE IT HAPPENS
- 47. HAPPY DEVELOPER WORKS BETTER : ARE YOU HAPPY WHEN YOU START YOUR IDE?
- 48. VERSION EVERYTHING ! Data & API
- 49. NOSQL JSON DATA NEED VERSION Get doc on DB Version check : is there an update to do ? Use it at last code version
- 50. USE HTTP AND ALL THE GOODNESS IT BRING ON YOUR APP
- 51. 200 OK BODY : { TYPE : ERROR, MESSAGE : I CAN’T FIND THE FILE }
- 52. REALLY ?
- 53. PUT SOME TOOLS IN YOUR CODE
- 55. LET PEOPLES FREE TO CHOOSE THEIR IDE
- 56. USE A CONFIGURATION MANAGER / LIBRARY
- 57. LEARN GIT “LIKE A BOSS”
- 58. I MEAN : USE GIT WITH CLI
- 61. YOU HAVE TO THINK IT’S YOUR FIRST DAY ON THE CODE BASE
- 63. A DOCUMENTATION SLIM AS POSSIBLE
- 64. WRITE EVERYTHING
- 65. DO YOU WORK LIKE THIS ?
- 66. EXAMPLE : HOW DOES CLEVER CLOUD WORK ?
- 67. SOME OF TECHNOLOGY WE USE C
- 68. ALL TOGETHER USING HTTP & AMQP
- 70. THE FAST DEVELOPER WAY • Statup weekends • Hackatons • Coding dojo • Lean startup machine
- 71. I’m @waxzce on twitter I’m the CEO of A PaaS provider, give it a try ;-) THX FOR LISTENING & QUESTIONS TIME