From RailsConf 2014 - Everyone tells you that being a great programmer means reading lots of code. This talks gives you guidelines on starting your own Code Club (a Book Club, but for reading code!), and how to make the most as a developing programmer. Follow @readingcodegood for codebases to get you started. And tell us about great code that you've read!

1. READING CODE GOOD
@SARONYITBAREK + @readingcodegood
Saturday, April 26, 14

2. a year ago today ...
Saturday, April 26, 14

3. Saturday, April 26, 14

4. Saturday, April 26, 14

5. Saturday, April 26, 14

6. Saturday, April 26, 14

7. Saturday, April 26, 14

8. Saturday, April 26, 14

9. Saturday, April 26, 14

10. Saturday, April 26, 14

11. Saturday, April 26, 14

12. how can I become an expert?
Saturday, April 26, 14

13. READ CODE
Saturday, April 26, 14

14. Saturday, April 26, 14

15. Saturday, April 26, 14

16. Saturday, April 26, 14

17. one hour
Saturday, April 26, 14

18. one hourevery
Saturday, April 26, 14

19. SUNDAY
one hourevery
Saturday, April 26, 14

20. SUNDAY@ 11 AM
one hourevery
Saturday, April 26, 14

21. and we called it ...
Saturday, April 26, 14

22. code club
Saturday, April 26, 14

23. so what code should we read?
Saturday, April 26, 14

24. so what code should we read?
ANYTHING
Saturday, April 26, 14

25. the code base should be exemplary
Saturday, April 26, 14

26. • popular
• well documented
• well written
• well maintained
exemplary
=
Saturday, April 26, 14

27. Saturday, April 26, 14

28. Saturday, April 26, 14

29. we started with Sinatra’s ‘get’ method
Saturday, April 26, 14

30. Saturday, April 26, 14

31. Saturday, April 26, 14

32. RETRO
Saturday, April 26, 14

33. • how was the experience?
• what did we learn?
• how can we improve?
Saturday, April 26, 14

34. 1.
pick a manageable code base
=> 100 lines of code
Saturday, April 26, 14

35. • asking questions
• trying things
• researching topics
Saturday, April 26, 14

36. it wasn’t just about reading the code ...
Saturday, April 26, 14

37. 2.
the learning happens in
these digressions
Saturday, April 26, 14

38. 3.
this is a team effort
Saturday, April 26, 14

39. 4.
pick a tour guide
Saturday, April 26, 14

40. finding ‘exemplary’ code is hard
Saturday, April 26, 14

41. Saturday, April 26, 14

42. Saturday, April 26, 14

43. Saturday, April 26, 14

44. 5.
interact with the code
Saturday, April 26, 14

45. • what’s the intent?
• why was it written that way?
• how does it fit in?
Saturday, April 26, 14

46. 6.
it doesn’t have to be exemplary
Saturday, April 26, 14

47. everything was going swimmingly ...
Saturday, April 26, 14

48. Saturday, April 26, 14

49. 7.
finding knowledge gaps
Saturday, April 26, 14

50. 8.
you gotta keep at it
Saturday, April 26, 14

51. everything was going swimmingly again ...
Saturday, April 26, 14

52. ... and then we read the omniauth-meetup gem
Saturday, April 26, 14

53. 9.
find interesting code bases
Saturday, April 26, 14

54. the unexpected benefits ...
Saturday, April 26, 14

55. Saturday, April 26, 14

56. • organization of the code
Saturday, April 26, 14

57. • organization of the code
• see the collaboration
Saturday, April 26, 14

58. • organization of the code
• see the collaboration
• build your confidence
Saturday, April 26, 14

59. so you want to start your own Code Club ...
Saturday, April 26, 14

60. CODE CLUB GUIDELINES
Saturday, April 26, 14

61. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
Saturday, April 26, 14

62. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
Saturday, April 26, 14

63. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
Saturday, April 26, 14

64. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
4. pick a tour guide
Saturday, April 26, 14

65. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
4. pick a tour guide
5. interact with the code
Saturday, April 26, 14

66. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
4. pick a tour guide
5. interact with the code
6. it doesn’t have to be good
Saturday, April 26, 14

67. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
4. pick a tour guide
5. interact with the code
6. it doesn’t have to be good
7. finding knowledge gaps
Saturday, April 26, 14

68. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
4. pick a tour guide
5. interact with the code
6. it doesn’t have to be good
7. finding knowledge gaps
8. keep at it
Saturday, April 26, 14

69. CODE CLUB GUIDELINES
1. pick a manageable code base => 100 lines of code
2. the learning happens in the digressions
3. it’s a team effort
4. pick a tour guide
5. interact with the code
6. it doesn’t have to be good
7. finding knowledge gaps
8. keep at it
9. find interesting code bases
Saturday, April 26, 14

70. how is this getting me to ‘expert’?
Saturday, April 26, 14

71. Saturday, April 26, 14

72. Saturday, April 26, 14

73. Saturday, April 26, 14

74. --- for more info --> bloggytoons.com/code-club ---
1. dotenv
2. figaro
3. omniauth-meetup
4. country select
5. gravatar_image_tag
6. googlebooks
CODE BASES WE’VE READ
Saturday, April 26, 14

75. If you’re looking to start a Code Club
or you’ve found a great code base to read,
I’d love to hear about it.
@readingcodegood
Saturday, April 26, 14

76. bloggytoons.com/code-club
Saturday, April 26, 14