5.0 out of 5 stars I wish I'd been taught the lessons in this book years ago.

A.C. · 27 March 2016

(function() { P.when('cr-A', 'ready').execute(function(A) { if(typeof A.toggleExpanderAriaLabel === 'function') { A.toggleExpanderAriaLabel('review_text_read_more', 'Read more of this review', 'Read less of this review'); } }); })(); .review-text-read-more-expander:focus-visible { outline: 2px solid #2162a1; outline-offset: 2px; border-radius: 5px; } While reading this book, I could relate to a lot of Robert C Martin's stories about unrealistic deadlines, poor requirements, inaccurate estimates and intense pressure to perform miracles. This book spends a lot of time examining the way that non-technical people perceive (and attempt to control) software development, and how all of these have a direct effect on the people who write the software, and ultimately quality of the software they produce, as well as the inevitable tension which emerges when things go wrong.I've personally experienced all of those things, and they aren't fun; the resulting software does not make me feel good either. I've had to deal with the tension and the office politics, deal with the poor quality rushed code merely weeks after asserting "We will do this properly", fix the buggy/broken software, explain missed deadlines, listen to disappointed customers.A part of me had been resigned to the fact that non-technical people just don't understand software, and that they are the cause of these problems. Explaining development to these people sometimes has felt like bailing out the titanic with a thimble, and it's tempting to believe that we have no way whatsoever to keep their wild expectations, their false assumptions and their mis-understandings in-check, or even that there's anything we as programmers can do to stop all that from derailing the efforts we put in to our software. Since reading this book, I've started to re-think my stance, and realised that there may be effective ways to handle these situations; maybe for their benefit but primarily for my own.I've made many of the same mistakes described in this book, and many of them without even realising that the mistake was even mine in the first place. Robert Martin provides advice and guidelines which arm us as developers to cope with these situations, and ways in which we can actually take control over other peoples' expectations and keep a lot of the mis-guided assumptions and - things which I assumed were out of my control, which may have been more about the way I perceived situations, or the way in which I handled communication with people I work with. I wish somebody had made me read this book years ago.Being able to write great code is necessary for advancing your career, but your career will go further, and it will be more enjoyable and satisfying if you don't always feel like you're losing control of the people issues. Furthermore, companies are likely to be enthusiastic about hiring programmers who know how to say the word "NO" when they're asked to do the impossible, and who know how to push for clear requirements, as well as knowing how to deal with all the other people issues.If you are a programmer, if you work with people (either technical or non-technical), and if you want to be a better programmer, then you will find plenty of good (yet surprisingly simple and common-sense) advice; this is a book about lessons learned from many years' of experience, and it's certainly easier to learn them from a book than by finding yourself in the middle of a failing project.

5.0 out of 5 stars A definite complement to Journeyman to Master in the track of the aspiring Software Craftsman

G.A. · 30 October 2012

My first book in the track of professionalism was "The Pragmatic Programmer: From Journeyman to Master", I was recommended the book from an seasoned colleague who I regarded highly. I got the book, and devoured it in a couple o f days. The thing I remember while reading it - was that so much in it made so much sense! It all felt natural, every part of it struck home.This book - is no different. Equally funny as thoughtful; the style is anecdotal but challenging. Given the few chances you get to receive such wisdom and depth from a true master, this is a must for anyone aspiring to become a true craftsman. I learnt a lot from this book - not only that you must not forget how others perceive you as a professional, but also that a true professional knows when to say no. This is one of the subjects I would say the book has a leaning emphasis on; how a professional ought to behave and act in hard times.No chapter is boring as it is opened with a good story from the life of Robert C. Martin himself, as well as disclosing his past weaknesses for everyone to see - and rightfully so. We must never forget that the journey starts with a step, and lasts until the end of our life.If you want a book filled to the brim with Wisdom and Laughs. This is the one.

4.0 out of 5 stars Part of "must have, must read" collection

A.F. · 11 July 2015

A very good book that every and I mean EVERY software developer (and not only because the book is more about professionalism than coding) must read. If you are just getting started in the field and have a lot going on, put everything else on pause, read the book then go on. If it did not change anything in your attitude towards work then good for you (you are already behaving like a professional or are to ignorant to care for the job you are doing. In case of the latter you should be slapped until you wake up to reality, nobody keeps a careless person around regardless of their skill, attitude is above skill. You need both, but attitude can compensate for skill while skill will not compensate for attitude).If you have thoughts about how a software developer should behave, what are the responsibilities of an organization towards their developer employees and the responsibilities of an employee towards his/hers employer and the work he/she is doing in a field so dynamic then read this book. It will shed some light on the path, confirm (or infirm) assumptions about how developers should do their job.Do not think this book will tell you how to write better code, it will but it is besides its focus (you have Clean Code for that). This book is all about attitude. It is about how we do what we do as developers and I do not mean how we write code, I mean how we communicate with our team, how we tell the management that the forced deadline cannot be met. Why and how we should do estimates. Last but not least understanding how a reply to a request is understood (e.g.: "I'll try to get it done by Monday" means that you will do your best to get the task done by that deadline, in other words it is mostly interpreted as "I'll get it done by Monday even if it costs me a few extra work hours and the weekend" otherwise it will be considered as you did not try hard enough). The management will try to pull every squeeze everything they can out of their developers (they probably will not go as far as blackmailing them but you can expect some sort of manipulation attempts) by asking to meet unreasonable deadlines (not always, but it happens often enough) and it is the job of the developer to tell the management that the respective deadline cannot be meet, developers must know how much work then can do and offer proper estimates (even though sometimes they are off, but they are estimates after all).I'm not giving this book 5 stars because it is somewhat repetitive and I would of liked more detail. Collaborating with QA, managers, fellow developers. How does Agile blend into all this. I would of liked more detail on forming teams (gelled teams are best, cool. How do we get there? If a team does not have a project to work on then why should that team exist? How is a gelled team forged? It needs to go though soft and hard times to properly form itself).

5.0 out of 5 stars Required reading for all software engineers

L. · 25 March 2024

It's mandatory reading. If your career transitioned like mine or you are entering your first job, it has all the info you need to think, act, and work like a professional software developer. It will put you way in front of your peers if they haven't read it.

-

D.N. · 3 February 2021

(function() { P.when('cr-A', 'ready').execute(function(A) { if(typeof A.toggleExpanderAriaLabel === 'function') { A.toggleExpanderAriaLabel('review_text_read_more', 'Read more of this review', 'Read less of this review'); } }); })(); .review-text-read-more-expander:focus-visible { outline: 2px solid #2162a1; outline-offset: 2px; border-radius: 5px; } -

I think every programmer should read this book very early in their career.

C.Z. · 29 April 2018

Another great book from Uncle Bob. This time it is not about the program but the programmer. I think every programmer should read this book very early in their career. What Bob writes about professionalism is spot on.

A must read for any serious professional

E. · 7 June 2023

I'm about halfway through and already its one of the most meaningful books in my career. It tackles a lot of the non-code issues in programming, such as being consistent on deliverables and communicating effectively.No matter how good of a coder you are, following the advice in this book will make you a better professional and more employable. Absolutely worth every penny.

Excellent book!!

C.M.G. · 18 June 2021

This book is perfect for those who want to see and learn tips to improve as a professional, an excellent book for my taste.

Un ottimo libro

C.A. · 7 June 2018

Non troverete una riga di codice in questo libro, ma molte indicazioni su come un professionista si formi, pianifichi, reagisca alle emergenze e in generale si comporti. Per la serie "allora non ero pazzo io".