Skip to content

Instantly share code, notes, and snippets.

@tjeden

tjeden/speaker.md

Forked from matiaskorhonen/speaker.md
Last active October 6, 2015 15:18
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tjeden/3013433 to your computer and use it in GitHub Desktop.
Save tjeden/3013433 to your computer and use it in GitHub Desktop.
Download ZIP
Frozen Rails Talk Proposal Template (http://2012.frozenrails.eu/)
Raw
speaker.md

Aleksander Dąbrowski

Contact details

Speaker bio

Aleksander Dąbrowski is a Ruby developer, Astarium CTO, and lecturer at Coder's Lab - Ruby on Rails school. He has worked in a variety of start-ups and in a marketing agency. He co-organises Warsaw's Ruby User Group. Aleks is also the author of rubysfera.pl, the leading Polish blog focused on Ruby and Rails. He likes to speak at Ruby developer events and is very passionate about sharing his knowledge with others. Along with using and contributing to open source software, Aleks particularly enjoys deleting ugly code, and in his spare is city guide of Warsaw.

Raw
talk.md

Rails Engines on examples

  • Desired talk duration: 30 minutes

Abstract

I spent last two years creating engines and using them as bricks to build complex applications. Now I'm ready to tell you how it worked out and what I did wrong (spoiler alert: I made a lot of mistakes). I won't teach you things, you can simply read in docs, but instead I will share my experience with Rails::Engine.

  • How can you benefit from engines?
  • Do I really have to commit the code, push it and bundle to see the changes?
  • What is the best way to extend mounted engine?
  • How to speed up development of them?
  • Why my assets and routes are not working?
  • How to organise the code, and manage versions?

I will answer all these questions, and many more (handy trick for developing migrations included).

You will learn how to simplify development and deployment of engines, how to test them, and most important how to avoid stupid bugs.

Notes

This is brand new talk about Rails Engines. I noticed this topic lacks of good coverage on blogs and conferences, so I would like to fill the gap. Frozen Rails looks like great place to present this topic. Although it's technical talk, fear not, it won't be boring. As a proof, you can watch my lightning talk from Railsberry: http://www.youtube.com/watch?v=Oj4vXMRenFo] (it's only 5 minutes long, and people find it funny.)

You can check feedback on my previous talks on twitter: https://twitter.com/#!/_tjeden/favorites Some samples are below:

Feedback

"entertaining and informative presentation at @RubyNation by @_tjeden! 'Goliath is a framework for losers' Jim Gay - @saturnflyer

"This was the best lightning talk ever #ihavetorepeatit @wrocloverb http://delete-your-code.heroku.com/#1 @_tjeden" Jan Kus - @koos

"hey @_tjeden, delete your presentation! no seriously! the greatest lightning talk: ""delete your code"" #Railsberry"" Edvinas Bartkus @edvinasbartkus

Previous talks:

On Lanyard you can see conferences I spoke at:

http://lanyrd.com/profile/_tjeden/past/speaking/

And here is a list of some vidoes from these conferences:

Sinatra autopsy given at Arrrrcamp 2012 and Rubyshift 2012

Building API: Sinatra, Node.js or Else given at Rubyshift 2011 and Rubynation 2012.

Write once, use twice given at Meet.js Summit 2012.

Delete your code lightning talk at Railsberry and Wroclove.rb .

I would love to be part of Frozen Rails. If you have any questions, don't hesitate to ask.

Best,

Aleks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment