Tag: books

Things we cannot see.

I’m starting to read Start With Why by Simon Sinek. I haven’t gotten very far into it yet, but I just read a chapter with a couple of quotes I really like:

… great leaders understand the value in the things we cannot see.

… it is what we can’t see that makes long-term success more predictable.

These come after a story about American auto manufacturing business men who traveled to Japan to learn from Japanese auto manufacturers. While the American factories solved an issue with how car doors fit by employing a person to use a mallet to ensure a correct fit, the Japanese factory took a different approach. The Japanese factory went back to the design of their components to make sure the engineering was done in such a way that the doors fit correctly every time. It really didn’t make much difference in the bottom line, but it’s important in the sense that the Japenese factory was solving the right problem instead of just fixing the symptoms.

Another quote:

So many organizations function in a world of tangible goals and the mallets to achieve them.

I think this is very applicable to software development. There are so many things when writing software that are analogous to fixing doors with a mallet. When we have defects, do we send them to the person with a mallet to just “fix it” or do we go back to the design and see where we could improve at a more fundamental level? How can we improve our design, or our process, so that we don’t need somebody with a mallet at the end of the line just to get things functioning?

When working with non-developers, it is often difficult to convey the importance of tackling technical debt, or spending twice as long on a feature just to “do it right”. But these things are important. They may not show up to the end user, but they show up in long term success.

Just some food for thought…