Learning less than Normal
This goes to people who have high egos when they get the position. Kindly, it’s just a privilege because you show a lot of skills. Both technical and non-technical are vital before you become a senior developer. Be humble. Learn more than junior devs. Dedicate your time to a lot of research. It’s better to have some knowledge of algorithms, libraries, and design patterns.
Running Away from Minor Responsibility
It’s true, as a senior everyone looks what you gonna do. When you become a senior dev, it doesn’t mean you sit away from codes. What if something is difficult for your juniors? You must be there, write the code or do what you can to achieve it. Don’t give junior teams a difficult time when they try to reach out for help. Some seniors assume and avoid managing junior teams, it’s your job. You cannot learn from your minors if you can’t manage them.
Poor Planning – Avoiding Software Engineering Process
Please! Please, I believe any senior engineer knows the correct path to follow before programming. It’s called the software engineering process. Any computer science student was taught that in college, while the self-taught programmers I believe internet got every knowledge. Just plan your work well before allocating it to your junior teams. You must discuss with juniors the relative problems, then hear on both sides any possible solution.
*Googling is for Juniors
Stop calling yourself a hero, we all need stack overflow. Despite your ten years’ experience lol, there are problems you can’t fix. We need each other. Read the blog post, Quora, and any other important resource. Just as the Bible says, "Ask and you shall be given. The problem you are facing, someone has experienced, or if not then post it.
Prioritizing your designs and not the End-Users
Remember software development is just like any other manufacturing company. You need to bring out the product as required by the client. Stop implementing your things while avoiding the designs of your client. Yes, there is room for correcting your customer, but on most occasions maintain what he/she wants. Understand their needs and make the application as simple as possible.
To be Continued…..Part 3
Top comments (0)