Ask HN: What are the best acronyms that programmers should know?
28 comments
API [0] - application programming interface
- not often explained when learning programming, but essential
- [0] https://www.robinwieruch.de/what-is-an-api-javascript/
- not often explained when learning programming, but essential
- [0] https://www.robinwieruch.de/what-is-an-api-javascript/
KISS: Keep it simple stupid
Looking for acronyms is a waste of time, let alone save you time. Just make enough mistakes fast enough to learn from them. And Let The Acronyms Be Alone. ALTABA.
PEMDAS
Mathematical order of operations.
Parenthesis, exponent, multiply, divide, add, subtract.
I only learnt this a year ago and it's almost embarrassing how much my maths or ability to understand math has improved from this(I'm 28 and never gotten taught this in schools general maths so I used to find math really difficult).
To complete the picture, you might've been taught a completely different mnemonic in other countries. The one I was taught was BODMAS ( "B"rackets, "O"f or "O"rder, "D"ivision, "M"ultiplication, "A"ddition and "S"ubtraction) and some African countries teach this as BIDMAS [0]. Caused a lot of confusion when I came to the US and drew a blank when someone mentioned PEMDAS in an example.
[0]: https://en.wikipedia.org/wiki/Order_of_operations#Mnemonics
[0]: https://en.wikipedia.org/wiki/Order_of_operations#Mnemonics
[deleted]
How come it was never taught?
Definitely SOLID
https://en.wikipedia.org/wiki/SOLID_(object-oriented_design)
It contains: - SRP - OCP - LSP - ISP - DIP
It contains: - SRP - OCP - LSP - ISP - DIP
CRUD - create read update delete
ACID - atomicity, consistency, isolation, durability
RTFM
LGTM, SGTM. Looks, Sounds good to me.
WIP. Work in progress.
Pebcak is the only one you need
CAP
Consistency Availability Performance. At scale, pick any two.
Consistency Availability Performance. At scale, pick any two.
"P" is for partition tolerance.
Partition tolerance?
Yeah, it just means that you can distribute the system across a cluster. Since we only talk about the CAP theorem in the context of distributed systems, you have to assume "P" has already been chosen. So the theorem is really about a trade-off between "C" and "A".
FUBAR, WTF, SOL, SSDD, STFU, FML
WET - Write Everything Twice
NDA 83(b) IPO AMT
REPL, SOLID, DRY, CQRS
The various stack acronyms such as LAMP and MEAN.
TLA
DRY
What else should I be liberally referring to as I try to improve my practices?