RUG::B

Logging in rails is a seamless experience. It just works! For rails developer, this is a no-brainer. It doesn't take that much time. However, if you experiment with Sinatra logging, you find the complete opposite.

• What kind of logging you need? Apache-like Access log?

• Do you need the convenient "logger.info/debug/error/..."?

• How about your ActiveRecord queries? They don't show automatically in the log (as in the case with Rails).

• But wait, errors don't show the log. Do you need to connect these as well?

Out of experience, Sinatra logging configuration is not easy. And, it doesn't come ready out of the box. In Minodes, I developed an open-source gem Sinatra Logger (https://github.com/minodes/sinatra-logger) to make Sinatra's configuration easier. I would also love to show the SemanticLogger from RocketJob (https://github.com/rocketjob/semantic_logger), on top of which we based our gem.

— Sinatra Logger gem is a Berlin-based project that was featured in Ruby Weekly.

Reviewing code has become a well-established best practice in the last decade of software development. Basically, programmers are reviewing code everyday now. But though they are such an important tool of our everyday work, I claim that they are often done very inefficiently and I will talk about how we can optimise.

The first part of the talk is about the important things on which we should concentrate during our reviews, the second part is about the human factor involved and how to give better feedback.

A shorter version of my RubyConfPH talk “Incredibly Fast Web Apps Without Touching Ruby” focussing on using CDNs.

Get your web app extremely fast by optimizing it outside of the app itself. If done right, it’s possible to reduce your loading times to less than 50 ms by using a CDN in front of your app, moving some kind of code into JavaScript, setting the right headers, and using localStorage. I’ll show you the easy and the lessons learned transforming a Rails app.