I would take your point forward and say if the code is hard too read then is it shit.
There is a reason that you are reading it: you are maintaining it, adding a feature or trying to fix a bug. If it is not easy to read then it makes this harder and that makes code bad and increases the chances of the editor making a mistake and breaking the system. (Or just making your day bad).
For those of you who were commenting and looking for a local only timetracking , I have a git plugin that supports Redmine timetracking, and is git friendly. Also, works for gitbranches and git repos, tracks by repo/by branch or annotated tag - does some other stuff - got to stop adding random features.
three projects: Homenet a closed source home networking system, multimedia, it's own TV stack. Currently re-writing as i thought the networking was a bit weak, and the android remote control/EPG was UGLY!
There is a reason that you are reading it: you are maintaining it, adding a feature or trying to fix a bug. If it is not easy to read then it makes this harder and that makes code bad and increases the chances of the editor making a mistake and breaking the system. (Or just making your day bad).