Becoming a more Productive Rails Developer

2,754 views

Published on

Tips and tricks for how to accelerate your technical learning, take better notes, search in the right places, get help faster, solidify your understanding and hold on to what you've learned.

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,754
On SlideShare
0
From Embeds
0
Number of Embeds
1,340
Actions
Shares
0
Downloads
8
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • I’ll post the slides, with more links\n
  • You’ve heard of DRY\n
  • debugging\nsublime w/dropbox, from any machine/phone\ngoogle docs tech_notes and search for chmod\nEvernote\nWorkflowy\n
  • hard drives are cheap, projects don’t take up much space\nkeep them sep, and runnable\nreview code in gitx\n
  • use NLP tag for delicious\nerrors_\n go to cheat.heroku.com\n
  • \n
  • have you covered already?\nThis becomes more important when you are working on older projects\nI’m still looking for improvements in this area\n
  • Get good at taking notes\ntoday its Rails, tomorrow it will be Node.js, Backbone, IOS, etc\n
  • Get good at taking notes\ntoday its Rails, tomorrow it will be Node.js, Backbone, IOS, etc\n
  • Get good at taking notes\ntoday its Rails, tomorrow it will be Node.js, Backbone, IOS, etc\n
  • learnivore.com, teachmetocode.com\nCA students get deal on treehouse\npuzzlenode.com mendicantuniversity.com\n
  • learnivore.com, teachmetocode.com\nCA students get deal on treehouse\npuzzlenode.com mendicantuniversity.com\n
  • learnivore.com, teachmetocode.com\nCA students get deal on treehouse\npuzzlenode.com mendicantuniversity.com\n
  • learnivore.com, teachmetocode.com\nCA students get deal on treehouse\npuzzlenode.com mendicantuniversity.com\n
  • learnivore.com, teachmetocode.com\nCA students get deal on treehouse\npuzzlenode.com mendicantuniversity.com\n
  • learnivore.com, teachmetocode.com\nCA students get deal on treehouse\npuzzlenode.com mendicantuniversity.com\n
  • local docs, make sure you are looking at the right version\n
  • local docs, make sure you are looking at the right version\n
  • local docs, make sure you are looking at the right version\n
  • local docs, make sure you are looking at the right version\n
  • local docs, make sure you are looking at the right version\n
  • rails performance -train, bush -president, irb -board\n“Unrecoverable error, exit code 1”\n~issues\n128Mb to Kb\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • tech comm. is helpful, if you show you did your work\nmake a screencast\nread more at http://www.catb.org/~esr/faqs/smart-questions.html, \nhttp://www.gerv.net/hacking/how-to-ask-good-questions\n
  • Use Ruby at work!\nhttp://reference.jumpingmonkey.org/programming_languages/ruby/ruby-one-liners.html\n
  • Use Ruby at work!\nhttp://reference.jumpingmonkey.org/programming_languages/ruby/ruby-one-liners.html\n
  • Use Ruby at work!\nhttp://reference.jumpingmonkey.org/programming_languages/ruby/ruby-one-liners.html\n
  • Use Ruby at work!\nhttp://reference.jumpingmonkey.org/programming_languages/ruby/ruby-one-liners.html\n
  • List yourself on various job sites\ntalk to recruiters, find out what you are missing\n
  • You may not want to do this kind of work, but its useful to see what’s out there\nelance and odesk both have skills tests that you may find useful\nhttp://www.cloudspokes.com/challenges/1320\n
  • in chicago\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • 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• Continuing your Rails education• 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, Shareable• In your own words• 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• Use a tool like gitx
    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 (free weekend)
    20. 20. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com (free weekend)• RubyKoans.com, RubyMonk.com
    21. 21. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com (free weekend)• RubyKoans.com, RubyMonk.com• CodeCademy.com, Treehouse
    22. 22. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com (free weekend)• RubyKoans.com, RubyMonk.com• CodeCademy.com, Treehouse• Railscasts.com, PeepCode.com
    23. 23. Keep learning• FINISH HARTL TUTORIAL!!!!!!!!!!• CodeSchool.com (free weekend)• RubyKoans.com, RubyMonk.com• CodeCademy.com, Treehouse• 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, LinkedIn
    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

    ×