@khalidabuhakmeh@mastodon.social
2026-03-18 19:30 UTC
Replies (6)
-
@tornhoof@hachyderm.io 2026-03-18 19:45
@khalidabuhakmeh@mastodon.social otp is fine, it's the normal abbreviation, minNum and stuff depends on context, would likely prefer MinNumber or similar
-
@david@social.colormixed.de 2026-03-18 19:47
@khalidabuhakmeh@mastodon.social Technical abbreviations are fine (for me). If they describe domain terms, I think it's harder.
-
@svelmoe@hachyderm.io 2026-03-18 20:24
@khalidabuhakmeh@mastodon.social random or homemade acronyms are always hard, regardless of language. Domain specific are easier if family with the domain, and common English ones are totally fine.
-
@jan-v.nl@bsky.brid.gy 2026-03-18 20:41
Even for texts in my native language I prefer fully spelled out words over abbreviations. It drives clarity.
-
@macf00bar@hachyderm.io 2026-03-18 20:45
@khalidabuhakmeh@mastodon.social even after living abroad and getting so used to english that I was dreaming in it, I still think acronyms are overused. If need be, at least include a glossary.
-
@DaveMasonDotMe@mastodon.social 2026-03-19 00:55
@khalidabuhakmeh@mastodon.social Oh, man. This post... I code review database-related deployments: stored procs, views, table designs, etc. I've been evangelizing *not* using acronyms and abbreviations when naming things. I'm constantly telling folks "This isn't the 90's. We're not bound by things like 8.3 file names. Spell out the words!"