3 ms·

It's a tradeoff. I love projects where I can "sweat the details" and refine not just wording but typography, padding, visual alignment, layout, edge cases, col

It's a tradeoff. I love projects where I can "sweat the details" and refine not just wording but typography, padding, visual alignment, layout, edge cases, colors, workflow, etc. And where the back-end, QA, doc teams are similarly able to hone their work to perfection. But I know that this isn't always Pareto optimal. Sometimes your user, customer, and business are better off if you swallow your pride and deliver an imperfect solution now instead of a better solution in the future, and knowing when and where to strike that balance is a sign of maturity, not disrespect.

ungreased0675 11mo ago
As a software product manager, UX is one of the areas I’m inclined to spend more time and money than strictly necessary. Details and polish matter. Users can tell the difference, even if it’s subconsciously.
- angiolillo 11mo ago
  Totally: users can absolutely tell the difference and details and polish absolutely matter, but so does shipping the product. As a UX designer I'm always happy to have more time/money to spend on usability testing and refining ever more granular details in workflows and UI. But I'm also grateful for the wise product managers I've collaborated with who know where to draw the line to make sure we don't end up losing out to our "worse is better" competitors.
ctxc 11mo ago
Agreed! But I suspect several of these decisions are not intentionally made and are "...meh, whatever".
- angiolillo 11mo ago
  Fair enough, and honestly I agree with you that supporting the n==1 case is the bare minimum of care I'd expect from an application developer. Though if you support languages other than English even the decision to simplify pluralization logic to n==1 seems like a form of "...meh, whatever" given various pluralization rules: https://cldr.unicode.org/index/cldr-spec/plural-rules https://cldr.unicode.org/index/cldr-spec/plural-rules
  - ctxc 11mo ago
    The best approach is to probably separate the number out I guess. Files deleted: {0 or 1 or 1,000,000}
    - angiolillo 11mo ago
      That's certainly the approach our translation team prefers! Assembling a grammatically-correct statement from multiple discrete tokens is hard in languages with grammatical gender, complex pluralization rules, word ordering, etc. And there's not much benefit of doing it halfway right.

ungreased0675 11mo ago

As a software product manager, UX is one of the areas I’m inclined to spend more time and money than strictly necessary. Details and polish matter. Users can tell the difference, even if it’s subconsciously.

angiolillo 11mo ago
Totally: users can absolutely tell the difference and details and polish absolutely matter, but so does shipping the product. As a UX designer I'm always happy to have more time/money to spend on usability testing and refining ever more granular details in workflows and UI. But I'm also grateful for the wise product managers I've collaborated with who know where to draw the line to make sure we don't end up losing out to our "worse is better" competitors.

ctxc 11mo ago

Agreed! But I suspect several of these decisions are not intentionally made and are "...meh, whatever".

angiolillo 11mo ago
Fair enough, and honestly I agree with you that supporting the n==1 case is the bare minimum of care I'd expect from an application developer. Though if you support languages other than English even the decision to simplify pluralization logic to n==1 seems like a form of "...meh, whatever" given various pluralization rules: https://cldr.unicode.org/index/cldr-spec/plural-rules https://cldr.unicode.org/index/cldr-spec/plural-rules
- ctxc 11mo ago
  The best approach is to probably separate the number out I guess. Files deleted: {0 or 1 or 1,000,000}
  - angiolillo 11mo ago
    That's certainly the approach our translation team prefers! Assembling a grammatically-correct statement from multiple discrete tokens is hard in languages with grammatical gender, complex pluralization rules, word ordering, etc. And there's not much benefit of doing it halfway right.