Keeping Rails on the Tracks

Keeping Rails on the Tracks Mikel Lindsaar @raasdnil lindsaar.net

Working in Rails & Ruby for 5+ Years http://lindsaar.net/ http://stillalive.com/ http://rubyx.com/

On the Rails?

Experience

Working Code?

Sexy Code?

Maintainable Code?

A Product is Only a Product if it is Exchanged

Budget MattersBeautiful code is ugly if no one buys it

Trade-Offs are LifeDecide how much refactoring needed based on code use

You are not selling code You are selling a solution Running app are what counts

Deployment is a First Class Citizen

Server SetupUse Chef / Puppet / whatever Repeatable Conﬁguration

Use Bundler Removes Deployment Pain Be explicit with versionsOnly lock to git repos you own

Repeatable Deployment Get the staging server up Use common deployment methods

Make a db/seeds.rb ﬁle Make it easy for other Developers The “other developer” may be you!

Link in SecurityDon’t store passwords in the app Use some other data store

Using “app” Gem

Document ItUpdate that README ﬁle!

Fast Page == Happy Client

Page Load Times Count Combine Javascript and CSS CSS Sprites Asset Pipelining in Rails 3.1 Before combination: 40 asset requests After combination: 5 asset requests

Caching Optimisation Know and love Rails view caching: Fragment Cache Action Cache Page Cache Before fragment cache: 2480ms After fragment caching: 120ms

Big Session == Slow Site Session objects are a slippery slope to pain Store values, not objects 10k session record 5,000 new sessions per month 500mb session table in DB

Pick Your Fights Don’t make a persisted session “cart” for every visitor 500,000 rows in sessions tableRemoved sessions for non customers Appdex went from 10% => 98%

Opinions Matter

Use Pluralization

Use the idioms

Remove Useless Code

Being Smart can be Stupid

Explicit MethodsDon’t use before, after and around ﬁlters for object instantiation Filters are for state modiﬁcation

Keep Tests SimpleComputers are good at nesting Humans less so

Use Helpers Insteadbefore & after should only maintain the test environment Keep tests “wet”

Hard to read

Easy to Read

Simple is better than Complex What you leave out is almost more important than what you put inMeta Programming has its place, that place is probably not in your Rails App

Good Code is Easy to Read Good code might be non trivial to implement But should be trivial to understand. The more bad code you have, the closer you are to a rewrite

Reinvention is Over Rated

Reinventing Controllers

Use the right tool for the job

Cucumber is not Unit Testing

You too can refactor

Read Ruby DocsGo and read the standard Ruby documentation online

Databases have feelings too

You don’t needdatabase agnostic code Make use of your database features Out of 50 apps, one is migrating DB

Instantiation is Slow Report run in ruby: 45 minutes Equivalent SQL query: 15 seconds

Use the DB tools you haveMigrate legacy data with Active Record: 150 hours PostgreSQL COPY with generated CSV: 74 mins

Don’t Share the DB12 rails apps against one BIG database 12 places for migration ﬁlesRefactor to API calls and CAS for auth

Code hasresponsibilities

Beware the Train Wreck

Control ﬂow is code smell DEMO (control_ﬂow_demo.rb)85 line 10 if else statement method

How to stay on track?

Get an Inspection Many consultancies do this Ask for a sample rubyx Inspect Service rubyx.com/services/inspect

Maintainable Code

Questions? Mikel Lindsaar @raasdnil rubyx.comrubyx.com/services/inspect

http://speakerrate.com	41
http://www.slideshare.net	2
http://en.oreilly.com	1
http://author.uthm.edu.my	1

Keeping Rails on the Tracks

by RubyX on May 17, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 45

Statistics

Keeping Rails on the Tracks — Presentation Transcript