We’ve all heard the age-old saying: putting the cart before the horse. Unfortunately, in the world of DevOps, this is happening far more often than it should, and it’s time we talk about it.

The crux of the issue is that, too often, the focus isn’t on solving actual problems; it’s on utilizing shiny new technologies. Picture this: A developer stumbles upon a cutting-edge piece of technology. They’re immediately enamored by its features, its capabilities, the way it’s touted as the ’next big thing.’ So, they start finding ways to incorporate it into their work, regardless of whether it’s actually the best fit for the problems at hand.

Nokia 8800 Sirocco#

This phone is a true classic. Known for its elegant stainless steel design and smooth sliding mechanism, the Nokia 8800 Sirocco was a fashion statement as much as it was a cell phone.

Nokia 8600 Luna#

The Nokia 8600 Luna dazzled users with its smoky glass exterior and illuminating keypad. It perfectly blended art with technology and gave us a taste of what a designer phone should look like.

Learning from your own experiences is priceless. We’ve all made our share of blunders, myself included. While sharing tales of our missteps might provide some comic relief, the real value lies in the lessons learned. You don’t forget a mistake when you’ve had to deal with its consequences.

Speaking from firsthand observation, it’s not uncommon for developers to roll out code live, often hastily, to meet pressing business deadlines. The urgency tends to outweigh any considerations for the potential havoc it could wreak on a production environment. These situations occur more often than you might think.

Why Programmers Want to Start Over

Have you ever felt the urge to scrap your code and rewrite it from scratch? If so, you’re not alone. Many programmers have this temptation, and there’s a hidden reason behind it. The reason is not that the old code is bad, but that it’s hard to understand. There’s a fundamental principle of programming that explains this: Reading code is harder than writing it. This is why reusing code is so challenging. This is why every developer on your team has their own favourite way of splitting strings into arrays. They create their own function because it’s more enjoyable and simpler than learning how the existing one works.

Many people wonder if college is a good investment for their future. They may have heard stories of graduates who struggle to find jobs or pay off their student loans. They may also have doubts about the quality and relevance of the education they receive in college. Is college really worth it?

The answer is not simple. College can be a valuable experience for some people, but it can also be an overinvestment for others. It depends on many factors, such as your personal goals, interests, skills, financial situation, and the labor market. College is not a guarantee of success, and it can also involve significant risks and costs.

Google came up with a new programming language called Go, which is supposed to be super fast and awesome and stuff.

But do we really need another language? I mean, come on. It’s hard enough to keep up with the ones we already have.

Go has some cool things going on, like goroutines, channels and interfaces. But it also has some weird things, like no generics, no exceptions and no inheritance. So it’s not for everyone.