Intro

People skills – the often overlooked superhero of an engineer's toolkit. Picture this: you study computer science in university, thinking your days will be a solo codeathon, a language spoken only between you and your screen.

But here's the plot twist: reality hits different. Engineering isn't a one-person show; it's a full-on ensemble. It thrives on collaboration, synchronized efforts, teamwork, and a culture of mutual support.

Guilty as charged – I fell into the "I'll just code all day" trap too. Time to unravel the truth. Let's dive into the intricacies of engineering, where good collaboration isn't just a bonus, it's the main feature. Ready for the real story? Let's break it down.

Turns out there is more to this job than just coding...

Before my start into the world of programming, I held a simple belief: engineers spent their days immersed in code, with little need for interaction once the coding tasks were done. No customer talks, project discussions, or client meetings – just pure coding, or so I thought.

Reality, as it turns out, had a different script. Upon embarking on my programming journey, I discovered a profound satisfaction in constructing things, in the perpetual process of learning and improvement. The idea of spending an entire day engrossed in coding without the need for conversation seemed like a dream job.

Upon entering my first role as an engineer, a paradigm shift reshaped my perspective. It dawned on me that I lacked the needed skills and a comprehensive understanding of the business requirements crucial for the accurate implementation of the coding project. What became unmistakably evident was the imperative for collaboration and seamless communication.

Engineering is one of the most collaborative fields out there

There is so much need for collaboration and alignment to effectively deliver solutions that can scale long-term. Just 1 person working in isolation and making decisions will cause a lot more harm than help.

The reason is that for every piece of code we create, someone needs to maintain it. If 1 person is just making isolated decisions → nobody else will know what those decisions were. All of the future changes would depend just on that person.

The goal is to create software that is easy to maintain and adjust based on future needs. And you can only do that with great minds that are working together.

Altering a couple of words in your overall mindset can create a significant impact.

Shifting your mindset from "How can I deliver this solution" to "How can WE collectively deliver this solution" will yield a profound difference.

Final Thoughts

In moments of uncertainty about the right course of action, consistently prioritize what will benefit the team and the organization as a whole. You can never go astray with that guiding principle!