Rails Development That Doesn't Hurt

Rails@a_matsuda

✴Intro✴Rails Development✴Social Coding✴10 Pro Tips

self.inspect✴name: Akira Matsuda✴Twitter: @a_matsuda✴GitHub: amatsuda

A Rails programmer

Rails3 Recipe Book

OMG Timetable

Seattle.rb

RubyGems

“Writing Friendly Libraries” !!!

RubyKaigi Eric Hodel

✴ Intro✴Rails Development✴ Social Coding✴ 10 Pro Tips

Who does RailsDevelopment?

Rails development

Rails app development✴Ride on someone else’s “rails”

Rails app development I’m not gonna talk about that Railsdevelopment today

Rails app development

Developing “rails”✴“rails” for yourself✴“rails” for everyone

Developing “rails”✴Developing Rails plugins✴Developing Rails

Rails Development✴There are 3 types of Rails development✴One (that you do everyday) is not so fun✴Other two are fun

✴ Intro✴ Rails Development✴Social Coding✴ 10 Pro Tips

To develop “rails”Is to write a software not just for you

To write a software not just for you✴You need to Communicate✴That’s called “Social Coding”

Social CodingTo code is not just to speak to your computer, but tocommunicate with the people behind it

Social Coding

Get yourself involved in Social Coding The way to be a member of “The Community”

“The Community”

“The Community”is not in this Island

Each of these are “a community”✴ Ruby✴Asakusa.rb✴Seattle.rb✴...

“The Community” == “The World”

“The community”✴A community that people communicate in Ruby code

Let’s get out of hereCode Ruby, and be a member of “The community”

✴ Intro✴ Rails Development✴ Social Coding✴10 Pro Tips

Pro tip: to become a great Social Coder

Pro Tip #1Read Rails

Read `git log`every morning

Firstly✴% brew install hub✴% function git(){hub "$@"}✴% alias g=git

Firstly% g clone rails/rails

Every morning✴% g pull✴% g log (diﬀ)

This will tell you:✴What Rails 3.2 / 4.0 will be like✴Who’s actually creating Rails

Who’s actually creating Rails You see, so manypeople are committing

You will notice:Not only the core team but WE are creating Rails!

This will teach you:✴How to improve a product✴How to test a software✴How to write a good comment

Pro Tip #2Know the people

Reading git log will tell you✴Who’s remarkable

Remarkable people✴Stalk them online✴GitHub✴Twitter✴Blog

BTWYou can actually meet and talk to the 3 topmost remarkable people here today

@tenderlove

@wycats

@carllerche

Pro Tip #3Imitate good commits

A good commit✴Atomic✴With tests✴With a short commit comment telling • What • Why

Do it in *your* project✴in English, of course

Pro Tip #4English

Why are you scared?✴We had been learning English for 6 years✴We’re speaking Ruby everyday✴There are only 26 letters

✴Know these 26 letters✴Aware of the accents

Watch Railscasts

Pro Tip #5Live on the edge

edge is fun✴As you’re reading edge every day,✴Can’t wait to try these great new features until stable release

Just bundle it✴gem rails, :path => ~/src/rails

Yes, Bundler! <3 <3 <3

Pro Tip #6Contribute to the documentation

docrails% git clone lifo/docrails

docrailsA special Rails fork just for contributingdocumentations via GH

Rules✴Anyone can commit✴No code. Documentations only (guides / code comments)✴Commit to master branch directly

Let’s start with a minimal contribution

For example, “s/a/an/g”https://github.com/rails/rails/commit/90887cb

Anyone can do this ifhe/she knows how to use grep & sed

Pro Tip #7 Share yourmonkey patches

Push it to the upstream

That’s the absolute way to make the world happier.

✴local monkey patch => makes only your app better✴push your patch => makes the whole world better

Lonely Monkey Patches Rails

Social Monkeys Rails

Stop writing“how to workaround” on your rubbishy H tena blog

Push the patch instead

Please.

fork Rails, push, and send a pull request

Pro Tip #8Start from a gem

not only using edge Rails, use edge Gem

% gem up% bundle update for your health

% gem i [any gem] --preis also a good challenge

add a feature x a bugrequest for a feature

Gems I wrote patches for https://github.com/ amatsuda

Pro Tip #9Write a good README

Kaminari

Pro Tip #10Attend RailsConf

RailsConf✴Everyone you see in the `git log` is there✴Meet your Rails heroes✴For a Rails otaku, RailsConf would be far more exciting than RubyConf

One more thing

Pro Tip #11Write a book

You will nd tons of bugs, typos and incompatibilities

So you can x them that’s called

BDD Book DrivenDevelopment

B-D-D!No, I’m not talking about “VDD”...

SummaryCode Ruby socially andget yourself involved in “the community”

Conclusion“The community” awaits YOU!

Thank you!

http://d.hatena.ne.jp	107
http://www.hanrss.com	4
http://tweetedtimes.com	1
http://www.slideshare.net	1

Rails Development That Doesn't Hurt

by Akira Matsuda on Jul 26, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 113

Statistics

Rails Development That Doesn’t Hurt — Presentation Transcript