What I Learned at Open Hack Naperville

466 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
466
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

What I Learned at Open Hack Naperville

  1. 1. Kevin P. Davis, Ph. D4/23/13
  2. 2.  http://openhack.github.io/ Simple purpose: “Code together, on anything” A little food A little introduction Then code for a couple hours @OpenHackNAP, but there are many others:it’s a movement
  3. 3.  Downtown Naperville, 33 ½ Jefferson TwoCanoes Software HashRocket Very typical looking startup Macs everywhere Beanbag chairs everywhere I mean, really hipster. Might as well havebeen Austin. Or Portland. Or Boulder.◦ And very welcoming
  4. 4.  Couple .NET guys Apple guys Java guy Mainframe guy Bunch of Rails/Ruby guys So we didn’t have that much in common.Except the guy bit.
  5. 5.  Instead of co-hacking, the night turned into apresentation (by the will of the participantsand their curiosity), with lots of Q&A Starting withhttp://jonallured.com/2012/10/17/setting-up-a-new-rails-app.html, webuilt, tested, and deployed a Rails applicationto production (on the for reals interwebs)
  6. 6.  Functional programming paradigm If you’re getting started, use RVM◦ Package management◦ Keeps your versions clean and you smiling Gems are the spiritual precursors to NuGetPackages Rake is “ruby make” – think NAnt
  7. 7.  MVC Framework Wildly popular “Optimized for Programmer Happiness” “Convention over Configuration”
  8. 8.  ActiveRecord – Architectural Pattern◦ Relational database◦ Instance of active record tied to row in a database◦ Ruby has an ActiveRecord library Postgres – Open source database◦ Actively maintained and under development◦ RDBMS◦ Since 1986 (!)
  9. 9.  BDD framework Provides automated scenario testing◦ Given [and]◦ When◦ Then Compare to NBehave
  10. 10.  YAML Ain’t Markup Language (Views) Requires more research. I’m going to admitthis is a mystery to me. Views written in YAML rendered into HTML
  11. 11.  DVCS All the cool kids are doing it Job interview question : “What’s your GitHubhandle?” Can be local or use GitHub
  12. 12.  Application hosting First dyno is free (disk + cpu + network) Solid integration with git Easy to provision and publish
  13. 13.  Apparently the market is sick (the good kind) Enormous supply/demand gap for Rails When asked why, the answer was“Community” Salaries look competitive with .NET(glassdoor.com) Dev bootcamps and other Ruby outreach
  14. 14.  Beware. The Rails Community is a Cult.
  15. 15.  http://rubyonrails.org/ http://cukes.info/ http://www.yaml.org/ https://www.heroku.com/ - free dyno https://github.com/And for the truly demented (er… dedicated) http://devbootcamp.com/

×