5 Bad Software Engineering Habits You Didn’t Know Were Bad (Until Now)
Are you falling victim to these bad habits?
As Software Engineers, we try our best to deliver high-quality code, but some of our daily actions cause more harm than good.
Try to avoid these five bad habits.
1. Setting up too many alerts in production
Alerts let us know when issues occur and often before the customer realizes them.
Alerts are powerful. They build trust in our systems. When first used, we start adding an alert for mission-critical features. It saves our backs, so we add more.
And before you know it, every logged exception has an alert tied to it.
The end result is not as desired.
What was once a team of engineers jumping on to every red alert like the charging bulls of Pamplona in July. Turns into a team who are so numb to a sea of red alerts, they are not sure what’s real anymore.
When everything is an alert, nothing is an alert.
The solution
Use alerts sparingly.
You can avoid alert fatigue by:
- Only add alerts for mission-critical features
