Why Change?

Steve Jones, 2019-02-04

I was reading Change is Hard from Jeff Hackert and I started to think about the ways in which I both change and resist change. I then started to think about the ways in which I ask people to change what they're doing. I do this both at work and in life, with mixed levels of success. The one thing the article got me to think about was the idea that in asking someone to change, I'm implying they are doing something poorly, or wrong, already.

In some cases, that's true. When I coach volleyball, I am often telling someone they are not practicing a technique correctly, and they need to change. The trick here is showing them what they are actually doing, since many of us don't realize when we are moving our body incorrectly. We think we're doing what we were told, and often it's only with video evidence do we realize what we're doing wrong. Once we do, it becomes easier to make corrections.

In technology, this is often more nebulous. There isn't often a set way that we should write code. Requirements vary, our schemas and data differ, and we almost always have disparate (and often not enough) indexes. Asking someone to change could very well mean asking them to admit they built something incorrectly. Sometimes we may do that, but often we have confidence in our work. Asking someone else to change how they build or develop software can be hard.

What can even be harder is getting management to change. We often feel pressure from management, who usually see our systems working well enough. While we may see sub-optimal performance, they see business getting completed. While we see stress and long hours, they see work getting done at the same cost. Changing priorities to improve our applications often becomes secondary when potential new features and functions exist. Telling management they're wrong is not only difficult, it's often fruitless.

Change is hard. Most humans like the status quo to continue indefinitely, even when we know that things can improve with some alteration in our routine. Inspiring others to join in and invest for the future is a skill. It's one that I'd encourage you to develop, both with peers and management.


4 (1)




4 (1)

Related content


Will the next version of Windows be a “Mini-Me” version of Vista? Who knows, and it’s too early to tell, but apparently there’s a mini-kernel version of Windows 7, the one after Vista, which fits into 25MB on disk. That’s a touch lower than the 4GB that Vista takes up. Granted it’s not a full […]

Steve Jones


60 reads

An Hour in Time

Daylight Savings time switches a little later this year. In fact it’s November 4th this year, after having been in October for all of my life. In case you don’t remember which way we move the clocks, here’s a saying: Spring forward, fall back.

5 (1)

Steve Jones


199 reads

Software is Like Building a House

One of the really classic analogies in software is that it’s like building a house. You have a foundation, multiple teams, lots of contractors that specialize in something, etc. And it’s an analogy that’s debated as to its relevance over and over. I won’t go into the correctness of this analogy, but I wanted to comment on it.

Steve Jones

2012-10-08 (first published: 2007-10-05)

290 reads