I’m now back to my daily work at SensioLabs after some days spent at Cologne, mostly for the Symfony Day 2011. It was truly great to be there. I had the chance to put faces on twitter nicknames and to talk in front of the crowd. I was a bit nervous and wasn’t as relaxed as I would liked to be. I will try to work on my english pronunciation for the next times.

Kids. Backuping your data is great. But assure you that your backups also contain your database. I’ve lost all the posts of this blogs and much more. Nothing to say that I was really pissed off.

I wanted to recreate this blog from scratch but got distract by other things. After a few months of procrastinating and slapping myself for not having a place to write, I found a great theme based on twitter bootstrap for wordpress and decided to give it a go. I’m pretty happy with that.

What is sfException?

As the sfException phpDoc says:

sfException is the base class for all symfony related exceptions and provides an additional method for printing up a detailed view of an exception.

If you look at the code of sfException you’ll see that sfException has a bunch of tool to wrap an exception inside an sfException. That’s why when an exception of any kind is thrown in symfony, you see a nice html output.

Fed up by using Eclipse (So slow) and Netbeans (always crashing), some folks at Sensio Labs told me to start using Vim. At first, I said: “Just the name makes me want to puke, but why not.”. A few weeks later, guess which tool I used to edit my code? Yes, Vim. No, I didn’t even puke!

VIM does not stand for “VIM Is Magic” but it could. It’s lightweight and usable everywhere. Whether you’re editing code, writing a blogpost in markdown or configuring an apache vhost over an ssh connection, it’s a wonderful tool to do the job.

• Step 1: Drink a few beers.
• Step 2: Drink some more.
• Step 3: Record your session.

Easy, isn’t it?