How agile is rails

624 views
557 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
624
On SlideShare
0
From Embeds
0
Number of Embeds
299
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • How agile is rails

    1. 1. HOW AGILE IS RAILS? Face the necessary trouble.
    2. 2. JOSÉ MOTASenior Interaction Designer @ Iuz Technologies
    3. 3. I WANNA MAKE MONEY. You guys want it too.
    4. 4. BUT I CARE MORE ABOUT BEING HAPPY. Do you?
    5. 5. THE AGILE MANIFESTO It serves a holistic purpose: to acknowledge the future in human behavior.
    6. 6. HOW AGILE IS RAILS? How does it affect human behavior?
    7. 7. WORKING SOFTWARE
    8. 8. $ RAILS NEWAWESOME_APP
    9. 9. MVC & CONVENTIONS BUILT-IN. Start doing your app. Focus on the what, not the how.
    10. 10. $ RAKE TEST OR $ RSPECThe framework (how) is tested,start testing your app (what).
    11. 11. DEVELOPER’S PROFIT
    12. 12. DEVELOPER’S PROFIT Less development time.
    13. 13. DEVELOPER’S PROFIT Less development time. Less headaches.
    14. 14. DEVELOPER’S PROFIT Less development time. Less headaches.More time to document, contribute and learn.
    15. 15. BOSS’ PROFIT
    16. 16. BOSS’ PROFITMore confidence on the team.
    17. 17. BOSS’ PROFITMore confidence on the team. Better response to clients.
    18. 18. CUSTOMERCOLLABORATION
    19. 19. FRAMEWORK +STRONG CONVENTIONS = SPEED
    20. 20. > SPEED ⇳> PEER REVIEW RATIO
    21. 21. > PEER REVIEW RATIO ⇳> SENSE TRUST AND BELONGING
    22. 22. BUILD TRUST, CLIENTS STICK AROUND.
    23. 23. DEVELOPER’S PROFIT You get to keep your job.
    24. 24. BOSS’ PROFIT
    25. 25. BOSS’ PROFITYou get to keep your clients. And your job.
    26. 26. BOSS’ PROFIT You get to keep your clients. And your job.A new sense of management. Collaboration, rather.
    27. 27. BOSS’ PROFIT You get to keep your clients. And your job.A new sense of management. Collaboration, rather. Responsibility is better balanced.
    28. 28. RESPONSE TO CHANGE
    29. 29. TEST-DRIVENDEVELOPMENT Pick your change: Unitary Integration Acceptance
    30. 30. TDD GRANTS CONFIDENCE ON THE DESIGN.
    31. 31. TDD + RUBY = AWESOME SAUCE
    32. 32. SOURCE CONTROL Use it how it’s meant to be used.Rails has a .gitignore file and everything!
    33. 33. DATABASESIt supports data, not the app.
    34. 34. SQL?Migrations – keep your database controlled over time. Schema is always up to date.
    35. 35. USING COUCH OR MONGO? They’re agile by nature, move along.
    36. 36. DEVELOPER’S PROFIT
    37. 37. DEVELOPER’S PROFIT It’s freakin’ Ruby.
    38. 38. DEVELOPER’S PROFIT It’s freakin’ Ruby. Express yourself: type less, do more.
    39. 39. DEVELOPER’S PROFIT It’s freakin’ Ruby. Express yourself: type less, do more. Less debugs.
    40. 40. DEVELOPER’S PROFIT It’s freakin’ Ruby. Express yourself: type less, do more. Less debugs. Come home sooner.
    41. 41. BOSS’ PROFIT.
    42. 42. BOSS’ PROFIT.A better, more confident team.
    43. 43. BOSS’ PROFIT.A better, more confident team.More confident towards clients.
    44. 44. INDIVIDUALS AND INTERACTIONS
    45. 45. THE TOOL / PROCESS IS RAILS. Stop worrying about it.
    46. 46. ITERATIVE / INCREMENTAL DEVELOPMENT More confidence on the present.
    47. 47. WORK WITH YOUR CLIENTS, NOT FOR THEM.
    48. 48. ABOUT PEOPLE AND CHANGE...
    49. 49. ITS 2012,WERE INFORMATION JUNKIES! Of course we can change.
    50. 50. CLIENTS CHANGE THEIR MINDS. Deal with it.
    51. 51. YOU CAN’T AFFORD PREDICTION. Don’t think ahead (too much).
    52. 52. DEVELOPER’S PROFIT
    53. 53. DEVELOPER’S PROFIT No prediction, no overkill.
    54. 54. DEVELOPER’S PROFIT No prediction, no overkill.Time to invest on good design with good tests.
    55. 55. BOSS’ PROFIT Start projects right away.
    56. 56. LONG STORY SHORT?I looked at code for the first time when I was eleven.
    57. 57. LONG STORY SHORT?
    58. 58. YOU WILL FACE TROUBLE. Just avoid the unnecessary.
    59. 59. Github: josemota Twitter: @josemotanet BE HAPPY. Thank you. ❦ Come talk to me!

    ×