Bjarne closes with the assertion that clean code does one thing well. It is no accident that there are so many principles of software design that can be boiled down to this simple admonition. Writer after writer has tried to communicate this thought. Bad code tries to do too much, it has muddled intent and ambiguity of purpose. Clean code is focused. Each function, each class, each module exposes a single-minded attitude that remains entirely undistracted, and unpolluted, by the surrounding details.
PS: Emphasis mine
A little offtopic, but: Columbia? WTF? The name of my fucking country is Colombia! with an O
Yeah! recently I'm interested on trying to help KDE, which btw is my preferred desktop environment on Linux, by the way of coding.
When I found that pages that you share which talks about going to IRC I said: WTF?
They should have some basic guidance page where they tell you what its needed to make code contributions to KDE:
all of this explained to the different distros on which KDE works
but going to a fsckn IRC is not a valid nor useful resource to the newbies trying to made some contributions
Say "twenty-three-skiddoo" to logout.