2 ms·
> This often manifests as developers or entire teams that can’t stop rewriting, refactoring, and rearchitecting code that is already good enough. We got tons o
by magicalhippo 5y ago
> This often manifests as developers or entire teams that can’t stop rewriting, refactoring, and rearchitecting code that is already good enough.
We got tons of code that I'd love to rewrite or refactor. But it works. Has done for 15 years and will continue to. Instead I can fix proper bugs and add new features.
Sure if the old mess is standing in the way of delivering something important I will do something about it. But not until then, we just tweak it when needed and that's it.
- handrous 5y agoUnfortunately, it's common to get "stakeholders" involved who want to "approve the design" before a feature's green-lit, as in, exactly what's going to be built, or at least very close. Because they're "important" so they must know software UI design better than the UX experts, designers, and developers they've hired. "No no no, this delete icon must be a red X, even though that could easily be mistaken for 'close' in this context, and I will fight you for weeks to make sure it happens". They don't like wireframes or deliberately-rough mockups. Or you get branding lunatics involved who aren't able to produce and provide visual-design guidelines that they trust well enough not to need to stick their nose into every project to make sure the button corner radius is "on-brand" and can't ever let a design pass without some kind of tweak, because that means they're doing work, I guess.