Messy Code - To refactor or not to refactor
 

I'm in a sticky situation right now,

A new project I took on recently has some really, really bad code.. which is saying something since this is only html.

There is so much mess it would take me about a week to completely refactor the webpage from the ground up.

The other option is to add to the messy code - and make it even more messier.


I know it's bad practice to add to bad code but if i have to refactor the code I'll probably loose my client..

Is it acceptable to add patches to the code to band-aid the situation and later on refactor the site when I have time?

Re: Messy Code - To refactor or not to refactor
 

It's up to your client. You work for them, so you can explain the situation. They pay you, so if they don't want you to refactor, you shouldn't. When I disagree with my boss/client/teacher, I mention in the comments what I intended to do. That way, the next programmer doesn't think ill of me. In the end though, the client decides the best use of their money.

Re: Messy Code - To refactor or not to refactor
 

If you're going to lose your client over a weeks worth of work, lose him. Next time pick a client who wants good work, not one who wants to pay you less than a McDonald's burger-flipper.

Re: Messy Code - To refactor or not to refactor
 

Refactoring is a good thing; get into the use of it.

Re: Messy Code - To refactor or not to refactor
 

I took DaWei's advice and detailed the problem I had, they didn't want to hear about it so I've ditched them.

Probably better off I dropped them anyway.

Thanks for the help.