How to make your more experienced and authoritative teammates not to create 'fast temporary solution

Posted by Roman on Stack Overflow See other posts from Stack Overflow or by Roman
Published on 2010-03-27T18:22:37Z Indexed on 2010/03/27 18:23 UTC
Read the original article Hit count: 144

Filed under:
|

I'm currently working on a small short-lived project. But despite the size it's complicated enough with very unclear logic. That's why it was started by more experienced developers. They work on it from time to time because it's not their main project.

They made some code drafts with numerous places which 'would be rewritten in the nearest future'. After that they added several another 'temporary pieces'. And then again..

So, now the project is a mess of 'half-working' pieces of code with some hardcoded values, like file names or some constants which 'will be replaced latter with working parts'. The API is awful (nobody thinks about it actually).

And it's really, really hard to do development now (for me it's the main and only project). I caught myself thinking that I spent about an hour every day just to understand again all that tricky 'temporary' things and API weaknesses. And after that hour my brain melts.

I can't just say that "guys, your code smells like a trash dump". What's the correct way?

© Stack Overflow or respective owner

Related posts about Development

Related posts about teamwork