SMART principle

Written by | 4 minutes read | Tags learning | Comments

This post is about the SMART principle that helps you to start and keep rolling projects. I outlined how I use SMART for my eBook project.

I recently read the book Pragmatic Programmer, in which Dave Thomas explained the SMART principle. SMART is an acronym and each character of the principle has the following meaning:

Putting theory into practice

Late in 2011, I started a new and personally ambitious project: Writing an eBook about the great web framework Padrino. In a first step, I created a rough road map, about what I wanted to write and which topics should be covered. After writing the intro section and pushing the resources to GitHub I did something very crazy and mentioned @padrinorb in one of my tweets and this was it – the authors of the framework motivated me with with writing the book. They retweeted every small progress I made with the project and through that I got further pull requests and even a bunch of interested followers who are watching the project.

Let’s see how I can formulate the Book project with SMART:

I set up the frame of SMART goals and developed a rough plan - that’s all you need to let come your dreams true.

The SMART principle was first mentioned in 1981 as an issue of Management Review by George T. Doran.

Cost for SMART

To be honest, writing of my Padrino eBook project consumes a lot of my free time so I in the near future I will publish only a few new entries on this blog. I have many ideas and topics I want to cover, but first I will finish this book to deepen my writing experience. I’m glad to hear your opinion (or contribution) to the book.


SMART is great if you want to start in small steps to begin with something completely new, learn much about it, and report (for example, I’m using the twitter Hashtag #dailywriting, #padrinobook) about the progress you made.