Today, most of our lives tend to focus around our jobs and our all-important relationships with our employers. After all, your employer hires you, pays for your working environment, sponsors the fun corporate events, and even provides the table for playing tennis. We should accept that our employers have all the power in this relationship, right?
When writing code, you will make the same mistakes again and again. Some of them can be quite minor, while others could lead to really expensive consequences. I am going to list the most common of these mistakes below, in no particular order. Next time you work on a new feature, make sure you won’t fall into any of these traps. And please notify me, if I do.
Your friend Joyce from another country wants you to have a video call at 20.**.2017 12:00. Will you join?
Whether you are writing your own unit tests or reviewing ones written by someone else, you can easily assess their quality by the shape of the test methods. You don't even need to read them.
Imagine yourself riding a bicycle where all the screw-nuts are loosened. Everything is rattling and the bike is ready to fall apart. This is exactly how it feels to maintain code when this essential keyword we are going to discuss is not used or is used only sparingly for some class fields and constants.
The short answer is both. Let me explain.