How agile is rails
Upcoming SlideShare
Loading in...5
×
 

How agile is rails

on

  • 481 views

 

Statistics

Views

Total Views
481
Views on SlideShare
218
Embed Views
263

Actions

Likes
0
Downloads
1
Comments
0

4 Embeds 263

http://2012.agilept.org 256
http://2013.agilept.org 4
https://twitter.com 2
http://translate.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \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 How agile is rails Presentation Transcript

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