Developers often face situations where logic bends. Now this happens quite a few times. Suppose we have an equation with factors that the outcome of this equation is the “bending logic”.
The first factor, and larger at times is the client input. “Yes, we know we asked for that, but now things have changed, so we have to change it” , “What? I did not ask for a red line drawn with a blue pen!” and so on. More on that at The Expert.
The second factor is the programming language we are using. And that is the point were we stand for now. Third and fourth factors is experience and capability but those are irrelevant on each person so, we wont be discussing them now.
ANGER. WRITING CODE THAT SEEMS TO WORK.
Quite recently I stumbled upon this interesting site :
Turns out that this guy: @abestanway is parsing repos from github and records each curse in the commit log message. A commit log message is a message we developers use when we are completing a project/code snippet/change/bug in the code of a system we are using.
This guy, took it to another step also. He gathered data and created a presentation, showing the languages with the most curses. He even created graphs of the most cursed and least cursed language:
He also created graphs with the most used curses:
Next, he compared the Most Cursed languages with the most used languages in Github. You can have a look at all the above from the relevant video :
To conclude he points out that the more the curses, the better the code…