Insights and advice for professional growth

Please note that the views and opinions expressed on this blog do not necessarily reflect the views or opinions of the company that creators of this blog work for. It is important to consult with a qualified professional before making any decisions or taking any actions based on the information provided on this blog.

prodev.blog


In today's fast-paced, technology-driven world, staying curious and active in your field is more important than ever. Not only does it demonstrate strength in your job, but it also opens up new opportunities for growth and efficiency. As part of the ["Navigating the Path to Seniority: A Guided Journey for Junior Engineers"](https://prodev.blog/posts/navigating-the-path-to-seniority--a-guided-journey-for-junior-engineers) series, this article will explore the advantages of continuous learning and growth.

![A helmet near a pile of books](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a-helmet-near-a-pileof-books.jpg)

### What is Technical Curiosity?. 🤔

Technical curiosity refers to the drive to learn and explore new technologies, experiment with innovative ideas, and continuously build your skill set. It's not just about keeping up with the latest advancements in your field, but actively seeking out opportunities to improve and become a better engineer.

### Why is Technical Curiosity Essential for Success? 🚀

Technical curiosity is a key ingredient for becoming an exceptional senior engineer, especially for those who don't have a mentor or manager who pushes their limits. It's important to take control of your own professional development and always seek new challenges.

![A person in a workshop surrounded by tools and prototypes](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/person-in-a-workshop-surrounded-by-tools-and-prototypes.jpg)

### Balancing Work and Learning. 📅

