Ruby approaches in the projection of professional growth - Max Goncharov
0 likes148 views
The document discusses various responsibilities levels for Ruby and Rails developers and debates common issues such as appropriate uses of models, controllers, views, ORM vs SQL, and test specifications. It emphasizes that developers should focus on their own responsibilities and choose tools competently rather than engage in holy wars over methodologies, as different approaches may be better suited to different needs. The best developers are defined by their ability to take responsibility and make informed technical decisions rather than claim any single approach is wrong.
Ruby approaches in the projection of professional growth - Max Goncharov
- 1. Ruby approaches in projection of professional growth Max Honcharov
- 2. WHY ARE WE HERE?
- 3. AGENDA WHO AM I IN CONTEXT OF RESPONSIBILITY? WHAT ISSUES RUBY/RAILS HAS? HOW CAN WE SOLVE IT? HOW DIFFERENT PEOPLE WILL DO IT? WHERE IS EXIT HERE?
- 4. WHO AM I IN CONTEXT OF RESPONSIBILITY?
- 6. TRAINEE
- 7. JUNIOR
- 8. MIDDLE
- 9. SENIOR
- 10. LEAD
- 11. WHAT ISSUES RUBY/RAILS HAS?
- 12. ATTENTION! HOLYWAR IS TOO CLOSE
- 13. BUSINESS LOGIC MANIPULATIONS DOES RAILS PROVIDE SOMETHING?
- 15. BUSINESS LOGIC MANIPULATIONS IS MODEL FOR BUSINESS LOGIC?
- 16. BUSINESS LOGIC MANIPULATIONS IS MODEL FOR PERSISTENCE LOGIC?
- 17. POINTS OF VIEW MODEL IS FOR BUSINESS LOGIC ONLY MODEL IS FOR BUSINESS LOGIC AND PERSISTENCE MODEL IS FOR PERSISTENCE ONLY MODEL IS JUST ORM ADAPTER
- 18. BUSINESS LOGIC MANIPULATIONS IS CONTROLLER FOR BUSINESS LOGIC?
- 19. POINTS OF VIEW CONTROLLER IS FOR BUSINESS LOGIC CONTROLLER IS FOR ALL OUTSIDE THE MODEL CONTROLLER IS FOR AUTH***ON CONTROLLER IS JUST FOR REQUEST HANDLING AND ALL ABOUT IT
- 20. VIEWS MANIPULATION IS VIEWS FOR BUSINESS LOGIC?
- 21. VIEWS MANIPULATION IS VIEWS JUST FOR MARKUP AND STYLES?
- 22. POINTS OF VIEW VIEW IS FOR HTML ONLY VIEW IS FOR DATA OUTPUT VIEW IS FOR BUSINESS LOGIC VIEW IS FOR INTERACTION WITH USER
- 24. ATTENTION! NEW HOLYWAR IS CLOSER THAN PREVIOUS
- 25. ORM VS PLAIN SQL HOW OFTEN DO YOU USE PLAIN SQL IN AN APP?
- 26. ORM VS PLAIN SQL IS ACTIVERECORD PANACEA?
- 27. ORM VS PLAIN SQL HOW MANY DEVELOPERS NEED TO SUPPORT THE APP WITHOUT ORM?
- 28. POINTS OF VIEW SQL IS FOR GEEKS ORM IS FOR NOOBS BOTH OF THEM ARE TOOLS
- 29. SOLUTIONS DATAMAPPER AND ANOTHER PATTERNS DISCOVER DIFFERENT SOLUTIONS MAKE DECISION BASED ON YOUR CURRENT NEEDS
- 31. SPECS WHAT COVERAGE DO YOU HAVE?
- 32. SPECS HOW DETAILED ARE YOU SPECS?
- 33. SPECS IS MAIN GOAL OF SPECS TO BE PRETTY?
- 34. POINTS OF VIEW CONTEXT VS DESCRIBE SHOULDA MATCHERS SUBJECT IS IMMUTABLE
- 35. SOLUTIONS IT’S JUST A TOOL SPECS ARE NEED TO BE HELPFUL SPECS DON’T NEED TO BE PRETTY SPECS ARE NEED TO BE
- 36. SUMMARY CONCENTRATE ON TASKS IN YOUR AREA OF RESPONSIBILITIES THE ABILITY TO TAKE RESPONSIBILITY AND COMPETENTLY APPROACH THE CHOICE OF THE TOOL MAKES YOU THE BEST DEVELOPERS YOU CAN’T BE WRONG, YOU CAN USE NOT THE BEST TOOL