jeudi 3 mai 2018

Which antipattern is this?

A new phone appears on the market that requires substantial changes in UIs. An engineering team decides to update their UI by singling out just one button that needs to be moved based on the new phone's dimensions and shape. They shift the button it up n pixels in every screen of an app, but only for that device, rather than thinking of the essential problem or larger issues. What antipattern is that? (Please don't refer to psychological causes e.g. stupidity or laziness.)

Some might praise them for following open/closed principle and refusing to refactor and rewrite, but open/closed isn't meant to lead to bad code.

Others might say, this is OK design because it's kaizen; but a little nip or tuck here or there repeatedly over time leads to... a mess.

Aucun commentaire:

Enregistrer un commentaire