The Hardest Parts Of Working In Software Development

16th March 2023

Hollie

During the pandemic, I had the opportunity to be introduced, more formally, to the world of Software Development.

It was already on my radar, having family within the sector in varying roles; however, given the circumstances, it wasn’t until this point that it was suggested that I look into the possibility of it as a career.

Now, in school, ‘on paper' (does that phrase even work outside of the villa?), I did okay if you’re going off results alone.

And yes, I’ve done an escape room or two and thought I was a genius for almost preventing the oncoming apocalypse (which is ironic in hindsight because I almost ripped a monitor apart to do so, much to my fellow escapee's amusement).

But in this role, everything is entirely new and changing and can appear scarily complex.

There is the external pressure every Developer faces, working within an industry where it can feel like there is an endless, evolving list of things required to learn. We must utilise our learning to produce an outcome that satisfies and exceeds the client's requirements and expectations.

I am the first to admit that these pressures can severely impact your overall progress.

It can lead to issues of:

  • Overthinking - by overcomplicating the problem, attempting to tackle the whole task in one go, or simply not taking the task at face value

  • Second-guessing yourself - to the point where you divert yourself from the solution you already suggested in the first place, oh how I’ve done this. Or, on a deeper, more existential level, your position as a Developer, in general,

  • And underpinning all of this, a lack of confidence - which can stifle and dishearten you from what progress you have made.

Therefore, to tackle this issue and promote a more positive outlook on my Development journey, I am attempting to stick to the following:

You can want to do your absolute best and make mistakes.

Trying things and happy accidents are how you sometimes come to solutions.

Like the debacle of the escape room, I mentioned previously, Developing is about overcoming and solving problems. As much as this can be one of the most frustrating aspects of the role - by not having an immediate solution - it is simultaneously one of my favourite parts about being a Developer.

The satisfaction of solving problems is unparalleled. Therefore, the journey to a solution should be appreciated and not dreaded.

Break the problem down.

Something which has helped enormously is the advice not to tackle the whole task all at once, which probably seems obvious.

Break it down into smaller, more manageable steps so you are not over-faced, overwhelmed, and lead yourself to self-made confusion and frustration.

Asking for help is not a weakness.

I am so grateful to be part of the team at Pecometer.

As budding Apprentices, we are surrounded by lovely, approachable and knowledgeable people who are patient enough to talk through a problem with you, helping you understand how to reach the solution and resolve this for yourself if faced again in the future.

To follow the sage advice I was given, “Don’t struggle”.

Learn learn learn.

Learning on the job is a given. As I have previously stated, having knowledgeable colleagues to ask for help is an invaluable resource.

However, taking the initiative to supplement your technical education outside of office hours is a choice and one that should be considered, circumstances dependent.

That list of things to learn may appear endless, but what do you need to know to fulfil your role?

Taking the time to improve your knowledge and skills on things that you know you’ll be using daily will only increase your confidence, making you a much more competent Developer and reducing the internal stress you create for yourself.

Related posts