3 ms·
Fully true, but how many times you will be able to justify that refactoring to the ones who asked ? Most of times, all they want in a "fast, small new importan
by gnoupi 17y ago
Fully true, but how many times you will be able to justify that refactoring to the ones who asked ?
Most of times, all they want in a "fast, small new important feature to put in a new menu item". It's hard to make them realize that because you add new features, most of times the dynamic of the UI has to be rethought.
And it ends usually in an application with countless menus and modes even for these menus. So redesign is important, but how do you justify to your marketing (or head programmer) that they have to "pay" for a redesign of what they "paid" already months ago, just for one feature ?
- megaduck 17y agoRefactoring doesn't have to be massive. Perhaps you can get by with a subtle tweak, so long as it's well thought out. Alternatively, if adding a feature demands a massive refactor, then it might be a warning signal that you've got some fundamental issues with your UI. In that case, it might be worth it to spend the time re-examining the core design of your app. You also might refuse to support that feature. Being able to say "no" is an important skill, both as a designer and a developer. Leaving stuff out is often as important as putting it in.