Logo

dev-resources.site

for different kinds of informations.

The Single Most Important Lesson I’ve Learned Working As A Software Engineer For 5+ Years

Published at
2/2/2024
Categories
webdev
beginners
lessons
career
Author
_ndeyefatoudiop
Categories
4 categories in total
webdev
open
beginners
open
lessons
open
career
open
Author
15 person written this
_ndeyefatoudiop
open
The Single Most Important Lesson I’ve Learned Working As A Software Engineer For 5+ Years

Not all lessons are created equal.

Some lessons we learn are small. They are little reminders along the way of what truly matters.

Other lessons are giant. They fundamentally change the course of our entire lives.

Over the past 5+ years working as a Software Engineer, this is the single most important lesson I've learned:

The best leverage doesn't come from software; it comes from people.

We are all too familiar with sentences like "Software is the best leverage." However, people are.

And here's why:

Reason #1: You can't produce great software without great people. 

It's plain and simple. Great software comes from great employees. Without them, you're stuck with a buggy, frustrating product that won't make you money. What's worse is that it ends up costing you more in maintenance and infrastructure.

Cheers to great people

Reason #2: You can't come up with the best solution on your own. 

Before I became a dev, I had this idea of a lonely programmer hiding in a room only to emerge with a perfect piece of software. However, this is entirely false. Rather than crafting code in isolation, the process involves collaborating, seeking feedback, and engaging in brainstorming sessions before arriving at the optimal solution.

MJ saying to ask for help

Reason #3: You need people to maintain your software. 

Once your code is out in the wild, you have to keep it up, add features, and fix bugs that will inevitably come. And that's where having the right team becomes essential.

Complexity increase

Reason #4: You need people to train others. 

If software engineering was simply about teachable skills, ChatGPT would be enough. However, training requires the human touch of empathy, encouragement, and soft skills transmitted by others.

Quality training

Reason #5: You need people so you can sell them your software. 

No people means no customers. No customers means no money💸. And no money means you can't continue supporting your software. So, at the end of the day, you need people willing to buy your product.

No people, no money

Now, if you're a junior dev, why is this relevant to you? It means :

  • You don't have to sweat over coming up with the best idea on your own. 
  • No matter how much care you put in the code, it will decay, etc. 
  • You can leverage other people's skills/experience.

So relax and enjoy the process 😉.


Thank you for reading this post 🙏.

Leave a comment 📩 to let me know what you think.

And Don't forget to Drop a "💖🦄🔥".

If you like articles like this, join my FREE newsletter, FrontendJoy, or find me on X/Twitter.

lessons Article's
30 articles in total
Favicon
Career Lessons Learned from Mistakes
Favicon
International drivers license Italy
Favicon
Discover Top Drumkit Lessons with Expert Drumkit Teacher in Brisbane
Favicon
20 things i wish i learned before college
Favicon
Worst Hire - my lessons
Favicon
Lessons That Forever Changes My Software Engineering Career
Favicon
The Single Most Important Lesson I’ve Learned Working As A Software Engineer For 5+ Years
Favicon
Exploring the Universe: How Cosmic Perspectives Unlock the Secrets of Life
Favicon
I built a tech startup and it failed. This is what I learned. 1/3
Favicon
6 lessons from a technical founder
Favicon
CTO last day: reflections, mistakes, and some learnings
Favicon
Things I learned.
Favicon
Lessons from a student hackathon
Favicon
8 Things I've Learned Working in a Legacy Codebase
Favicon
Lessons I have learnt from Project Management
Favicon
What I learned from CREATIVITY, PIXAR Director's Book
Favicon
My non-dev side project got me 700 subscribers & 4000+ traffic
Favicon
Hacktoberfest 2020: Lessons learned as Maintainer
Favicon
I fell through my bed the other day
Favicon
3 lessons from 3 years on joining startups as a Software Engineer
Favicon
Lessons learnt in year three as a software engineer
Favicon
That blank stare
Favicon
6 Lessons learned from upgrading a Rails app
Favicon
Lessons learned from surviving an application attack
Favicon
Things I’ve learned in a skeleton crew
Favicon
5 lessons I've learned during my first year as a Software Engineer
Favicon
Remove a commit from history in Git – local and remote
Favicon
7 years as a developer - lessons learned
Favicon
If you want to ship a side project, start with unlearning the best practices
Favicon
2018 FIFA World Cup: Three Key Lessons for Web and Mobile Developers

Featured ones: