Trying out the kindle app

After having exclusively used iBooks on my iPad Mini for reading books, I am now starting to realize that using the Kindle app instead may not be such a bad idea. Even though I like tech, I would normally have a hard time for instance buying a Kindle when I have a perfectly fine iPad, but I am starting to reconsider. Given the utter convenience of the Kindle and the total echo-system which is the Amazon store, convenience plays a major factor here, including the difference in weight and the ability to read outdoors.

Since I am starting to read The Martian now, I am considering using the Kindle app on my iPad to get acquainted to “The Amazon experience” of reading books. From what I can tell, there is a cool integration to Goodreads built into the app, but for some reason it only seems to work on books bought on Amazon and not books imported from other services.

I’m pretty sure that my reactions will find their way to the blog after finishing the book, and the experience will definitely impact whether or not I will be buying a Kindle in the near future as well.

Started reading The Martian

Having just finished Becoming Steve Jobs, I was looking through my to-read list on Goodreads, and decided on The Martian by Andy Weir as my next fiction. I have heard lots of good things about it, and given that I want to read it before the movie comes out later this year, it was an easy decision.

Also there is a revealing xkcd about The Martian:

The Martian

Do your own work first

Andrew Merle writes about how to make sure that your projects are progressing, instead of just focusing on the urgent but not so important tasks.

I stopped checking my email first thing in the morning several years ago after reading Tim Ferriss’ The 4-Hour Workweek. He said that one simple change would be a life-changer, and it has been for me.

The reason why it works is because it enables proactive work first, reactive work second.

Even when we have clear top priorities for the day, checking email first thing can easily derail those plans by compelling us to react and respond to other people’s “urgent” needs. And before you know it, the day has been totally eaten up, and our energy drained, before we can get started on our own projects.

This made me think about the daily review in GTD, and that instead of doing it first thing in the morning, do it by the end of the day instead. By then, you usually know what to focus on during the next day, and deciding there and then removes the friction of getting started early the next day.

via Why You Should Do Your Work First, Others’ Work Second

Garden State (2004)


Garden State (2004) is an indie movie about Andrew, a troubled young man returning to his hometown to attend his mothers funeral after being shut out by his family for more than a decade. His return coincides with his decision to stop taking his antidepressants after being dependent on them for the major part of his life. He happens to run into many of his childhood friends but also Sam, a like-minded and troubled woman he instantly connects with.

Continue reading

India 2015


I recently took a trip to India to visit some relatives and while I did bring my camera, I did not go all-out on taking photos during this trip. I did take some though and this gallery is a selection of them. Some photos are taken with my iPhone, others with the main Nikon camera.

Continue reading

Referencing external tasks in OmniFocus

Startup Stock Photos

Getting Things Done provides an excellent framework for managing all aspects of your life. What could easily happen in a professional work environment though, is that there is already an existing tool in place to keep track of tasks for the entire team, be it Trello, Pivotal Tracker or some other collaboration tool. While it is certainly possible to keep track of some tasks in separate systems, there will usually be an uncertainty in what goes where and if everything has been captured and taken care of appropriately. The worst thing that could happen, and usually does, is that you lose trust in the system and things fall through the cracks because you missed to check one system.

Continue reading

Uninterruptible programming

Being a developer, or doing anything creative, usually requires being “in the zone”. Being interrupted usually makes one drop right out of that sweet zone of productivity, and it usually takes a lot of time getting back.

uninterruptible programming is an interesting post dealing with how to handle this situation by constantly keeping the current state, and is exemplified by a filesystem journal.

The way it works is simple. When you want to do a disk operation, first, you write down in a special place (called a journal) what you are going to do, at a high level. “I’m going to delete this directory and all its files.” Then, you go through the steps of actually doing that. Finally, you record in your journal that’s what you did.

Now when power is interrupted during a disk operation you simply look at the journal and you can complete any operations that were in-flight at the time of the interruption. For example if the journal says “Delete X folder” and you see it still exists, now you delete it. It’s eventually consistent, even in the face of power interruptions, assuming that the intent hits the journal. And since journaling a high-level operation is a lot faster than actually doing it, chances are you’ll die doing the operation, not doing the journal.

Sounds simple enough, but instead of relying on a physical notebook, I would use Evernote, since I already use that for everything remotely considered reference material.