Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Becoming a more productive Rails Developer

1,381 views

Published on

A presentation by John McCaffrey of RailsPerformance.com on how to manage technical information, ask technical questions, expand Ruby and Rails knowledge, and work on interesting side projects for open source, non-profits or as a freelancer

Published in: Technology, Education
  • Be the first to comment

Becoming a more productive Rails Developer

  1. 1. Becoming a More Productive Rails Developer A Collection of semi-useful suggestions John McCaffrey @J_McCaffrey RailsPerformance.com
  2. 2. Intro
  3. 3. Intro• Independent Rails Developer
  4. 4. Intro• Independent Rails Developer• CodeAcademy Mentor
  5. 5. Intro• Independent Rails Developer• CodeAcademy Mentor• Enthusiast
  6. 6. Topics• DWTDSYADB aka Taking good notes• Learning opportunities after• Getting help• Taking your skills to the next level• Q&A
  7. 7. DWTDSYADB Don’t waste time doing *stuff you’vealready done before
  8. 8. Take Notes like your life depends on it• Take lots o’ notes• Searchable• Reachable• Tools: Editor, Evernote, GoogleDocs
  9. 9. Code = Executable notes!• Save and organize all your projects• Create tests to document what you know• Follow interesting projects on github
  10. 10. Links & Sites• Write em down• Delicious• Google history
  11. 11. Use other people’s notes• Gem install cheat• cheat heroku• cheat jquery
  12. 12. Local Docs• gem server• gem install yard • yard gems && yard doc • yard server• sdoc• jQuery, prototype• Rails version
  13. 13. Summary
  14. 14. Summary• Do what you can to capture what you know right now
  15. 15. Summary• Do what you can to capture what you know right now• When you come across something useful, write it down
  16. 16. Summary• Do what you can to capture what you know right now• When you come across something useful, write it down• Make a note to your past/future self
  17. 17. Keep learning
  18. 18. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!
  19. 19. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com
  20. 20. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com• RubyKoans.com
  21. 21. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com• RubyKoans.com• Javascript: ejohn.org/apps/learn
  22. 22. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com• RubyKoans.com• Javascript: ejohn.org/apps/learn• Railscasts.com, PeepCode.com
  23. 23. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com• RubyKoans.com• Javascript: ejohn.org/apps/learn• Railscasts.com, PeepCode.com• SpeakerRate.com, Confreaks.com
  24. 24. Getting Help
  25. 25. Getting Help• 20 minute rule
  26. 26. Getting Help• 20 minute rule• Campfire/IM/IRC
  27. 27. Getting Help• 20 minute rule• Campfire/IM/IRC• Local Docs
  28. 28. Getting Help• 20 minute rule• Campfire/IM/IRC• Local Docs• How to Google
  29. 29. Getting Help• 20 minute rule• Campfire/IM/IRC• Local Docs• How to Google• Stackoverflow.com (SO)
  30. 30. Google Master• exclude with -• “quoted search”• fuzzy search ~• site: specific search• define: antidisestablishmentarianism• range ‘128gb ssd $100..$230’• Time in New York
  31. 31. How to ask a tech question
  32. 32. How to ask a tech question• Do some background research (RTFM)
  33. 33. How to ask a tech question• Do some background research (RTFM)• Document what you’ve tried
  34. 34. How to ask a tech question• Do some background research (RTFM)• Document what you’ve tried• Find the right place to ask
  35. 35. How to ask a tech question• Do some background research (RTFM)• Document what you’ve tried• Find the right place to ask• Post your question w/summary
  36. 36. How to ask a tech question• Do some background research (RTFM)• Document what you’ve tried• Find the right place to ask• Post your question w/summary• Link to full details (gist)
  37. 37. How to ask a tech question• Do some background research (RTFM)• Document what you’ve tried• Find the right place to ask• Post your question w/summary• Link to full details (gist)• Be willing to back up a few steps
  38. 38. How to ask a tech question• Do some background research (RTFM)• Document what you’ve tried• Find the right place to ask• Post your question w/summary• Link to full details (gist)• Be willing to back up a few steps• Post the resolution
  39. 39. Honing your Skills
  40. 40. Honing your Skills• Scratch your own itch, use Ruby at work!
  41. 41. Honing your Skills• Scratch your own itch, use Ruby at work!• Keep building apps
  42. 42. Honing your Skills• Scratch your own itch, use Ruby at work!• Keep building apps• Help the next batch of CA students
  43. 43. Honing your Skills• Scratch your own itch, use Ruby at work!• Keep building apps• Help the next batch of CA students• Help out on StackOverflow
  44. 44. Build your profile• Github.com• Stackoverflow.com• WorkingWithRails.com• LinkedIn.com• Blog• Build and deploy apps to heroku, etc• Contribute to open source
  45. 45. Freelance projects• Elance.com• oDesk.com• rentacoder.com• donanza.com• cloudspokes.com
  46. 46. Build something• Collaborate with others, join a team• Participate in startup weekend• Look for volunteer opportunities • taprootfoundation.org, grassroots.org • overnightWebsiteChallenge.com
  47. 47. Get inspired• TechStars.org, TechStars TV• Killerstartups.com• StartupsOpenSourced.com
  48. 48. Summary
  49. 49. Summary• Master your info
  50. 50. Summary• Master your info• Keep learning
  51. 51. Summary• Master your info• Keep learning• Learn how to find the right info
  52. 52. Summary• Master your info• Keep learning• Learn how to find the right info• Keep building apps
  53. 53. Summary• Master your info• Keep learning• Learn how to find the right info• Keep building apps• Collaborate with others to increase velocity
  54. 54. Questions?• John McCaffrey• RailsPerformance.com• @ J_McCaffrey

×