All articles
Software Development1 min read

8. DNtUA (Do Not Use Abbreviations)

The deliberately unreadable, abbreviation-stuffed short version of "Do Not Use Abbreviations" — proving its own point one cryptic acronym at a time.

Delft-blue tile reading "DNtUA"

Abbrs R v.pop in SW dev. B4, this was a req: mem ↓, BW 💸, langs like FTN only let U use varNms ≤6ch. So ppl came up w/ brvs like i18n (intlzn) & a11y (accsblty).

Now? Thx 2 mod langs (e.g. TS, JS, PY) & tools like min, TShk & gzcp, we can use descNmz W/O perf hit. So, rly, no need 2 go full YOLO on abbrs.

But devs still ❤️ shrtNms. OK 4 std ones (id, UI, API, fn, ctx, err), but probs start when ppl use rand abbrs like e (evt? err?), dR (dataResp? deleteReq?), or sM (stateMgr? setModal? snackMachine??). It's chaos.

Hence this wk's DTOW:

🧱 DNtUA

If U must use abbrs (e.g. client reqs, legacyCtx, OCD), put a ✨LUYA✨ (Lookup U'r Abbreviations) section in README.md. Helps U, YOLOdev, & all FDEs in 2y trying 2 🐛ur code.

🧠 Part of the wkly DTOW series: TL;DRs 4 FEs, TLs & HCDs 🧑‍💻.

💬 Agree? Disagr? Drop ur 🤔 in the 🧵.

💼 Need a TL who can turn messy projX into clean, doc'd FE_sys? HMU.

Related articles