Top 5 DEV Comments of the Past Week

I rediscovered my love of coding again!
I've been struggling with burn-out for a couple of years now, ever since I was forced to give up coding professionally for health reasons. I started developing a few java games for android but, after a succession of failed projects, I came very close to giving up completely.
Two weeks ago, a friend suggested a do some messing around with C++, a language I haven't used since the early 1990s! I'll admit it's a challenge as I haven't used pointers etc for a very long time, but I am officially hooked!

You. Are. So. Good. At. CSS!

But you didn't include this loader:

This week our entire build process went down because of a dependency of a dependency of a dependency, and I learned just how much of a house of cards npm is. Luckily, I can count that experience as a win because I was able to get in touch with that dependency's maintainer, send him as much info as I could about the error I (and by now some other people) were seeing, and he got a fix out within a couple of hours. It felt great to contribute to someone else's OSS project and help fix a bug that could have potentially derailed a ton of other apps like mine.

...there's probably a blog post about that I could write :)

My current title is the lofty "Lead Software Engineer" and I can say that these items all apply to me as well, especially that last one. To me, the difference between the Junior and Senior engineers is almost exclusively non-technical in nature. There are a few practices that make a difference in terms of performance, and reducing errors, but for the most part Senior-developership is matter of leading, encouraging, and supporting. It's all the meta-work around software development.

Here is a tip for avoiding unexpected bills from AWS. Always make a budget and take action according to it. i.e You can make a budget of 5$ per month and after the threshold reach, you can easily trigger some actions like stopping services or receive notiifications.