Chronic Blogger

To refactor or not to refactor..

That is the question.

Finding the right balance between refactoring existing code and delivering business requirements is never easy. This is especially true when you keep finding code that should be refactored. I'm not one to complain (aw who am I kidding ahha) but I don't like having to live with code that's not readable and hence hard to maintain. But how can one spend enough time refactoring code when there are so many other business requirements to deliver at the same time. It becomes a question of 'how much pain will this cost us' and 'how much benefit can we get out of refactoring this' *sigh*.

I don't like taking the easy way out all the time at the expense of sacrificing code quality. Sure, the app might work now, but when (and it's really just a matter of time) bugs are found, oh woe is me if I ever have to investigate and fix them. If I need to spend hours looking at code just to understand what's going on, I get stressed and annoyed.

It hurts.

It really does.

posted by chronicblogger @ 12:39 AM