Software development is not just a profession; it’s an art, a science, and a journey. At different stages of this journey, we find ourselves with varying levels of expertise and problem-solving skills. A frequent question that comes up is, what sets a senior developer apart from a middle-level developer? The answer may surprise you: It’s less about the code you write and more about the problems you solve. Defining Roles Middle Developers: Generally, middle developers are proficient in coding and can build features, fix bugs, and understand the project at a reasonable depth.

Multitasking is a common practice in today’s world. We are constantly bombarded with information and stimuli, and it can seem like the only way to keep up is to do more than one thing at a time. However, research has shown that multitasking is actually less productive than focusing on one task at a time. When we multitask, our brains have to constantly switch gears between tasks. This takes time and effort, and it can lead to errors and mistakes.

Today my colleague shared that they started to use RFCs inside of their development team. I was surprised in a way that I thought “why it’s not a common practice?”. I know that it’s not a common practice because I never used it in my previous companies. But I think it’s a good practice and I want to share it with you. What is RFC? RFC stands for Request for Comments.

How it started My PhD journey started in 2022. I was working full-time as a software engineer and I was doing my masters part-time. The masters journey was challanging but doable, and I finished cum laude. So I started to talk with other PhD students, why they are doing it, how they do it, etc. Appeared, that everyone has their own reasons and their own way of doing it. The main reasons for my peers were the interest in the topic and the desire to learn more about the topic.