When I learn something new I often get into this frenzy of consumption of knowledge where I need to read every book, article, video on the topic I can get my hands on. Every new book is a promise of magnificent and wondrous abilities which are just waiting to be learnt just a couple of pages away. I imagine myself inbued of this new power to be more awesome at coding and I can’t help to feel giddy with excitement.

Of course the excitement fades eventually and all that’s left then is the determination to finish what I started. Finishing things. What a great skill to practice. If you haven’t got around setting up your new year’s resolution that one might be it.

Back to topic. As you may have noticed from my favorite new topic in this blog, for the past few months I’ve been investing most of my dad free time learning more about vim. Thus I’ve read a bunch of books and I’m in a great place to give you some recommendations.

Here are my favorite books on vim in the order in which I read them with some brief reviews and some advice on whether any of these books is the right one for you.

Don’t give up. Keep Iterating.

Every single time that I work on any creative endeavor the same process will unfold:

Hello You! Can’t believe another year has passed! But it has, and that means that it is time for the tradition of the yearly reflective summary, a wrap-up blog, retrospective of sorts, on what I’ve achieved the past year, my biggest fails, what I’ve learned and what I am planning to do in 2019.

This time the summary is somewhat special because it’s going to include 2017 as well as 2018. Yep. Last year, with my son Teo just a teeny tiny baby I didn’t have the energy, nor inclination, nor force of will to do a summary. In fact, I pretty much abandoned the blog (and life) from October 2017 onwards up until very recently.

Here we go!!

I looooove reading. I love reading fiction, non-fiction, long-form, short-form, anything! From a very tender age if you found me somewhere in the street, there was a high chance that I’d have a book with me. I remember vividly going to visit my sister at summer camp and vanishing from sight to go read 20000 leagues under the sea inside my dad’s car. Reading the same book at the beach. Going to the library to read Star Wars. Staying up until 8:00 a.m. trapped in the magnificent adventures of Jack Aubrey and Stephen Maturin. Traveling hours by train submerged in the world of The Dark Tower. Bringing a book about how to cultivate your character through the use of Stoic philosophy or mindful meditation while I went out to party…

I was reading dev.to a couple of weeks ago (I think) and there was an article that made me reflect about my interviewing experience at big tech companies (as an interviewee). So I thought… Why not share it and help other people that may be in the process of interviewing? Or who are considering applying themselves but perhaps don’t dare to? Or with someone who is merely curious and may think of it as a long term career goal?

So here it goes! In this article you’ll find out how to tackle the technical interviews at big tech companies. You’ll learn from my experience and my mistakes and we’ll distill everything into a methodology of sorts: A way to prepare your mind, and body, and mind (:D) before and during the interviews.

Get those interview books ready, pen and paper, and let's kick some ass!

So one day many, many seasons ago I got this call from Amazon…