CodeVault
Logo picture

Latest articles

3 GIT productivity features explained

I know there are some people in the community that use GIT on a day-to-day basis...

5 helpful features in Chrome's DevTools

Chrome's DevTools (and its Firefox counterpart) is undoubtedly one of the most used debugging platforms...

Failing code | Part 3

Now, the last rule is more prevalent to interpreted languages than compiled ones but here it is:

Failing code | Part 2

Another problem when treating errors is that we sometimes forget to return an invalid return value. Let's check out the second rule regarding this:

Failing code | Part 1

Let's start simple. You have a method that, sometimes, when called with certain arguments or at certain times it might fail. How do we tell that to the user? What about to the programmer using that method?

Comment-pocalypse | Part 2

The next method of commenting, we surprisingly saw a lot of in the industry, is section commenting. It starts simple, with a question asked but almost any programmer after a bit of experience:

Comment-pocalypse | Part 1

There are quite a few conventions when it comes to commenting your code. Let's break them down and see how good/bad they are.

Invert your if statements!

Here's a practical solution that can be applied at any moment in development you want with doing these simple steps until there are no longer any exception cases nesting the main code.

Get notified when a blog post is released

+ Free Clean Coding Guide