DEV Community

Sohail Nasir
Sohail Nasir

Posted on

What sort of developer should I be

Since I started my career 15 years ago, there's been one question that's continually worked its way through my mind. Over the years, the answer has changed many times.

For the next few minutes, I'd like to explore what I thought the answer was at different stages of my career, why I thought that way, and perhaps some of the things happening in my life that influenced those decisions.

Photo by RUT MIIT on Unsplash

I want be a serviceable developer

I graduated with a decent degree in Computing with Games Development and worked as an intern in a foreign country. We'd come out of the 2008 financial crash, and job markets were starting to recover.

I got my first job, and my confidence was all over the place. I couldn't believe my luck. I'd finally made it onto the career ladder, working for a small company of around 30 people.

I addressed people as Sir, Mr Smith, Mrs Bates or even Lord of the Manor, until I realised this wasn't 1970s England anymore!

I wanted to be a "good" developer. Someone who could pick up any task and be seen as a safe pair of hands rather than just the junior developer.

I was single, living with my parents and full of optimism. I wrote games in my spare time and had what I thought was a decent understanding of C#.

Oh boy, was my first task a shock!

I had to work on a new feature that was around the document processing codebase that wasn't explained particularly well. It took me two weeks, it didn't work, and I remember thinking... what the hell have I got myself into?

I saw people writing code so much faster than I could, with an understanding of the subject that was second to none. I wanted to be one of those people, rather than someone who struggled with the basics.

The other team members I worked with helped me enormously, and I'm still grateful to them today. Eventually, I went from someone who knew zilch to someone who could implement features, join the pub lunches and become something of a mascot.

When I eventually left, I felt I'd done everything I could at that place at that particular time. I also wasn't a fan of the new CTO, who was a bully. That was a shame, because I genuinely loved that place and had four very happy years there.

So, did I become a serviceable developer in the end?

Answer is yes I did

I want be a senior developer

Let's skip forward a couple of boring years.

I found myself at a lovely company with an absolutely legendary team. During my almost two years there, I learnt a lot, and I owe much of my development style today to some of the fantastic people I worked with.

This company had a ridiculous amount of talent, and its hiring policies were really strict. The recruiter who put me forward for the job told me they'd rejected so many of his candidates.

Whilst I learnt a lot and faced some difficult tasks and challenges, I also recognised an uncomfortable truth, getting promoted wasn't impossible, but it was going to be tough given the structure at the time. There were a lot of talented colleagues ahead of me who deserved a promotion more than I did.

After slaying multiple dragons and being forged and tempered by a group of master craftsmen, I felt ready.

A recruiter reached out to me on LinkedIn with the promise of my dream... that much coveted senior developer title. I took the job and, well, hated it. I quit after four months, but from that point onwards, I had "Senior" in my title... so there is a win.

Photo by Matt Ridley on Unsplash

I want to be a disrupter

2019.... The word "disruptor" was being thrown around everywhere.
Bye-bye, corporate hell... hello, corporate cringe!

A lot was happening in my personal life, too. I got engaged and felt ready to let my personality come through more freely. I had a mouth on me, but I also had the knowledge and skills to back it up.

I hated the drudgery of the 9-to-5. I hated the everyday inefficiencies of processes that hadn't been properly thought through or systems that hadn't been architected well enough.

I hated seeing people being bullied, and I hated the mindset of going to work, getting paid, going to sleep and doing it all over again.

We spend around eight hours a day, five days a week at work, give or take. Why should we spend that time hating it?

So, I took a job at a start-up doing something interesting in a domain I knew a lot about.

I wanted to take my game to the next level, but I also wanted to prove to myself that I could lead and be disruptive.

I started writing articles about different thought provoking subjects and began proving that I had what it took to be that disruptor. I was architecting good solutions that are still in place today, even though some of them went against common practices.

My ability to lead and contribute was noticed, and I finally got the opportunity to formally lead a team when the lead developer left.

But then... depression hit.

I stopped being that person. I became a shell of myself, easily distracted and struggling to perform. I was spoken to several times about my performance, and I didn't understand what had happened to me.

Although I was never fired, I eventually relinquished the lead role and slowly found myself doing only basic tasks.

