Release engineering is one of those roles I didn't even know existed. But when the opportunity came to join the release team in my company I took it without thinking much about it. 💡Pro tip: Always think before making career moves. Later on, I figured it would be
Imagine this, it's a Tuesday, you've just finished developing a feature, it passed all the checks, and you're ready to deploy. You merge the changes, and soon after you notice that the deployment to two servers succeeds, but the third fails. This isn'
These days, developers have a lot of cognitive load. You’re not just writing code, you’re playing around with cloud providers, troubleshooting Kubernetes, managing observability tools, making sure that your software is compliant with security best practices, and so much more… It’s not only you. It’s everyone
A lot of software engineers forget why their software is successful. (or why it's not). The #1 reason is that your customers love your software. But making good software is hard, the stars must align. Things such as tech, product, marketing, and sales all come together. On the
Load balancing is the process of distributing network traffic equally over a set of resources that support an application. Modern applications must process millions of users simultaneously and return the correct data in a fast and reliable way. To do that we distribute the network traffic equally which will result
Back at it again, this week we will cover chapter 9 of the book titled "I can't get this class into a test harness". Sometimes it's just hard. But if it were easy then everyone would do it!! Okay, I'm sorry that
In legacy code, one of the most important considerations is that we don't have tests around much of our code. What's worse, is that getting them in place is difficult. That's why many people are tempted to go back to the techniques we learned
How long does it take for you to make a change? If I ask this to 100 different people, I will get 100 different answers. The answer varies widely. So in projects with unclear code, many changes take a long time. On the other hand, in clearer areas, this can
You might ask me? Is doing all this additional work worth it? Do I need to test all my code? Do I need to break all these dependencies? You might be wondering whether it’s worth doing these things right now. The truth is, the work that you do to
When people first start writing tests, they will notice how horrible code is structured for them. In general, this is true most of the time, except when you write tests along with the code which is called Test Driven Development. I personally think it's a thing that every
Back at it again, this week we will cover chapter 9 of the book titled "I can't get this class into a test harness". Sometimes it's just hard. But if it were easy then everyone would do it!! Okay, I'm sorry that
In legacy code, one of the most important considerations is that we don't have tests around much of our code. What's worse, is that getting them in place is difficult. That's why many people are tempted to go back to the techniques we learned
How long does it take for you to make a change? If I ask this to 100 different people, I will get 100 different answers. The answer varies widely. So in projects with unclear code, many changes take a long time. On the other hand, in clearer areas, this can
You might ask me? Is doing all this additional work worth it? Do I need to test all my code? Do I need to break all these dependencies? You might be wondering whether it’s worth doing these things right now. The truth is, the work that you do to
When people first start writing tests, they will notice how horrible code is structured for them. In general, this is true most of the time, except when you write tests along with the code which is called Test Driven Development. I personally think it's a thing that every