{"id":2041,"date":"2016-04-26T08:00:36","date_gmt":"2016-04-26T06:00:36","guid":{"rendered":"http:\/\/codingwithempathy.com\/?p=2041"},"modified":"2016-04-26T21:25:36","modified_gmt":"2016-04-26T19:25:36","slug":"the-proactive-software-developer","status":"publish","type":"post","link":"https:\/\/codingwithempathy.com\/2016\/04\/26\/the-proactive-software-developer\/","title":{"rendered":"The Proactive Software Developer"},"content":{"rendered":"
I recently wrote about lessons I’ve learned from my personal burnout<\/a>, and touched on the topic of being proactive and how this is helping me move forward. My\u00a0attitude towards being proactive is greatly\u00a0inspired by Steven Covey’s first habit: “Be Proactive”<\/a>. I want to explore what’s involved in having a proactive mindset<\/a> as a software developer and why I believe it’s something every developer should strive for.<\/div>\n

<\/p>\n

Reactively speaking<\/h2>\n

We can’t talk about being proactive without first talking about its opposite ugly brother; being reactive<\/strong>.<\/p>\n

Reactive<\/a> –\u00a0acting in response to a situation rather than creating or controlling it.<\/span><\/em><\/p><\/blockquote>\n

In other words, reactive people allow external events or factors to dictate their reactions in their\u00a0lives. Strong emotional reactions\u00a0are common in reactive people, as they allow themselves to be defined\u00a0by other people’s actions.<\/p>\n

It’s easy to fall into the reactive mindset when certain conditions are right, especially when we are tired or our mind is preoccupied with something else.<\/p>\n

Having a reactive mindset over a long period of time can push you into a state of loss or need, which over time can develop into desperation, blame and even depression. This can arise after many years of exhaustion or constant financial or emotional issues.<\/p>\n

Examples of being reactive: “I have to attend that boring retrospective again. It’s such a waste of time.” or “If only I made more money, I’d be happy”.<\/p>\n

These examples clearly show external forces leading to reactive emotions. Firstly “frustration” because the meeting is “forced” and they see no value. Secondly “desperation” because the money situation is \u00a0assigning their happiness to having more money.<\/p>\n

The choice of\u00a0being Proactive<\/h2>\n

Being proactive is all about taking responsibility of your\u00a0life. Where you take responsibility for your actions and reactions. We can’t always change what happen to us, but we can decide how we choose<\/strong>\u00a0to react. Only you are responsible for how you react to any given situation.<\/p>\n

Proactive<\/a> –\u00a0creating or controlling a situation rather than just responding to it after it has happened.<\/span><\/em><\/p><\/blockquote>\n

The definition also supports this. But what does it mean to take responsibility and choose your reaction?<\/p>\n

Although we care about a great many things, which may reside in our Circle of Concern, it’s only when\u00a0focusing on matters that are within our Circle of Influence, we can truly be proactive.\u00a0Meaning looking at and caring about things that can be done something about. Usually this will start with yourself<\/strong>.<\/p>\n

So being proactive\u00a0is a choice<\/strong>.<\/p>\n

\"you\"
Photo credit: Photo Extremist<\/a> via Visualhunt<\/a> \/ CC BY-NC-ND<\/a><\/figcaption><\/figure>\n

The Proactive Developer…<\/h2>\n

As with other parts of life, being proactive relates very well to the field of software development. Here are some important aspects of what a proactive developer does.<\/p>\n

…is present and aware<\/h3>\n

Much of becoming proactive is about listening to your feelings and reactions to external events, and choosing<\/strong> a reaction. Being mindful<\/a> about yourself throughout the day is a key skill here. The first step is noticing and acknowledging the feelings and reactions you are having before expecting to be able to change your reactions. It’s amazing how everything changes once you’re willing to accept adjusting your own view on the world.<\/p>\n

Be very clear on what your personal values are and how these\u00a0relates to your work, colleagues and employment.<\/p>\n

“How are you starting to feel when reading another developers code-review of your code where it has been slaughtered as not-fit-for-production?”<\/p>\n

“Why are you growing frustrated \/ angry \/ sad when speaking to … about …?”<\/p>\n

…communicates\u00a0in proactive terms<\/h3>\n

Good communication is hard, but a proactive person will seek out opportunities to make themselves heard from when needed, instead of waiting for others to contact them. A typical example is when making a mistake<\/a>. A reactive person would rush to fix that mistake and potentially introduce others, whereas a proactive person will announce the mistake to anyone needed and explain their next steps.<\/p>\n

How we phrase ourselves is crucial to how we think, and is also equally obvious for the next person\u00a0to understand where you are.<\/p>\n

A reactive person will begin sentences with:\u00a0I can’t, I have to, if only.<\/span><\/p>\n

A proactive person will begin sentences with:\u00a0I can, I will, I prefer, I choose.<\/span><\/p>\n

…seeks opportunities, not limitations<\/h3>\n

There will often be limitations at your current employment where things aren’t how you’d prefer them to be. Nor are they going to change any time soon. A reactive person would fall victim to this and accept defeat since that they\u00a0can’t change anything. Meaning they are focusing on their Circle of Concern.<\/p>\n

A proactive developer, on the other hand, will focus on their Circle of Influence, and concentrate on what they can change or focus on.<\/p>\n

By continuously focusing on your immediate Circle \u00a0of Influence, you will not only find that you are able to get work done, but you will also realize that said Circle of Influence will expand.<\/p>\n

…learns from mistakes<\/h3>\n

We will make mistakes in our jobs. The key is to not let ourselves be defined by the mistakes we make, but rather the learnings we do and be\u00a0willing to accept feedback, even if it isn’t good.<\/a> It will be a great learning opportunity.<\/p>\n

…sets themselves up to succeed<\/h3>\n

A proactive developer takes steps to set themselves up to succeed<\/a>, by having focused goals and creating habits that aid them along the way.<\/p>\n

Part of this is being a great team player. Thinking win-win and looking for synergies.<\/p>\n

…improves\u00a0themselves<\/h3>\n

A crucial part of being a proactive developer is taking active measures to keep yourself up-to-date on the technologies that mean the most to you, work-wise or hobby-wise.<\/p>\n

A reactive developer would most likely seek to improve others, whereas a proactive developer will seek ways to be the change<\/strong> they want to from others, and thus leading by example.<\/p>\n

…is aware of their context<\/h3>\n

Focusing on your Circle of Influence will allow you to do the things that give you most value and that you can actually change, but you need to be aware of the context you are in.
\nIf you are only focusing on yourself without realizing the needs and expectations of your team \/ department \/ project then you may just end up focusing on the wrong things.
\nBy starting with the context it’s easier to make every day decisions and show how you\u00a0are proactively considering the bigger picture.<\/p>\n

Examples<\/h2>\n

Following are a few examples to give you an idea of how reactive vs proactive mindsets of a software developer may differ.<\/p>\n

When working in a software team, you often need tasks or stories to work on. How do you go about\u00a0selecting tasks?<\/strong><\/p>\n