[gus_massa]

For context: When has the project started? When did most of your team come together? When did you enter the team? How many working experience do you have?

Most of your ideas are right, but in real world sometimes you need to make exceptions. For example sometimes you must add a special case. It makes the code worst, but sometimes something has to get fixed now and cleaned after.

I recommend you to read: "Getting Things Done When You're Only a Grunt": http://www.joelonsoftware.com/articles/fog0000000332.html (don't forget strategy 6)

[ThrowawayCoward]

The rewrite started a year ago. It's the _fifth_ version of the same product that is only four years old. I joined this project about a month ago, but have been working on a related project and interacting with them for about three years.

I agree that sometimes things have to be fixed now and cleaned later, but it should make you feel a little bit queasy when you do it, and you should be aware that you are adding future work to the project.

I skimmed that link and it looks great, I'll be diving in fully. Since I've seen the posts from others and was leaning that way already, it's likely I won't send it, but I really want to push this project to be better. Since you suggested strategy 6, I read that first, and it's awesome and difficult. Part of being new means that more than a usual amount of my development time is spent understanding the project. I've felt rather unproductive because of this.

Thank you.