Eventually, I decided to leave. I felt like the ship was sinking due to financial woes brought on by the pandemic, and I was sinking with it.

Photo by Andrew Teoh on Unsplash

I don't want to be a developer anymore

Burnout is real. Depression can be debilitating, and ignoring either can be detrimental.

I left the start up and went to a consultancy. I loved my first day and that's all about I loved there and got fired after 2 weeks. I wrote about it in another article here.

The experience shook me, and, to be honest, after a couple of failed technical interviews, I told my wife at the time that I thought my time as a developer was over.

I was miserable. I had two kids, yet I felt I couldn't make anything of myself.

I scoured the job market and eventually found a role with office locations that were perfect for my situation at the time, it was still in tech but not a developer role.

I applied, got an interview and went through the entire process.

During the final interview, the partner at the firm looked at me and said:

"I have a concern..."

My heart sank. I'd already been without pay for two weeks. Was I going to have to wait even longer?

He then said:

"You probably won't do any development here. Is that OK with you?"

I nodded. That was absolutely fine with me.

I started this job 4 years ago and for the first time in my career I was no longer a developer but as a "senior consultant".

It felt a bit like when a football player retires and becomes part of the backroom staff. My time on the pitch had come to an end and the days of wearing shell suits and barking orders at players had started.

I went on my first project as a "team lead" for a development team with the expectation to manage developers who were twice my age.

Except, two months into the project, the client approached me.

"We have a VB6 program that handles our finances, and we need it looked at ASAP. Have you done any VB6?"

I'd used it back in my junior year, so, as a favour to the client and wearing my consultant hat, I took a look.

I found the issues, fixed them and shipped the changes.

Whilst talking with the client, I also reviewed some code written by another consultancy. I immediately spotted a security vulnerability and pointed it out to the client, who then got that consultancy to fix it.

One day the client pulled me to one side and asked:

"Do you mind doing development on a regular basis?"

I said not really, and, lo and behold, I managed to inherit a lot of .NET code from a consultancy that had lost the tender for the project.

I took on the position of team lead and senior developer with the client and continued working there for another two years.

Eventually, the project came to an end for me, as I needed to take some time off whilst going through a divorce.

Photo by Samuel Regan-Asante on Unsplash

Maybe I want to develop again

I eventually returned after a lot of emotional turmoil in my personal life. I won't get into the details here, but I was pretty broken.

At the same time, though, I felt I could finally start healing and actually begin managing my depression.

I received a message from a manager at my consultancy asking whether I knew a couple of programming languages they needed for an upcoming project.

I replied that I did, but that I was still on sick leave.

He asked when I was planning to return. I told him within the next couple of days.

"Good. Come and see me when you're back."

I returned to work, still feeling pretty broken, and was told I'd be on "the bench".

For anyone unfamiliar with consultancy terminology, being on the bench means you don't currently have a project. You're generally expected to either wait until you're assigned to one, complete training courses or contribute to company initiatives.

I took my first day as it came and thought I'd message the project manager who had originally contacted me.

He called, we had a chat, and the next thing I knew, I was no longer on the bench. I was back doing project work.

Over the next few weeks, I used my client-facing skills to help settle the client in, my leadership skills to organise the work, and finally my development skills to close tickets.

In that moment, when I was feeling low and potentially heading towards another downward spiral, I seized the opportunity and climbed out of my rut.

I finally realised something... I actually wanted to keep developing.

In the age of AI its easy to lose sight of what development is, for some people its writing prompts, checking the code and building something, for others it might still be writing code, whatever it becomes for now I still want to be a developer.

There are a lot of people I want to thank, and I'll attempt to name them here using their first names (or nicknames). My memory is terrible, so if I've missed anyone, I'm sorry!

So in no particular order, thank you Gary, Russ, Dan.R, James, Will, Mark, Jim, Jacek, Dan.B, Sancho, Matt, Lewis, Sonya, Allan, Alex, Elena, Harveer, Tony, Hoskies, Dixon, Rob.A, Christian, Joe, Bakara, Tim, Ed, Dominic, Brad, Robbie and many others.

I also want to thank my family as well.

You've all challenged me, helped me grow, and I'm forever grateful.

Thank you.

Top comments (0)