Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

RailsSummit Latin America 2008 by Mind Map: RailsSummit Latin America 2008
5.0 stars - 1 reviews range from 0 to 5

RailsSummit Latin America 2008

David Hansson (Q&A)

Rails 2.2 Multithreaded

Its mainly done, but time is needed to say it's fully ok

No big deal for MRI users due to the lack of native threads

JRuby users actually are the only ones that will really leverage this improvement., JRuby threads == java.lang.Thread

Rails evolution philosophy

Purely lean

No milestones defined

Rails major design changes tends do be fewer by now

Chad Fowler

Title: Evolution of a framework

the framework of a developer

Be Remarkable!

"Purple Cow" by Seth Godin, Mainly a business/marketing book, But devs can borrow alot of ideas for building their carrers

Chad's Example: Ipod, Joined a saturated market, Its price was way more expensive than average, Turned out to be a world fever!

My Example: Nintendo NES, Released in a time where the home console market was considered dead(~1983), Tons of low-quality games that saturated the marked causing a massive loss of public interest in games, It bringed the market back to life and turned to be a synonym of electronic entertainment

IT Shops market resembles the initial scenario of both examples, Programmers == Lemmings

People with jobs aren't remarkable

"You are a product"

Do you trespass the investments they put in you?

Learn2Learn and Learn to share knowdlege

Pragmatic Thinking and Learning by Andy Hunt

Rails is the bleeding edge tool for building Web Apps

To leverage it well you MUST learn Ruby decently!!!

Closures are responsible for 83% of the cool stuff you can do with Ruby

Fluency is productivity, "Experts makes things easy"

Changes

Keep calm even if the world is falling apart, "Doom"

Real experience comes from Changes

Brings Evolution, don't be afraid of it!

Criticism

Keep your critical sense high

Be critical but keep it to yourself, Do something better instead of talking

Lai & Bui (Phusion)

Scalability

Ahmdal's Law, Load distribution calculations considering sequential/parallel processing

Major Bottleneck is I/O

Application Scaling, Spreading app servers over different machines, Load balancers, Can be done via DNS as well, Caching, Page rendering cache (Fragment Cache), DB Access cache (Memcached)

Database Scaling, Master Slave Replication, Multi-Master Replication, Sharding, Absolutely no data normalization

New collaboration project : Yummius (URL anyone?)

yuumi.us

Jay Fields

General "rules-of-thumb" for writing good tests

1 object per test-case, problematic instantiation = bad smell

Exposed major Ruby test frameworks

Selenium, Good tool but Far from perfect, 1000 ways to do the same thing. Can turn to a mess., Speed issues

Test::Unit

RSpec

"Remove the pain from testing"

Do every effort for, Ex: In a project jay invested lots of time to remove DB access from tests

100% Coverage

Foul goal, Doesn't mean your app is properly tested

Focus in high quality tests at high business value parts instead

Smoke Testing

Chelimsky

Acceptance Test Driven Planning

Acceptance criteria defined at planning

helps to estimate

Stories

User Stories Applied by Mike Cohn

Different stories templates

"Feature Injection" concept by Chris Matts

RSpec

Cucumber

Hanrigou

Acceptance Test Paralellism with Selenium Grid

Default acceptance test scenario in RoR

Rspec + Selenium

Main issue: Selenium is slow

Selenium grid

Enforces parallel acceptance tests

Common steps

Fixtures are bad!

Initializing the domain object in the own test is better

Use ObjectMother pattern instead

Don't turn your back on acceptance tests

Obie

The Hashrocket Way

A living proof of successful agile+lean driven company

PivotalTracker