Rubyconf2012 recap

  • 236 views
Uploaded on

Recap of Rubyconf 2012 for OCRuby

Recap of Rubyconf 2012 for OCRuby

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
236
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. RECAP Forrest Chang OCRubyFriday, December 21, 2012
  • 2. Friday, December 21, 2012
  • 3. Friday, December 21, 2012
  • 4. Friday, December 21, 2012
  • 5. Friday, December 21, 2012
  • 6. Friday, December 21, 2012
  • 7. DIDN’T SEE ANY OF THATFriday, December 21, 2012
  • 8. Friday, December 21, 2012
  • 9. Friday, December 21, 2012
  • 10. Friday, December 21, 2012
  • 11. Friday, December 21, 2012
  • 12. Friday, December 21, 2012
  • 13. Friday, December 21, 2012
  • 14. Friday, December 21, 2012
  • 15. Friday, December 21, 2012
  • 16. Friday, December 21, 2012
  • 17. Friday, December 21, 2012
  • 18. Friday, December 21, 2012
  • 19. Friday, December 21, 2012
  • 20. Friday, December 21, 2012
  • 21. Friday, December 21, 2012
  • 22. Friday, December 21, 2012
  • 23. Friday, December 21, 2012
  • 24. Friday, December 21, 2012
  • 25. Friday, December 21, 2012
  • 26. Friday, December 21, 2012
  • 27. Friday, December 21, 2012
  • 28. Friday, December 21, 2012
  • 29. Friday, December 21, 2012
  • 30. Friday, December 21, 2012
  • 31. 20 TALKSFriday, December 21, 2012
  • 32. MOSTLY SUMMARIESFriday, December 21, 2012
  • 33. Friday, December 21, 2012
  • 34. Friday, December 21, 2012
  • 35. KEYNOTE • What I thought it was • Matz keynote • Why I picked it • You always see the Matz keynote • What it actually was • Another good Matz keynote • What I got out of it • Do things out of love. Go and change the worldFriday, December 21, 2012
  • 36. ABSTRACTING FEATURES INTO CUSTOM REVERSE PROXIES (OR: MAKING BETTER LEMONADE FROM CHAOS) • What I thought it was • How to break up your huge systems into smaller systems • Why I picked it • Always interested in service-izing systems. Better than the other choices • What it actually was • Story of how NREL broke up their systems for the better • What I got out of it • Some tips and technology, https://github.com/NREL/api-umbrellaFriday, December 21, 2012
  • 37. SERVICE ORIENTED ARCHITECTURE AT SQUARE • What I thought it was • How Square does SOA w/JRuby • Why I picked it • Interested in servicizing, expect Square to be pretty heavy duty • What it actually was • The Square SOA creation process • What I got out of it • Great example of process - thorough, secure and “Document Oriented” and polyglot • https://github.com/square/fdoc - document format and validation • https://github.com/square/cane - code quality in the build • https://github.com/square/jetpack - self contained Jruby app deployment • Growing Object Oriented S/W Guided By Tests Steve freeman, Nat PryceFriday, December 21, 2012
  • 38. RUBY MONITORING STATE OF THE UNION • What I thought it was • A survey of the current state-of-the-art projects available for runtime monitoring of production Ruby code • Why I picked it • Looked the most useful of the bunch. Could always use good ideas on better monitoring • What it actually was • A survey, with a suggestion on how to unify to a central interface/process, vs. stovepiped monitoring apps • What I got out of it • hope for the future of monitoringFriday, December 21, 2012
  • 39. BUILDING DATA DRIVEN PRODUCTS WITH RUBY • What I thought it was • Building Data driven products • Why I picked it • Building Data driven products. Mentioned big data. • What it actually was • Data driven products, definition and stages from a Data Scientist • What I got out of it • Steps, some tools. Aware of the non Ruby world wrt data driven productsFriday, December 21, 2012
  • 40. WHY JRUBY WORKS • What I thought it was • Nitty gritty on how JRuby works and works well. • Why I picked it • Not certain, I’m already pro JRuby • What it actually was • 1st of many “How awesome is JRuby” talks. Did show how it’s improved • What I got out of it • We should be doing more JRuby. It smokes even Ruby 2.0 in many areasFriday, December 21, 2012
  • 41. BUILDING MODULAR, SCALABLE WEB APPS? OF CORS! • What I thought it was • Cross Origin Resource Sharing(CORS) implications • Why I picked it • Best looking selection. Michael has written awesome gems. • What it actually was • Overview on CORS and some examples. • What I got out of it • Food for thoughtFriday, December 21, 2012
  • 42. Friday, December 21, 2012
  • 43. Y NOT -- ADVENTURES IN FUNCTIONAL PROGRAMMING • What I thought it was • Y-Combinator in Ruby keynote • Why I picked it • You always see Jim Weirich. Also interested in digestible y-combinator talk • What it actually was • Jim defines and builds the y-combinator from the ground up using stabby lambdas • What I got out of it • Understanding of the y-combinator. Understanding of the origins of some javascript functional idiomsFriday, December 21, 2012
  • 44. RUBY VS. THE WORLD • What I thought it was • A look at some other languages from a Ruby perspective • Why I picked it • See what the rest of the world is doing • What it actually was • A comparison of Go, Clojure and Scala for the Ruby Eye • What I got out of it • I should look at ScalaFriday, December 21, 2012
  • 45. REAL TIME SALAMI • What I thought it was • Aaron Patterson talk • Why I picked it • Aaron is always entertaining, and sometimes you learn something • What it actually was • Salami steps and RT streaming in Rails 4 • What I got out of it • Entertainment, DtraceFriday, December 21, 2012
  • 46. RAILS IS A FOLLOWER: WHAT WE CAN LEARN FROM DRUBYS METAPROGRAMMING MAGIC • What I thought it was • Explanation of metaprogramming magic behind Druby • Why I picked it • Looked more interesting than the others • What it actually was • history and ideas behind the implementation of Druby • What I got out of it • A reminder I should use it again for certain categoriesFriday, December 21, 2012
  • 47. INSIDE RUBYMOTION • What I thought it was • Rubymotion overview and how easy it is to write an IOS app • Why I picked it • Objective C? nuff said... • What it actually was • Overview of Rubymotion, and how awesome it is. How thin the layer is. • What I got out of it • Definitely should consider Rubymotion and Rubymine if building an IOS app. Rubymotion console is a beautiful thingFriday, December 21, 2012
  • 48. THE CELLULOID ECOSYSTEM • What I thought it was • Celluloid overview and ecosystem • Why I picked it • Concurrent programming is all ‘teh rage’. Celluloid seems to be the way to go in Ruby • What it actually was • Celluloid overview and ecosystem • What I got out of it • Consider Celluloid, but it only runs in JRuby/Rubinius for real threadsFriday, December 21, 2012
  • 49. LIGHTNING TALKS • What I thought it was • Lightning talks • Why I picked it • Lightning talks are awesome. Tons of stuff, no fluff • What it actually was • Lightning talks. 40ish people signed, only 18ish got to go. I was #35 • What I got out of it • wish they had gschool when I was young, @rubyhangout, twitter power tools, gitnesse, pursuit of happiness, machine creativityFriday, December 21, 2012
  • 50. Friday, December 21, 2012
  • 51. THE INSUFFICIENCY OF GOOD DESIGN • What I thought it was • Stuff for good design exists, but it’s not enough • Why I picked it • Like good design, want to know what else there to make a successful project • What it actually was • An awesome talk about how software mirrors the culture of it’s creators and how disfunctions culturally are represented in the code • What I got out of it • Fix your cultureFriday, December 21, 2012
  • 52. TESTING SHOULD BE FUN • What I thought it was • How to make testing fun again after you have huge long running test suites • Why I picked it • looking for those sort of tips to improve our test suites. Noel’s online writings are good • What it actually was • Assorted tips, but not super for, or super well put together • What I got out of it • Joy is key. A list of practicesFriday, December 21, 2012
  • 53. INTERFACE TESTING: CREATING A DIABLO 3 BOT USING JRUBY AND SIKULI UI • What I thought it was • How to solve hard Interface testing and making a Diablo 3 bot • Why I picked it • Hard interface testing • What it actually was • How awesome running Sikuli w/JRuby is, w/a great building a bot story line • What I got out of it • JRuby + Sikuli FTWFriday, December 21, 2012
  • 54. BOUNDARIES • What I thought it was • Study of test and class boundaries in light of mocks. • Why I picked it • testing boundaries always an issue, wanted to see Gary Bernhardt • What it actually was • Presentation of a thoughtful approach. Good ideas there, unfortunately, not to be easily plugged into Rails • What I got out of it • Ideas, I should check out the current state of DCI in rubyFriday, December 21, 2012
  • 55. THINKING IN OBJECTS • What I thought it was • The right perspective of what is OO from a veteran smalltalker • Why I picked it • You can’t ever be too good at fundamentals • What it actually was • OO 101. I was expecting more • What I got out of it • a review of OOFriday, December 21, 2012
  • 56. AN INTIMATE CHAT WITH MATZ • What I thought it was • Evan Phoenix’s reboot of the Matz Q/A in a “Larry King” format • Why I picked it • You always see the Matz Q/A • What it actually was • A Matz Q/A with just Evan asking collated questions • What I got out of it • Matz prefers that the community decideFriday, December 21, 2012
  • 57. TALKS I HEARD WERE GOOD, BUT DIDN’T SEEFriday, December 21, 2012
  • 58. • XIKI - the Rubyfied next generation Shell Console • Refactoring from Good to GreatFriday, December 21, 2012
  • 59. Friday, December 21, 2012