Senior Archives - LDNDeveloper

Andrew Pallant – A Strategic Leader in Engineering

Introduction

In the dynamic landscape of technology, effective leadership is crucial for driving innovation, fostering collaboration, and achieving organizational goals. As a Vice President of Engineering, I have had the privilege of witnessing Andrew Pallant’s remarkable journey—a journey that exemplifies technical excellence, strategic vision, and unwavering commitment to customer success. In this article, we’ll explore Andrew’s impact, his role in shaping engineering teams, and the principles that guide his leadership.

7 Soft Skills That Senior Developers Should Have

Developers often ask what they need to do to make it to the level of a senior developer. They can gain all the programming skills in all the popular and new software frameworks, but they will not be anything more than just a developer. A Senior Developer needs to have some fundamental soft skills.

What are soft skills?
Soft skills are how you interact with people, tasks and projects where hard skills are the skills we learn at college, online tutorials or books ( “HOW TO DO” skills ). Soft skills are tough to achieve and are often part of a persons natural tendencies. Soft skills like hard skills can be learned, but not easily. Soft skills can get better through practice and time just like hard skills. An example of hard skills is carpentry. An example of soft sills is a skill that is transferable to any job like being a team player.
Continue reading 7 Soft Skills That Senior Developers Should Have

Development Team Relationships

This week I pushed out some old blogs outlining the relationships between senior and more junior developers. I did this because I thought it was very important to listen to each other. We can all learn from old and new experiences. Continue reading Development Team Relationships

How a Senior can Help a Junior Developer

Senior developers have a responsibility to help those who are new to the profession. We are the one group of people that the junior developer can turn to after college. Essentially the college gave the new developer 2 years of education, a piece of paper and tossed them out to sink or swim.

I personally do not like to see anyone sink. I believe no matter what the skill set is, a person could be a little better if a helping hand is given. I am not suggesting a babysitter, as no one really wants that. I am suggesting an open door, an open mind and a little patience. Juniors will make mistakes and they will often be a little cocky thinking they know it all coming out of school, but we need to remember their minds are still in the stage of learning.

Juniors can learn much more at their stage in life. Their minds are like sponges and soak in the good and bad habits and knowledge that we share with them. The best thing we can do for them is to teach them everything we know, encourage them to do extra learning on their own and to listen to them. When I last managed a small team, I asked for a weekly report, which consisted of:

1. What are they working on?
2. Where are they on the schedule of tasks?
3. What obstacle have then encountered? Are they still stuck, if not how did they over come it?
4. What is one thing they learned new this week?

During our weekly meeting, I would get one or two of the developers to talk about either the obstacle or their new found knowledge with the rest of the team. This way all new and old developers had a chance to share and learn from each other.

In summary, help them learn in every aspect. Listen to their ideas and new found knowledge. Have an open door for questions. Lastly; be cautious of your bad habits.