Possible Duplicate:
How to tell your boss that his programming style is really bad?
There was a question about the boss having a bad programming style (weird booleans, empty loops, etc.) Having a bad/weird style does not imply being a bad programmer, but my situation is different.
My boss outputs some really nasty code for the project, on which we are working together (just two of us). Examples:
functions that span over several screens (big screens - 1900 x 1200)
Deeply nested Conditional and Loop statements (up to 10 levels!!)
Too much static variables, singletons, and both (singleton class with all the methods and members also static)
Sometimes the code committed to the version control system does not even compile!
Copy-Paste code instead of separating it into an independent function.
Fail all the deadlines.
"This's [C#|Java|Python] it shouldn't be efficient, that's why we loop all over the haystack to find the needle."
"This's C/C++, it's fast enough to loop all over the haystack to find the needle."
There is much more to mention... But the worst is that I have to redo much of the stuff he does, my code, which I try to keep clean is often polluted with above-mentioned atrocities.
He's reaching 30 soon, so all his skills are established, and I don't even know if it's possible to change something.
I like the project, but sometimes I just want to quit...
