A missing image of a manager

You must have seen this meme. A group of people is pulling a stone. The first one, that is in the front of the group is labeled as a leader. There’s also another picture, showing a person sitting on the stone and doing nothing. This person is labeled as a boss. If you are a software engineer, this image probably resonates with you. In my opinion, this resonance, is a result of the confirmation bias kicking in, just proving that technical leadership is the only one that’s needed. In my opinion, there’s one more image that should have been added, but was omitted.

The missing picture came to my mind, when I was on my book reading quest, consuming First, Break All the Rules. The  book is based on a Gallup’s institute research, testing how people are being managed and how this changes the way they work. At the beginning, authors are dissecting the poll that they used for their tests. Also, they show a very important difference between the outward and the inward thinking. They describe a leader as a person that looks outward, pulling the line in a new direction, helping other to conquer new territories. It’s interesting that they don’t discuss the boss figure. They discuss the manager, looking inward.

The third picture that is missing is one showing a manager role. It’s not for looking outward, it’s for looking inward, at the people, at the team. Asking them about their goals, their needs and motivating them. I wrote manager role, as this is just a role. Maybe in your organization you’ll find people having two, or even three roles (startups, anyone?). Maybe, unfortunately for you, you’ll find none (complex organizations, gov related companies ruled by policies).

At the end, I’d like to ask you for one thing. Next time, when you see this extremely fitting or soothing presentation slide or meme, think again, why does it suit you? Maybe it’s just a confirmation kicking in? It’s popular to question authorities. Unfortunately for us, it’s still not popular to question self.

Software as Cheap Cr*p

‘You mean the cheap cr*p?’. This is what I heard, when I ask a colleague in London about a local souvenir shop. Unfortunately for me, fortunately for the cheap cr*p shop, I bought a not so beautiful Big Ben replica and brought it back home. My wife was not so happy. The only good thing was that I was able to buy 2 for 3 or 3 for 4. You know, this kind of deal.

When I bought The Cheap Cr*p, I felt that I signed a simple contract containing two points. The first part was easy, it was about being cheap. That’s it. The second was not that obvious. It was about being replaceable or ready to be thrown away.

The cheap cr*p situation recently reminded me of all these not so good code pieces that we all meet and endure. They probably were introduced as a quick fix, something, that is cheap in terms of time spent on the fix. They do not fulfill the other part of the cheap cr*p contract though. I could easily throw away my not so beautiful Big Ben. I did not use it to build foundations of my house. I do not use it as a oven knob. It’s just a piece on a small shelf, that sooner or later will be cleaned up.

Imagine that you’re under pressure, delivering your product on the deadline. You want to make this small change, ensure that your work fulfills the cheap cr*p contract. Remember it. It’s not only about being cheap. The first and foremost is about being easily replaceable and having a short expiration date. Otherwise, this cr*p won’t be so cheap at all.