published 3 months ago
(02.08.2009 11:45)
According to SpeakerRate. 5 is the maximum rating.
rated > 4.5
(both videos aren’t online yet)
- Dead simple JavaScript Unit Tests in Rails with Blue Ridge and Screw.Unit, Dr. Nic Williams 4.52
- Agile Happiness, Paul Campell 4.52
rated > 4
rated > 3.5
- Rails i18n From the Trenches 3.99
- Plenary: JRuby & Rails 3.98
- Sphinx: Beyond the Basics 3.96
- Sneaking Ruby & Rails Into Big Companies 3.95
- Invoicing Gem – Sales & Payments In Your App 3.95
- CouchDB and Ruby 3.90
- From the Keyboard to the Community 3.90
- Distributed and Concurrent Programming using RabbitMQ and EventMachine 3.84
- Agile Deployment with Ruby 3.84
- Mobilize Your Rails Application 3.83
- Launching Ruby on Rails projects: A checklist 3.77
- Bringing the Web to Your Desktop with MacRuby 3.57
rated > 3
- Rails Is a Hammer 3.33
- Panel Q&A 3.29
- Working with Legacy Rails Apps – Technical Debt Hell and how to work your way out of it 3.28
- Git Basics 3.20
- Behaviour driven monitoring with cucumber-nagios (no ratings)
Posted in ruby | Tags conference, rails, ratings, talks, underground | no comments | no trackbacks
published 3 months ago
(26.07.2009 19:38)
Update: added links to conference-related stuff at the bottom of this post.
Some notes, roughly chronological, left in draft state.
- Rails developers usually don’t seperate data access layer and domain model.
- This can constrain how easily the domain model can be changed. If done, saving/loading and validating data is on the DAOs, and “the interesting stuff” (business logic) lives in the model objects.
- Q: how do you develop a domain model? A: may should be explained in Analysis Patterns
- SASS and lesscss are nice extensions to css. They require processing the CSS, however.
- at least three German-speaking universities now have courses where they use Rails (Bremen, Potsdam, Salzburg).
- Refactor vs. Rewrite. First, “find out the hard core of what the client actually needs”. Be brave and delete, change.
- clients of “rescue mission” projects didn’t get what they wanted from their last dev shop. The time and money reserved for the project are usually already spent, so they are in a hurry. => as a dev team, you need to show progress as early as possible.
- do the agile thing as well—prioritize by business need
- Don’t change code that you don’t like but which works well. Overcome your own prejudice and deal with the client’s money responsibly. Part of being professional, imho. Resist the Not invented here syndrome. Especially if the code is well tested. You can always refactor it when continue to work in that area.
- don’t dive into removing complexity as a first refactoring step. Look for easy targets first.
- Watch team morale on legacy code projects. Always pair.
- Read the Refactoring book before starting, and really apply the techniques step by step when doing non-trivial stuff. Always keep the application running while changing structure.
- When coding normal apps, refactor as you go, don’t see it as a separate activity, don’t speciallly reserve time for it.
- always manage your client’s expectations. Underpromise, overdeliver.
- JRuby has the by far best compatibility of the alternative Ruby implementations. It has an extensive test suite.
- It allows you to change between 1.8 and 1.9 with a command-line switch.
- ActiveRecord via JDBC is slow.
- JRuby is the only Ruby implementation with real native threads.
- Rack allows inserting code before and after the application handles a request. And allows plugging together different frameworks and components, and access session data from one in the other via Rack::Session. “Middleware” examples: Rack::Profiler, Rack::MailExceptions, Rack::Cache.
- Rails 3 release: “could roll it up and ship” any time. Rails development has always been like that. There’s never a “Todo” list of what will go into a release.
- They will do so when they feel they have done enough. But at least one thing Yehuda would like to do is get ActionMailer on the rewritten ActionController code.
- London’s monthly Rails usergroup meetings easily exceed 100 people.
- to introduce new technologies in places reluctant to change, first do ugly or boring stuff no one wants to do anyhow. With Ruby that could be: automate manual processes, write a test tool, small internal applications, quickly build prototypes, wire together systems. Realize that Ruby is perfect for glue code. Introduce the techniques (agile), not only the technologies.
- A couple of experienced people fear that the new JVM Scripting languages (Clojure, Scala, ...) may stop the stream from Java-resignees to Ruby.
- CouchFoo is intended to allow smooth ActiveRecord/RDBMS => CouchDB migration. This is a good first step to get on the couch. Then you can start wrapping your head around how to persist stuff with document-oriented databases, which I find the hardest part. “Performance tuning” of CouchDB is a whole new topic to be discovered.
- With couchDB, the cost of index updates is incurred at read, not at write as with RDBMS. Index updates at read can be suppressed with :update => false. Read CouchFoo::Base for performance info.
- #bulk_save for performance.
- a good use for document-oriented DBs is when the data structure changes often and future “schema” development is unpredictable.
- CouchFoo generates views for simple AR-style finders on the fly. Nice!
- Dr Nic once more proved to be the best Rails entertainer (_why is in his own league, of course, but wasn’t present to present).
- the i18n gem has great new features in 0.2.0 and edge: pluggable extensions, translation procs, advanced pluralization rules (implemented with procs), translation fallbacks, backend fallbacks, etc. Using it in current Rails currently requires a hack, however. See the Unicode CLDR Project for a massive amount of localization information.
- Globalize 1 happily overused metaprogramming, had to hack into Rails big-time, and as such is a PITA to migrate to the new Rails i18n. Any solutions?
- Kasabian kick Oasis’ ass on stage (according to London press).
- Rough trade in Brick Lane reminds you what’s cool about a real-world record store.
- LBI has 400 employees, a large terrace where you can work, and friendly people doing lots of barbecues.
- ExtJS is a useful rich client library with nice client-server data transportation, interface elements and data binding. It doesn’t have to look like Windows. It lacks a high-level architecture, though. It’s not free for commercial work (150 per developer), only for open source.
- Food in London is better than expected; even the traditional (Lamb stew, Apple Crumble & custard). Girls are cuter than expected, as well.
- London weather follows the same patterns as in Hamburg. Quick rains, lots of grey skies, sometimes sun. A bit warmer.
- Kevin Davy played the trumpet for Lamb, on tracks like Merge. Today he has fun playing around with electronic effects at his Jazz gigs.
- ””Now wash your hands””:http://www.flickr.com/photos/phil76/3759350196/in/set-72157621719325175/ was a design agency that built cool stuff in their time. Today only toilets in Indian restaurants remind of their glory.
- Hashrocket has guest pairs regulary. You can visit them at Jacksonville, Florida, stay at their guest house, and pair with them on the regular work.
- London is green, can be sunny and beautiful.
- a taxi from Russell square to Denmark Hill costs less than 20 pounds. Good if you’ve already spent the same amount on beer.
- the mapping of the British pound shapes and sizes to their value is only obvious to the British themselves. They lovingly call the coins shrapnel.
- Conaissence can be seen as underlying principle of many OOP design rules. And it’s a word that only Jim Weirich uses, so far.
- the Rails community is as great as ever.
- Smaller conferences are better.
For a more throrough summary of the talks, continue reading at rubypond: day 1, day 2.
Links:
Posted in ruby, travel, coding, photography, the rest | Tags london, rails, underground | no comments | no trackbacks
published about 1 year ago
(22.06.2008 16:23)
taken at the Rails Konferenz 2008 by patrick lenz.
Posted in ruby, coding, mac | Tags 2008, konferenz, mac, rails, ruby | no comments | no trackbacks
published over 3 years ago
(21.05.2006 10:49)
rails_conf << phillip
i’ll be in london for a good week in september, mainly to attend the first european conference held on ruby on rails.
i’m excited about meeting the people behind ruby/rails in person, and to experience the rails community! from what i’ve learnt by reading blogs, books, documentation, emailing, viewing videos and listening to podcasts, and visiting sites created in rails i believe they are the most “human” and broad-minded of all programming communities i know. so i believe it will be a pleasant and fun experience, too. beside the obvious – getting a much deeper insight into the tech side of things and learning about rails’ future.
another reason i’m going is to commit myself more to the technology. having been a php guy all my developer life, today my brain says “use rails, it’s superior”, but habit and some lazy parts of my brain sometimes still respond “hey why bother – you already know one very powerful web development environment really well, and have invested a lot in it”. i believe the experience of attending a rails conference will provide a breakthrough and convince all of me, and only a warm and fuzzy feeling will be left.
since i’ve been to london only once, i’ll stay there more than a week. the conference is on the 14th/15th, but i’ll be in town from the weekend before the conference to the weekend after it (9th-17th). i’m looking forward to being in london again, too. i’m really curious – the last time i went was in the early 90s.
Posted in ruby, travel, coding | Tags community, development, london, php, rails, ruby, thoughts, travel, web
