We all learn lessons in life. Every book you pick up has its own lesson or lessons. You look around and you learn. You search on the internet and here is our blog. And a lesson again. Even five… 5 software development lessons from Stephen McLean that we are going to present to you today.
Stephen McLean is a software developer who shares some of the lessons he has learned along the way. We found them reflecting our own thoughts and decided to share them with you. So, here they are:
- Never Assume
Never assume that someone will do something just because you’ve asked them to.
Never assume someone understands what you’ve told them, even if they say they do.
Never assume the other party is wrong.
- Non-Technical problems are the most difficult.
Figuring out how to help on-board or mentor new team members. Trying to smoothly introduce something new to the development process.
- Think first, code later.
Stop, and think about the problem, not the solution. Talk to a range of people, not just developers.
- What you create is more important than the tools used to create it.
In frontend development, there is a new framework every other day. And while it’s important as a developer to keep up, the end users just want it to work.
- Every role is equally important.
A project doesn’t work without representation from each role and similarly doesn’t work if resourcing isn’t shared equally amongst the different resource types.
Keep learning! And read more here.
And let’s finally get software development roles explained! It’s never too late!