With a busy schedule, it can be challenging to find time to feed your technical curiosity. That's why it's essential to make the most of your time, as we discussed in the article ["Efficient and Productive: Top Time-Management Strategies"](https://prodev.blog/posts/efficient-and-productive-top-time-management-strategies). One way to do this is by using a calendar to block off dedicated time slots each week. Keep it fun by starting simple and having fun while learning, like building a small chatbot if you're interested in Machine Learning. 🤖

### The Power of Community. 🤝

Building a network of peers, mentors, and experts is crucial for sharing ideas and overcoming obstacles in your technical journey. Attend meetups, conferences, and participate in online forums and discussion groups to practice and improve your communication skills, as we covered in ["The Power of Brevity: How to Communicate Effectively"](https://prodev.blog/posts/the-power-of-brevity--how-to-communicate-effectively).

![A group of people brainstorming](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a-group-of-people-brainstorming.jpg)

### Continuous Learning Leads to Better Leadership. ⚡

As explored in ["Engineering Leadership: From Aspiring to Exceptional"](https://prodev.blog/posts/engineering-leadership--from-aspiring-to-exceptional), continuous learning is a vital aspect of leadership development. Leaders who constantly seek out new opportunities to learn and grow are better equipped to tackle complex challenges and drive innovation. By expanding your knowledge and skills, you'll develop problem-solving abilities, improved communication, and a deeper understanding of your field, all of which contribute to your ability to lead and make a greater impact.

### How to create a continuous learning path? 📈 

It's time to start plotting your continuous learning path now that you understand the importance of technical curiosity. Consider the following questions to get started:

- What are my technical goals?
- What resources do I need to achieve my goals?
- How will I make time for learning?
- Who will I turn to for support?
- How will I track my progress and measure my success?

Answering these questions and taking the necessary steps to achieve your technical goals will help you become a lifelong learner. Good luck!


### 💬 Final Thoughts
Technical curiosity is a valuable asset for anyone in technology or engineering. It drives innovation and progress and helps individuals stay up-to-date with the latest advancements. Cultivating technical curiosity requires a willingness to continuously learn, ask questions, collaborate with colleagues, experiment with new technologies, and stay open-minded. By nurturing your technical curiosity, you'll become more productive, innovative, and creative.

This is the final article of the series ["Navigating the Path to Seniority: A Guided Journey for Junior Engineers"](https://prodev.blog/posts/navigating-the-path-to-seniority--a-guided-journey-for-junior-engineers), I hope it has provided some value and you've learned or refreshed some thoughts you may already have around it. I will revise and update the content of these articles every now and then, but I will also continue publishing content relatable to engineers and professionals at different levels.

<a href="https://medium.com/@dev.aaron.gh/navigating-the-path-to-seniority-a-course-for-success-6fc8a7ccaace" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

Part Seven: How lifelong learning is linked to professional development

In a world where technology is rapidly evolving, staying technically curious and active is not only a strength in your job but also a way to find more efficient tools, techniques, and methods to get better at it.

Inquiring Minds, How to Cultivate Technical Curiosity


Problem-solving skills are essential to find efficient solutions to complex problems on a daily basis, make a real impact in our field, and to make informed decisions. Being able to identify and solve problems quickly and efficiently can make the difference between a successful project and a complete failure. Furthermore, effective problem solving can help you reduce stress, increase productivity, and have a better job experience.

In this article, we'll explore a few problem-solving methods and strategies to improve your problem-solving skills.

![a person at the bottom of a mountain of hay drafting a plan to split it to find a needle that is inside of the mountain](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/mountain-of-hay-drafting-a-plan.jpg)

### What problem-solving methods exist?

Problems arise every day in all aspects of life. Luckily, there's a set of techniques to help you solve them, we will explore the following:

1. PDCA (Plan-Do-Check-Act) Cycle
2. 5-Why Analysis
3. Ishakawa (Fishbone) Diagram
4. Simplified Failure Modes and Effects Analysis (SFMEA)
5. The Scientific Method
6. Critical Thinking

Each of these techniques provides a structured approach to problem-solving, allowing you to tackle problems in an organized and efficient manner. Let's take a closer look at each technique and how it can help you solve problems like a pro.

### What is the PDCA Cycle

This technique is a four-step process for continuous improvement. It starts with planning, where you define the problem and come up with a solution. Then, you implement the solution, check to see if it worked, and act on the results. PDCA is particularly useful for solving problems that are repetitive or cyclical.

![The 4 stages of PDCA: Plan, Do, Check, Act](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/pdca.webp)

In practice this is how it'd look, let's say that every time a new feature is implemented and pushed to production, it causes the server to crash. The development team might fix the issue temporarily, but then it reoccurs a few weeks later when another feature is pushed to production.

The team might then use the PDCA problem-solving technique to identify the root cause of the issue. They would first **plan** by identifying the problem and gathering information on when and how it occurs. They would then do a thorough analysis to find the root cause of the issue, such as code inefficiencies or conflicts between features.

Once the root cause is identified, the team would create and implement a solution (**do**). This might involve re-writing code, adjusting server configurations, or adding new monitoring tools. After the solution is implemented, the team would **check** if the problem will be resolved and if the solution is sustainable over the long term. With that, the team **acts** by releasing the solution to production and monitoring the server to ensure that it is working properly.

Using the PDCA technique in this scenario allows the team to continuously improve the reliability of the web application and reduce the time spent on fixing server errors.


[PDCA - sydle.com](https://www.sydle.com/blog/pdca-cycle-61ba2a15876cf6271d556be9)

Here's a mini-episode from Ray Dalio's _Principles_ addressing a similar approach to solving problems: [Youtube](https://youtu.be/B9XGUpQZY38?t=1533)

### What is 5-Why Analysis

"5-Why Analysis" is a problem-solving technique that involves asking "why" questions about a problem in order to determine its root cause. This approach helps you to uncover the underlying issues behind a problem and find its root cause, which is the key to implementing a successful solution.

To use 5-Why Analysis, start by asking "why" five times in a row to get to the root of the problem. For example, if the problem is a machine that is not working, you could ask "why is the machine not working?" The first answer might be "the electrical circuit is broken." Then you would ask "why is the electrical circuit broken?" And so on, until you have asked "why" five times and have found the root cause of the problem.

This technique can be used in a variety of industries and is often used in manufacturing and engineering. It is a straightforward and effective way to find the root cause of a problem and implement a solution that will prevent it from happening again in the future.

[5-whys with examples - Indeed.com](https://www.indeed.com/career-advice/career-development/5-whys-example)

### How to use the Fishbone Diagram

This technique is useful in engineering as it allows you to break down a problem into smaller components, making it easier to understand and solve.

```
          Cause_1  Cause_2
          /        /
         /        /
Problem +----------------
         \        \
          \        \
        Cause_3  Cause_4
```

The Ishakawa diagram is named after its creator, Kaoru Ishakawa, who used it as a quality control tool in the 1960s. The diagram is shaped like a fish skeleton, with the problem being represented by the head and the causes being represented by the bones. To use the Ishakawa diagram, simply draw the fish skeleton and list the problem in the head. Then, brainstorm the potential causes and attach them to the bones as sub-causes. This process can be repeated until the root cause is identified.

[Fishbone diagram - asq.org](https://asq.org/quality-resources/fishbone)


### The Simplified Failure Modes and Effects Analysis technique

This technique is especially useful in industries where product or process failures can have serious consequences, such as aerospace, automotive, and medical devices. By identifying potential failure modes, you can take steps to prevent them from happening.

The process consists of several steps, primarily:

- Listing the potential failures.
- Assessing the severity, occurrence, and detection of each.
- Prioritizing based on risk.
- Identifying corrective actions to mitigate risks.

### The Scientific Method as problem-solving technique

This technique is based on the scientific method and is used to identify the root cause of a problem. Start by defining the problem, creating a hypothesis, testing the hypothesis, and then analyzing the results.

The steps of the Scientific Method are:

1. Observe and define the problem: Start by observing the problem and gathering information about it. Define the problem in clear and concise terms.
2. Formulate a hypothesis: Based on the information gathered, formulate a hypothesis or an educated guess about what might be causing the problem.
3. Test the hypothesis: Conduct experiments to test the hypothesis and gather data to support or disprove it.
4. Analyze the results: Analyze the results of the experiments and draw conclusions based on the data.
5. Evaluate and conclude: Evaluate the results and draw a conclusion about the hypothesis. If the hypothesis is supported by the data, it becomes a theory. If not, the hypothesis must be modified or discarded.

By following these steps, you can ensure that your problem-solving process is systematic, unbiased, and based on data and evidence. This technique is also helpful in avoiding common pitfalls such as jumping to conclusions or making assumptions without sufficient evidence.


### Combining Techniques for Effective Problem-Solving

![Multiple tools, one solution](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/mechanic_working_on_an_airplane_using_multiple_tools.jpg)

It is important to have a toolkit of problem-solving techniques at your disposal. But the best way to tackle a problem is to not rely on just one technique, but to use a combination of techniques that work best for the situation at hand.

For example, you could use the Ishikawa (Fishbone) Diagram to identify potential root causes, then apply the 5-Why Analysis to drill down further into the most likely cause. Or, you could use the Scientific Method to structure your problem-solving approach, and then use an SFMEA to identify potential risks and consequences.

The goal is to find the best approach that will give you a comprehensive understanding of the problem. This way, you can identify both internal and external factors that may be contributing to the problem and arrive at a solution that addresses all the underlying issues.

In short, combining problem-solving techniques allows you to tackle complex problems in a systematic and effective way. So, it's crucial to keep experimenting with different techniques and refining your approach until you find the combination that works best for you.

### Closing thoughts

We've discussed several problem-solving techniques that you can use to identify and solve problems. Each technique has its own strengths and weaknesses and can be used in conjunction with other techniques for a comprehensive understanding of a problem. I hope that this article has provided you with a better understanding of these techniques and how they can help you to become a more effective problem-solver.

I've wrote an [article about how to write an specification document](https://prodev.blog/posts/speccing-1-1--a-template-for-writing-specifications), it provides a template to structure your thoughts and approach when solving a problem, you can find it [here](https://prodev.blog/posts/speccing-1-1--a-template-for-writing-specifications).


### Resources

1. "Thinking, Fast and Slow" by Daniel Kahneman - This book explores the psychology of decision-making and how our minds often lead us to make irrational decisions.
2. "Problem Solving 101: A Simple Book for Smart People" by Ken Watanabe - This book provides a simple and effective approach to problem solving, using the author's own experiences and case studies.
3. "How to Solve It" by George Polya - This classic book offers a systematic approach to problem solving, using mathematical examples to illustrate key concepts.
4. "The 7 Habits of Highly Effective People" by Stephen Covey - This book covers the importance of proactive problem solving and the habits that can help us achieve it.


<a href="https://medium.com/@dev.aaron.gh/" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

Part Six: What problem-solving methods exist?

Problem-solving skills are essential to find efficient solutions to complex problems on a daily basis, make a real impact in our field, and to make informed decisions.

Solving Problems Like a Pro, Tips and Techniques


## **What is a specification document?**

A specification document is a detailed and organized description of a solution to a problem. It helps to clearly define what is expected from the solution and how it will be implemented. This document is crucial for communicating the solution to stakeholders, as well as for guiding the implementation process.

![An specification is like drawing a map to meet your goals in a structured way](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/spec-1-1-1.jpg)

In this guide, we will go over the different parts of a specification document and provide an example for each part. Please note that every project is different, so you may need to adapt this template to fit your needs.

## **Background**

The Background section provides context for the problem the solution is trying to solve. It should explain how the problem was discovered, and any relevant background information.

Example:

> Slow image load times on our e-commerce website has been causing issues with the user experience and leading to increased customer complaints. In order to improve the situation, a solution is needed that will address this issue and improve the overall performance of the website.


## **Goal**

The Goal section clearly states what needs to be accomplished by the solution. <u>This section should be concise and specific</u>.

Example:

> The goal of this specification document is to outline a solution that will reduce the load times for images on the e-commerce website, resulting in a better user experience and reduced customer complaints.


## **Problem**

The Problem section defines the specific problem that the solution is trying to solve. It should be focused on a single problem and not try to solve all problems at once.

Example:

> Improving load times for images on the website, which is negatively impacting the user experience and leading to increased customer complaints.


## **Hypothesis**

The Hypothesis section provides the foundation for the solution. It should be a concise statement (or a few statements) that the solution is based on.

Example:

> By optimizing the image file sizes and implementing a content delivery network (CDN), the load times for images on the website can be reduced and the overall performance of the website can be improved.

## **Requirements**

The Requirements section defines the expected outputs from the solution. It should list the features, views, stakeholders, etc. that will be affected, and how they will be affected. The requirements should be as explicit as possible to avoid any assumptions.

Example:

> - Reducing the load times for images on the website by 20%.
> - Reducing customer complaints around this issue by 80%.
> - The solution should result in images loading faster and appearing smoothly on the website. The solution should not introduce any new issues or negatively impact the functionality of the website.


## **Constraints**

The Constraints section defines the limitations of the solution. This could include limitations in terms of time, effort, money, or other resources. It is important to define these constraints upfront to ensure the solution is achievable within the available resources.

Example:

> - Time: The solution needs to be implemented within a 2-week period.
> - Budget: The solution must be within the $5000USD budget allocated for it.
> - Technical limitations: The solution must be feasible to implement given the existing technical infrastructure.
> - Impact on existing functionality: The solution should not negatively impact the existing functionality of the website.


## **Solution Proposal**

The Solution Proposal section provides a high-level description of the solution. It should give a general idea of how the solution will work, and how it will interact with other components.

Example:

> The solution proposed for this problem is to optimize the image file sizes and implement a content delivery network (CDN). By optimizing the image file sizes, the amount of data that needs to be loaded will be reduced, resulting in faster load times. A CDN will help to distribute the load of the images across multiple servers, further reducing the load times and improving the overall performance of the website.



## Functional Specification

In this section, you will describe the steps that need to be taken to implement the solution. This is where all the work gets done, so it's important to be organized and thorough. You should also include error checking procedures to make sure that the implementation is done correctly.

Here's an example of what this section might look like:

> 1. Research and evaluate different CDN providers to determine the best fit for the website's requirements.
> 2. Configure the CDN to work with the current website infrastructure, including setting up the appropriate DNS records.
> 3. Integrate the CDN into the website, ensuring that all images are being served through the CDN.
> 4. Test the implementation to verify that the CDN is reducing load times for images and improving user experience.
> 5. Monitor the CDN to ensure it is performing optimally and make any necessary adjustments.
> 6. Document the CDN implementation and provide training to the website support team on how to manage and maintain the CDN.

It is important to document any deviations from the plan, as well as any unexpected issues that arise during the implementation process. This information will be used to make improvements in future iterations.



## Technical Specification

The purpose of a technical specification is to clearly and precisely describe the technical details of each functional part. It provides the necessary information anyone in your team with technical knowledge to understand the product, system, or component and to build, test, and implement it.

A technical specification typically includes diagrams, schematics, or other technical drawings to help illustrate the product's design and functionality. 

Writing a technical specification can help to reduce the likelihood of errors or issues arising during development, and helps to maintain consistency and quality throughout the development process.

One way to validate that your technical specification is compliant is by ensuring each part of the functional spec is backed by the technical details.

Example of technical specification for the Functional Specification example above:

> ### CDN configuration
> - Zone type: `Public`
> - Zone name: `my-domain-example`
> - DNS name: `subdomain.mydomain.com`
> - ...

As you can see, the technical details can be mapped to the functional spec step "Configure the CDN to work with the current website infrastructure, including setting up the appropriate DNS records." in the Functional Specification example.



## Dependencies

In this section, you will describe the relationships between tasks based on their sequence. Tasks that are dependent on one another will need to be completed or started in a specific order.

Here's an example of what this section might look like:

> - The DNS records for the website must be updated before the CDN can be configured and integrated.
> - The website support team must be trained on how to manage and maintain the CDN before it is put into production.

It is important to be aware of these dependencies when creating a project plan and assigning tasks to team members.


## Implementation

The Implementation section is where the solution proposed in the previous sections is put into action. This is where the plan becomes a reality. This section is all about executing the plan and making sure everything is working as expected.

The Implementation section should include a detailed description of the steps required to set up and deploy the solution, including instructions for installation, configuration, and testing. The instructions should be precise and easy to follow, so that anyone with the necessary skills can carry out the implementation.

It is important to have a plan in place for error checking and handling any unexpected situations that may arise during the implementation process. This plan should be documented, so that everyone involved in the implementation process is aware of what to do if something goes wrong.

Finally, the Implementation section should include information about the distribution of tasks and the tracking of progress. This could involve creating tickets for different tasks and assigning them to specific individuals or teams, as well as tracking the status of each task and ensuring that everything is progressing smoothly.

Example: 

> 1. Install and configure CDN servers: The CDN servers will be installed in multiple locations around the world to ensure that content is delivered to users quickly and efficiently.
> 2. Connect CDN servers to the origin server: The CDN servers will be connected to the origin server using a high-speed, low-latency network. This will ensure that content is synchronized between the CDN and the origin server.
> 3. Configure content delivery rules: The CDN will be configured to deliver content based on specific rules, such as the type of content, the location of the user, and the available bandwidth.
> 4. Test the CDN: The CDN will be tested to ensure that it is delivering content quickly and efficiently. This will include tests of the delivery rules, the synchronization between the CDN and the origin server, and the performance of the CDN servers.
> 5. Go live: Once all tests have been completed successfully, the CDN will be put into production, and users will start to receive content from the CDN.
> 6. Monitor and maintain: The CDN will be monitored to ensure that it is performing as expected, and any necessary maintenance will be performed to keep it running smoothly.



And that's it! Of course, each project is different and may require more or less sections, but this should provide a good starting point.

<a href="https://prodev-blog-assets.s3.us-west-1.amazonaws.com/downloads/template-for-writing-specifications.md"  target="_blank">Download template here.</a> (Opens in a new window).

Writing specs is an structured way to describe how problems are solved, [click here to know more about problem solving techniques](https://prodev.blog/posts/solving-problems-like-a-pro--tips-and-techniques).

<a href="https://medium.com/@dev.aaron.gh/" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

How to write a specification document for a software project.

A specification document is a detailed and organized description of a solution to a problem. It helps to clearly define what is expected from the solution and how it will be implemented. This document is crucial for communicating the solution to stakeholders, as well as for guiding the implementation process.

Speccing 1:1 - A template for writing specifications



Developing leadership skills give you the ability to effectively manage your workload and lead projects, unveiling your value to any team or organization. Plus, it makes you more attractive to potential employers, as it demonstrates that you are autonomous and require minimal management overhead. In this article, we'll focus on the key leadership skills that you should develop in order to unlock your leadership potential.

## Technical Foundation

![Developing a strong technical foundation is the foundation of effective leadership](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/eng-leadership-01.jpg)

Having a strong technical foundation is essential for any engineer, but it's especially important for Junior Engineers who want to develop leadership skills. It's difficult to lead others if you don't have a deep understanding of the subject matter. So, make sure you're up to date on the latest technologies and industry trends. Continuously improve your technical skills through online courses, attending conferences and workshops, and staying active in online communities.

Tip: Learn a single technology as deep as you can, preferably choose a language in high demand, as it will likely share some patterns that will enable you to learn any other language with less friction.

## Soft Skills

![Effective communication, problem-solving and the ability to inspire others are the key soft skills for leadership](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/eng-leadership-02.jpg)

Leadership isn't just about technical skills, it's also about soft skills. Every good engineer should develop their communication, problem-solving skills, and the ability to inspire others. 

In order to [communicate effectively](https://prodev.blog/posts/the-power-of-brevity--how-to-communicate-effectively), you must be able to explain complex technical concepts in a way that everyone can understand. 

To improve your problem-solving skills, practice breaking down complex problems into smaller, manageable chunks. 

If you want inspire others, you must be able to articulate a vision for the future and motivate others to join you on the journey, one way to go about this is getting in-depth knowledge of the product or service of your organization and understand how it makes its customers lives easier.

## Mentorship and emotional intelligence

![Mentorship is about navigating the path to success with the guidance of an experienced leader](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/eng-leadership-03.jpg)

Mentorship is a powerful tool for personal and professional development, and it's an essential aspect of leadership. 

Find someone who has more experience and knowledge than you, and who is willing to share their wisdom and guidance. They can help you to navigate the challenges of your career and personal life, and to identify your areas of growth. 

Building a strong relationship based on trust and mutual respect with your mentor is crucial.

Emotional intelligence is the ability to understand, manage and express your own emotions, and to understand and influence the emotions of others. It's a key factor in effective communication, problem-solving, and the ability to inspire others. 

A mentor with a high level of emotional intelligence will be able to help you to build effective relationships with your colleagues, friends and family.

## Identify your areas of growth

![Identifying your strengths and weaknesses is like navigating through unknown territory](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/eng-leadership-04.jpg)

Identifying your areas of growth is an essential step in self-improvement, it allows you to focus your efforts on the areas where you need the most development and to make the most out of your strengths. 

The process of identifying your areas of growth requires self-reflection, honesty and a willingness to change. One effective way to identify your areas of growth is to conduct a self-assessment, or by simply reflecting on your skills and abilities. Another way to identify your areas of growth is to ask for feedback from others. 

Once you've identified your areas of growth, the next step is to set goals and create an action plan for achieving them. 

Remember, self-improvement is a continuous journey and requires constant effort.

## Conclusion

Leadership skills are essential for Junior Engineers who want to advance in their careers. By developing a strong technical foundation, focusing on soft skills, and setting goals, Junior Engineers can become effective leaders. 

In the next article in this series, ["Solving problems like a Pro"](https://prodev.blog/posts/solving-problems-like-a-pro--tips-and-techniques), we will explore in depth how to identify a problem and break it down into smaller units, stay tuned!

Remember, leadership is a continuous journey, so always be open to learning new things and improve yourself.

<a href="https://medium.com/@dev.aaron.gh/" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

Part Five: Excercise Your Leadership Skills Without Being a Manager

This article provides tips and examples on how to become an exceptional leader by focusing on mentorship and emotional intelligence.

Engineering Leadership, From Aspiring to Exceptional



Hey there! 🙋‍♂️ Communicating effectively is a must-have skill in any profession. One way to do that is by being brief and getting straight to the point. Not only does it make your message crystal clear, but it also saves time in fast-paced work environments. In this article, we're diving into the importance of brevity in communication, how to achieve it, measure its effectiveness, and even how to start implementing it in your next meeting. 📅 Let's get started!

![Navigating a ship without clear communication is like trying to find your way through a foggy sea without a compass.](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a-ship-navigating-fog-towards-an-iceberg.jpg)

One of the main benefits of brevity is its ability to cut through the noise and get straight to the point. In today's busy work environment, attention spans are short and time is of the essence. By being brief and concise, you can ensure that your message is not only heard but also understood. 💡

## How to develop effective communication skills

To develop effective communication skills, it's important to follow the Hemingway principle. This principle emphasizes short, simple sentences and an economy of words. It also involves avoiding repetition and using a variety of words and phrases. Trust me, it's a game changer! 📚

![Just like an iceberg, the Hemingway principle shows that less is more - only revealing the essential information.](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/like-an-iceberg--the-Hemingway-principle-shows-that-less-is-more.jpg)

I recently took this mini-course on Effective Communication and I think you’ll find a lot of value in it: [https://www.youtube.com/watch?v=2OBewm5guJk](https://www.youtube.com/watch?v=2OBewm5guJk)

## How to measure effective communication

Measuring the effectiveness of your communication can be tricky, but there are a few signs that can indicate that your message is getting through. One sign is if your audience is able to repeat back the key points of your message. Another sign is if they are able to take action based on your message. If you're not sure if your communication is effective, try asking for feedback from your audience. 📊

## How to practice effective communication

Stand-up meetings are a great opportunity to practice brevity. Write your message beforehand, make sure it follows Hemingway’s principles, focus on the key points you want to make during the meeting, avoid getting into too much detail, and try to use relatable examples or analogies to explain complex concepts. You’ll notice it’s easier for your team to understand and remember your message. 🚀

## How (in)effective communication looks in practice

In practice, effective communication can look very different from ineffective communication. 

For example, an effective communicator during a stand-up meeting might use brevity to explain the progress of a project and the next steps for the team. They might also encourage team members to share their thoughts and feedback. On the other hand, an ineffective communicator might tend to use technical jargon and speak at length about project details, making it hard for the team to understand and follow. Understanding how effective and ineffective communication looks in practice can help us improve our own communication skills. 🔍

![Effective communication is the lighthouse that guides your team to the right destination."](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a-lighthouse-on-a-foggy-sea-near-an-iceberg.jpg)

## Conclusion

In conclusion, being an effective communicator is an important skill to master as a professional. Brevity and simplicity can make it easier to keep everyone in sync when you take the lead on a project. 

Speaking of leadership! in the next article [**"Engineering Leadership: From Aspiring to Exceptional".**](https://prodev.blog/posts/engineering-leadership--from-aspiring-to-exceptional) we will dive deeper into the topic of leadership in engineering. We will explore the key skills and traits that are required to become an exceptional engineering leader, and how effective communication is a crucial component of leadership in the field. So stay tuned! 📢

<a href="https://medium.com/@dev.aaron.gh/" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

Part four: What is effective communication?

Learn the importance of brevity in effective communication, how to achieve it, measuring its effectiveness, and implementing it in your next meeting. Get practical tips and examples to improve your communication skills and make your message clear and easy to understand.

The Power of Brevity, How to Communicate Effectively


Welcome to the third installment in the series, "[Navigating the Path to Seniority: A Guided Journey for Junior Engineers](https://prodev.blog/posts/navigating-the-path-to-seniority--a-guided-journey-for-junior-engineers)";  In this article, we focus on skills essential for handling complex projects and meeting tight deadlines:

1. Seting SMART goals
2. Planning
3. Estimation and risk assessment
4. Effective communication, and
5. Adaptability

![Image of a captain plotting a route in a map - via OpenAI](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a-captain-plotting-a-route-in-a-map.jpg)

Image of a captain plotting a route in a map - via OpenAI

## 1. Set S.M.A.R.T. goals

You've probably been in a situation where you've been assigned a task from the backlog but it's poorly described, it can be difficult to know if your efforts are directed towards the expected outcome. To avoid running in circles, it's important to know how to set SMART goals. 

SMART stands for Specific, Measurable, Achievable, Relevant, and Time-bound, and it's a helpful way to ensure that your goals are clear and focused.

Before you start any task, take some time to think and write about:

- [Why is this important?](https://www.youtube.com/watch?v=u4ZoJKF_VuA&ab_channel=TEDxTalks)
- [What specifically needs to be accomplished](https://www.youtube.com/watch?v=1-SvuFIQjK8&t=32s)?
- [How will you measure progress?](https://www.youtube.com/watch?v=1-SvuFIQjK8&t=58s)
- [Is the goal realistic and achievable?](https://youtu.be/1-SvuFIQjK8?t=99)
- [How it fits into your overall objectives?](https://youtu.be/1-SvuFIQjK8?t=125), and
- [When does it need to be completed?](https://youtu.be/1-SvuFIQjK8?t=171)

[S.M.A.R.T. Goals - Attlassian](https://www.atlassian.com/blog/productivity/how-to-write-smart-goals)

**So if you're faced with an ambiguous task like:**

> Title: "fix bug in dropdown where content shows intermittently”
Description: None
> 

**You can use this SMART goals template to structure it:**

> Title: Identify and fix the bug causing the dropdown content to show intermittently.
> 
> 
> Description: 
> 
> - Specific: Identify and fix the bug causing the dropdown content to show intermittently.
> - Measurable: Test the dropdown after the fix to ensure that the content is consistently displayed.
> - Actionable: Research and implement a solution that addresses the root cause of the bug.
> - Relevant: Address the bug as it is a hindrance to user experience and could impact customer satisfaction.
> - Time-bound: Complete the task within two days to minimize any potential or ongoing disruption to the user experience.

**Here's another SMART goals example that feels less formal:**

> Description: Fix the bug causing the dropdown content to show intermittently, identify and address the root cause and test the dropdown to ensure it is consistently displayed, prioritize the user experience and customer satisfaction, appetite for this task is within two days.
> 

As a software engineer, setting clear goals is essential for staying focused and achieving success. While it may not always be your responsibility to provide all the details, taking the time to understand your objectives can help you stay on track and make a meaningful contribution to the project.

In future article, we'll contrast SMART goals versus OKRs. Stay tuned for a comparison of their differences, practical examples, and why tech leads should be familiar with both methods.

## 2. Outline a plan and break it down

Once you have identified your goals, the next step is to outline a sequence that lays out the steps and tasks needed to complete the project. This should include a timeline for each task, as well as any necessary resources or dependencies. A well-organized schedule can help you stay on track and ensure that you are making progress towards your goals.

![Breaking down a plan can be compared to solving a puzzle](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/breaking-down-a-plan-can-be-compared-to-solving-a-puzzle.jpg)

One way to outline your plan is to start with high-level goals and then break them down into smaller, more manageable tasks. For example, if your goal is to build a new feature for a web application, your high-level goals might include:

1. Research and understand the requirements for the new feature
2. Design the overall architecture for the feature
3. Implement the feature
4. Test the feature
5. Deploy the feature to production

It's generally recommended to keep the number of goals low, as having too many goals can lead to feeling overwhelmed and may make it difficult to prioritize your time and resources effectively. 

It's generally best to focus on a few key goals at a time rather than trying to tackle too many at once.

From there, I can break down each of these high-level goals into smaller, more manageable tasks. 

## 3. Break down your plan to estimate time and identify risks

Part of effective time management is being able to accurately estimate how long tasks will take to complete. This involves considering any potential risks or challenges that may arise and allowing for extra time to address them. By accurately estimating your time, you can more effectively plan and allocate your resources, which can help increase efficiency and productivity.

![Once a plan is broken down is easier to forecast](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/once-a-plan-is-broken-down-is-easier-to-forecast.jpg)

**Example of breaking down goals into smaller pieces:**

1. Understand requirements for the new feature
    
    1.1 Review the project specification document
    
    1.2 Meet with the product manager to clarify any questions
    
    1.3 Research similar features in other applications to get ideas and inspiration
    
2. Design the overall architecture for the feature
    
    2.1 Research and review existing architecture for similar features

    2.2 Collaborate with team members to brainstorm design options

    2.3 Create a detailed design plan with input from the team

    2.4 Present the design plan to the project manager for approval

    2.5 Make any necessary adjustments to the design plan based on feedback from the project manager
    
3. […]

Having your plans broken down will make it easier to estimate the time to complete each stage, plus, it can help you identify any dependencies and risks involved.

**Example of a list of tasks with their associated priorities, dependencies, estimates, and risks:**

| **Task** | **Priority** | **Dependencies** | **Risks** | **Estimate** |
|----------|--------------|------------------|-----------|--------------|
| Implement login feature | High | User registration feature | Dependency on user registration feature being completed on time | 4 days |
| Write unit tests for login feature | Medium | Login feature | None identified | 3 days |
| Integrate login feature with backend API | High | Login feature, backend API documentation | API documentation not being up to date | 2 days |
| Fix bug in homepage layout | Low | None | None identified | 1 day |

By including this information in your task list, you can more easily identify and plan for any potential risks or dependencies that may impact your schedule. This can help you stay on track and ensure that you are making progress towards your goals.

It can be overwhelming to know where to start, especially if you're not a seasoned at risk management. That's why we'll be discussing some simple strategies for identifying and managing risks in an upcoming article titled "Risk Management for the Rest of Us: Simple Strategies for Identifying and Managing Risks". Stay tuned for more on this topic!

Breaking down your plan into smaller, more manageable tasks can help you effectively estimate the time required to complete each stage and identify any dependencies or risks that may impact your schedule. By considering these factors and being proactive in your communication with team members and stakeholders, you can increase efficiency and productivity as you work towards your goals. In the next section, we'll delve further into the importance of effective communication in time management.

## **Communicate Effectively**

It's important to communicate effectively with team members and stakeholders to ensure that everyone is on the same page and working towards the same goals. This can help prevent delays or misunderstandings that could impact your schedule.

![Orchestrate communication](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/orchestrate-communication.jpg)

To determine whether your communication is effective and timely, ensure:

- Messages are clear and concise.
- Ensure to address the right audience with the right level of detail and style.
- Practice actively listening and responding to feedback.
- Choose the right message channel (e.g., email, slack, face-to-face meeting).
- Set up reminders for important actions and deadlines.
- Adapt to fit the needs and preferences of your audience.

Call-to-action: In your next meeting, try asking how often they would prefer to receive updates, and see if there are any changes you can make to your communication style to better meet their needs. It will pay off!

By being proactive and adapting to change, you can maintain momentum and keep your project on track. In the next section, we will discuss the importance of flexibility and adaptability in time management and how to incorporate it into your schedule.

## Flexibility and Adaptability

Imagine you're working on a software development project and you've carefully planned out your schedule and set your goals. You've even gone so far as to break down your tasks into smaller, more manageable pieces and identified any potential risks or dependencies. You're feeling confident and ready to tackle your work, but then something unexpected happens. Maybe a team member gets sick and can't work on their portion of the project, or perhaps the scope of the project changes and you need to pivot your approach.

In situations like these, it's important to be flexible and adaptable. By being open to change and willing to adjust your schedule as needed, you can maintain momentum and keep your project on track. It's also important to communicate effectively with your team and stakeholders to ensure that everyone is on the same page and working towards the same goals. In the end, being flexible and adaptable can help you increase your productivity and achieve success.

![Be ready to re-route if needed](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/be-ready-to-re-route-if-needed.jpg)

**Pad your estimates**

Padding your schedule can help you account for unplanned tasks or activities that may arise. By allowing for extra time in your schedule, you can be more prepared for the unexpected and better able to adjust your plan as needed. It's important to be proactive and adaptable in order to maintain momentum and keep your project on track.

To determine how much extra padding to add, you may consider the knowns:unknowns:assumptions ratio, as those increase the risk of missing your schedule, I usually start at 20% and exchange padding over level of detail during negotiations. I use this rule when I'm asked to estimate a project of which I know 20% about.

---

### **Conclusion**

By setting clear goals, creating a schedule, accurately estimating your time, and being flexible, you can increase your productivity and ensure that your efforts are aligned with your overall objectives. However, effective communication is also key in this process.

In the next article, <a href="https://prodev.blog/posts/the-power-of-brevity--how-to-communicate-effectively">"The Power of Brevity: How to Communicate Effectively"</a>, we will dive deeper into the importance of clear and concise communication in achieving your goals.

<a href="https://medium.com/@dev.aaron.gh/" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

Part Three: Why setting SMART goals are important?

Learning to set SMART goals is important, as it can improve your time management skills to achieve efficient productivity.

Efficient and Productive, Top Time Management Strategies


Welcome to the second article in the series, "Navigating the Path to Seniority: A Guided Journey for Junior Engineers." In this article, we'll focus on the top five skills that every engineer needs to develop in order to advance in their field: time management, communication, leadership, problem-solving, and technical curiosity.

By consistently working on these skills, you'll be well-equipped to take on new challenges and responsibilities as you progress in your career. Let's dive in and explore each of these skills in more detail.

![A safety helmet near a toolbox](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a_safety_helmet_near_a_toolbox.jpg)

### Time management

Effective time management is crucial for handling complex projects with tight deadlines. To manage your time effectively and meet deadlines, you need to:

- [Set clear goals](https://medium.com/the-post-grad-survival-guide/a-complete-guide-to-goal-setting-a01ced9b6040)
- [Define a schedule](https://medium.com/@quasichad/how-to-create-a-schedule-that-will-actually-help-you-54e56397a87b)
- [Avoid distractions](https://medium.com/@quasichad/how-to-create-a-schedule-that-will-actually-help-you-54e56397a87b)
- [Learn to say no](https://www.heysigmund.com/how-to-say-no/)

[Here's an article](https://www.linkedin.com/pulse/i-took-ankoor-warikoos-time-management-course-so-you-dont-rall/) about one of the most popular [courses about time-management](https://webveda.ankurwarikoo.com/course/time-management).

In the next article in this series, ***“[Efficient and Productive: Top Time Management Strategies](https://prodev.blog/posts/efficient-and-productive-top-time-management-strategies)”***, we'll explore this fundamental skill in depth.

### ****Concise communication****

Concise communication is critical for conveying ideas and collaborating with others. By being brief and to-the-point, you can more effectively convey your ideas and be understood by others. This skill is especially important in situations with limited time or when you need to convey a lot of information quickly.

Quick tips for improving your concise communication skills:

- Practice [active listening](https://www.verywellmind.com/what-is-active-listening-3024343)
- [Use clear and concise language](https://www.youtube.com/watch?v=2OBewm5guJk)
- [Write well](http://chicago.iabc.com/2011/12/hemingways-4-rules-for-writing-well/)
- Seek feedback

In a future article, ***“[The Power of Brevity: How to Communicate Effectively](https://prodev.blog/posts/the-power-of-brevity--how-to-communicate-effectively)”***, we'll dive into this topic.

### Leadership

Leadership is an important skill to develop in engineering, even if you don't aspire to lead a team. Strong leaders are able to:

- [Take initiative](https://medium.com/mind-cafe/how-to-take-initiative-and-change-your-life-acc0464ac7b9)
- Communicate effectively
- Empower others
- Be open to feedback

These skills can help you take on more responsibility and lead projects or teams, but they can also be valuable in any role by enabling you to be proactive and influential within your team and organization.

In the article, ***"[Engineering Leadership: From Aspiring to Exceptional](https://prodev.blog/posts/engineering-leadership--from-aspiring-to-exceptional)"***, I will explore the importance of leadership in engineering and provide tips and strategies for developing your own leadership skills. Whether you aspire to be a team leader or simply want to be a more effective contributor to your team, this article will provide valuable insights and guidance.

### Problem-solving

To **[tackle complex challenges and find creative solutions](https://www.hashlabs.com/guides/en/methodology/X-Workflow.html)**, it's important to have strong problem-solving skills. This involves defining problems, generating potential solutions, evaluating those solutions, and implementing the best one.

Effective problem-solvers are able to think critically, analyze data, and make informed decisions. They are also able to break problems down into smaller pieces and approach them systematically.

To improve your problem-solving skills, try **[using different methods](https://hr.uiowa.edu/development/organizational-development/lean/8-step-problem-solving-process)** to approach problems, **[getting feedback](https://www.skillsacademy.co.za/using-feedback-to-improve-job-performance/)**, and **[practicing](https://uwaterloo.ca/centre-for-teaching-excellence/teaching-resources/teaching-tips/developing-assignments/cross-discipline-skills/teaching-problem-solving-skills)**.

In the future article, ***“[Solving Problems Like a Pro: Tips and Techniques](https://prodev.blog/posts/solving-problems-like-a-pro--tips-and-techniques)”***, we'll delve further into this topic.

### Technical curiosity

A curious engineer is an **innovative engineer**. To be curious means to have a **desire to learn and understand**, which is essential for staying current in an industry that is constantly changing.

Technical curiosity is not only about staying up to date with the latest technologies, but it's also about staying open to new ideas and approaches to problem-solving.

To cultivate your own technical curiosity, try **learning new technologies**, **[exploring new topics](https://www.learning-mind.com/learning-methods-for-problem-solving/)**, and **[asking questions](https://www.verywellmind.com/what-is-curiosity-2795868)**.

In the final article in this series, ***“[Inquiring Minds: How to Cultivate Technical Curiosity](https://prodev.blog/posts/inquiring-minds--how-to-cultivate-technical-curiosity)”***, we'll delve further into this topic.

---

### **Conclusion**

Developing the skills we'll cover in this series will help you navigate the path to seniority and succeed as a junior engineer. By consistently working on your time management, communication, leadership, problem-solving, and technical curiosity, you'll be well-equipped to take on new challenges and responsibilities as you progress in your career.

I hope this series has provided valuable insights and guidance for your journey to seniority. Stay tuned for the next articles in the series as we delve deeper into each of these important skills.

In the next article in this series, <a href="https://prodev.blog/posts/efficient-and-productive-top-time-management-strategies">***"Efficient and Productive: Top Time Management Strategies",***</a> we'll delve deeper into the importance of effective time management and provide tips and strategies for developing this fundamental skill. Whether you're just starting out in your career or are a seasoned professional, this article will provide valuable insights and guidance on how to improve your time management skills and increase your productivity.

<a href="https://medium.com/@dev.aaron.gh/navigating-the-path-to-seniority-breaking-through-the-skills-you-need-to-get-ahead-375f0f44be4f" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest!

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

Part Two: What professional skills to develop?

In this second article of the series, we explore the top five skills every engineer needs to develop in order to advance their career: time management, communication, leadership, problem-solving, and technical curiosity. By consistently working on these skills, you'll be well-equipped to take on new challenges and responsibilities as you progress in your career.

Breaking through, the skills you need to get ahead


![A photo of "a group of engineers in a raft"](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/a-group-of-engineers-in-a-raft.jpg)

Welcome to my series on helping junior engineers become successful senior professionals.

As an <a href="https://www.linkedin.com/in/fullstack-problem-solver/" target="_blank">engineering manager</a>, I've had the opportunity to see the challenges of trying to advance one's career. I've also seen the value that both junior and senior engineers bring to a team. 

For example, I remember working with an engineer who was determined to become an architect. They consistently sought out opportunities to take on more challenging projects, and within no more than a couple of years got promoted several times up to a senior position. Today, I'm proud to see how that person has become head of engineering. 🫡

This series will guide you to identify and develop the skills needed to become a senior engineer.


## First off: What is seniority?

There is no universal way to measure seniority, and it can vary depending on the company, industry, and role in question. However, there are a few common factors that are often used to measure seniority:

1. **Experience**: Time in field, number and complexity of projects are good representations.
2. **Expertise**: Ability to solve complex problems and design effective solutions.
3. **Responsibility**: Ability to handle several projects of distinct complexities.
4. **Recognition**: Awards or publications are good examples.

_Seniority is the measure of expertise and ability to handle complex responsibilities._

## Why does seniority matter?

It can bring benefits to your career, like *promotions*, higher **pay**, and the **opportunity** to take on more challenging projects. It's an important step to take in order to **advance** your career.

!["a raft sharing space with a drawing of a ship"](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/an_engineer_with_a_safety_helmet_in_from_of_a_raft_and_a_boat_and_a_ship.jpg)

Seniority is important for companies because it often brings a level of expertise and responsibility that can be valuable in tackling complex tasks and projects. Senior staff can provide guidance and mentorship to junior staff, and their experience can help inform decision-making and problem-solving.

Overall, having a strong senior staff can contribute to a company's overall efficiency and success.

## Do I have to become a senior?

It's important to note that pursuing seniority is not for everyone, and it's perfectly okay if it doesn't align with your interests.

Examples of why someone might choose not to pursue the seniority path:

- **Personal interests**: Some may be interested in other aspects of their job or career, and may not feel the need to pursue seniority.
- **Work-life balance**: Some may focus on work-life balance and not want to take on the extra responsibility that comes with more senior roles.
- **Career change**: Some may pursue a career change, and may not want to focus on advancing within a specific field.
- **Other priorities**: There may be other priorities, like family or hobbies that take precedence over advancing their career.

## What seniority is not

Here are a few common misconceptions about seniority that are worth noting:

### Time as the only factor

Seniority is sometimes equated with age, but it's vital to highlight that the two are not the same. 

I remember working with a young engineer who was fresh out of college, but he had already developed a level of expertise and responsibility that far surpassed many of his more senior colleagues. Despite his youth, he was frequently sought out for his technical expertise and was trusted to lead important projects. He was a great example of how seniority is not solely determined by age, but rather by a combination of factors including experience, expertise, responsibility, and recognition.

Someone who has worked in their field for a long time may not necessarily be more senior. For example, a developer who has spent their career working on a specific proprietary platform may not be considered a senior in the broader industry even if they have a lot of experience.

### Seniority as a one-time accomplishment

Seniority is something that can be continuously built upon. You can continue to develop and improve in your profession as you accumulate more experience and broaden your skill set.

### Seniority is only based on technical knowledge

While technical knowledge is unquestionably a crucial component of seniority, it is not the only one. Being a senior professional requires having strong communication, leadership, and problem-solving abilities.

!["advanced engineer in a ship"](https://prodev-blog-assets.s3.us-west-1.amazonaws.com/img/advanced_lead_engineer_with_white_helmet_in_a_ship.jpg)

## Ok I get it! so, how do I develop these skills?

To advance in your profession and take on more challenging duties, you must learn and grow your knowledge and skills *continuously*.

If you want to take the first step in becoming a senior and made it this far, **congratulations**! you're already on the right path!

The following posts in this series <a href="https://prodev.blog/posts/breaking-through--the-skills-you-need-to-get-ahead">"Breaking through, the skills you need to get ahead"</a> will explore in depth the skills you'll need to develop to become a senior professional.

<a href="https://medium.com/@dev.aaron.gh/navigating-the-path-to-seniority-a-course-for-success-6fc8a7ccaace" target="_blank">Let me know</a> if you liked this post (or not), and if you'd like me to post on a topic of your interest! 

**Next up**: *"[Breaking through, the skills you need to get ahead](https://prodev.blog/posts/breaking-through--the-skills-you-need-to-get-ahead)"*

<a href="https://medium.com/@dev.aaron.gh" target="_blank">**Follow me**</a> to get notified when I publish a new post. And thanks for reading! :)

In this series, we'll explore what seniority is, why it matters, and how junior engineers can develop the skills and expertise needed to become successful senior professionals.