It took me less than one week to reread “The Pragmatic Programmer”.

I like beginning of the book the most, because it introduces pragmatic programmer and I like to think about myself as about such type of programmer.

So who are pragmatic programmers?

Pragmatic programmers are guys with willing to outperform, to stand out of the crowd, always trying to see bigger picture in order to produce higher quality code and to bring more value to customers. They learn a lot, they read technical blogs. You are also pragmatic, as very likely you share similar opinions about doing our job.

We don’t stop on achieved, we continue improving. We don’t just do our tasks, we make sure we do the right thing. We have a vision on our career and on what we want from our professional lives. We don’t complain, we solve problems. Cats don’t eat our source code, and we don’t live with broken window. We keep an eye on what is happening so no one can silently boil us as stupid frogs.

As per book pragmatic programmer is early adopter, inquisitive, critical thinker, realistic and jack of all trades.

This book is critically outdated when it comes to technologies or tools, because it was written IT centuries ago, in 1999. But it is astonishing how up to date it is about all other things.

I strongly recommend reading this book.

I find ideas expressed in book close to my understanding of software craftsmanship and I have my things to remember to become successful developer. In book you will find 70 tips, not just 8 as I have in my post!

I think this book is great because it inspires, and thus I would like to read it once again.