Complexity

Often times, software engineers are faced with the prospect of adding new functionalities or checking in new code that seems to be beneficial. The common reasoning goes like this: why not? What do we have to lose? We already wrote it. It will provide the customers with more options.

In reality, what seems like a simple addition is more harm than good. These small changes introduce friction and weight that the engineering team will need to continuously maintain and support. These are efforts and time spent being anchored and bogged down rather than spent on doing the next big thing.

Flickr engineers were not sitting down doing nothing when they missed Instagram and Microsoft engineers were definitely not slacking (I was there) when they missed on web and mobile. They were just being busy doing busy work and adding anchors on themselves.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.