Slides for @a_matsuda's talk "たのしいRails" at RubyKaigi2011 http://rubykaigi.org/2011/ja/schedule/details/17M03

1. Rails
@a_matsuda

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

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

6. A Rails programmer

8. Rails3 Recipe Book

9. OMG Timetable

11. Seattle.rb

12. RubyGems

13. “Writing Friendly
Libraries” !!!

14. RubyKaigi Eric Hodel

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

17. Who does Rails
Development?

18. Rails development

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

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

21. Rails app development

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

23. Developing “rails”
✴Developing Rails plugins
✴Developing Rails

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

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

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

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

28. Social Coding
To code is not just to speak to
your computer, but to
communicate with the people
behind it

29. Social Coding

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

31. “The Community”

32. “The Community”
is not in this Island

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

34. “The Community”
==
“The World”

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

36. Let’s get out of here
Code Ruby, and be a
member of
“The community”

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

38. Pro tip: to become a
great Social Coder

39. Pro Tip #1
Read Rails

40. Read
`git log`
every morning

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

42. Firstly
% g clone rails/rails

43. Every morning
✴% g pull
✴% g log (diff)

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

45. Who’s actually creating
Rails
You see, so many
people are committing

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

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

48. Pro Tip #2
Know the people

49. Reading git log will tell you
✴Who’s remarkable

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

51. BTW
You can actually meet and talk
to the 3 topmost remarkable
people here today

52. @tenderlove

53. @wycats

54. @carllerche

55. Pro Tip #3
Imitate good commits

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

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

58. Pro Tip #4
English

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

60. ✴Know these 26 letters
✴Aware of the accents

61. Watch Railscasts

62. Pro Tip #5
Live on the edge

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

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

65. Yes, Bundler! <3 <3 <3

66. Pro Tip #6
Contribute to the
documentation

67. docrails
% git clone lifo/docrails

68. docrails
A special Rails fork just
for contributing
documentations via GH

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

70. Let’s start with a minimal
contribution

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

72. Anyone can do this if
he/she knows how to
use grep & sed

73. Pro Tip #7
Share your
monkey patches

74. Push it to the upstream

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

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

77. Lonely Monkey Patches
Rails

78. Social Monkeys
Rails

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

80. Push the patch instead

81. Please.

82. fork Rails, push, and
send a pull request

83. Pro Tip #8
Start from a gem

84. not only using edge
Rails,
use edge Gem

85. % gem up
% bundle update
for your health

86. % gem i [any gem] --pre
is also a good challenge

87. add a feature
x a bug
request for a feature

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

89. Pro Tip #9
Write a good README

90. Kaminari

91. Pro Tip #10
Attend RailsConf

92. 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

93. One more thing

94. Pro Tip #11
Write a book

95. You will nd tons of
bugs, typos and
incompatibilities

96. So you can x them
that’s called

97. BDD
Book
Driven
Development

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

99. Summary
Code Ruby socially and
get yourself involved in
“the community”

100. Conclusion
“The community”
awaits YOU!

101. Thank you!