Common Acronyms Every Newbie in Software Engineering Should Know — Part 1

Mukul Bichkar on November 14, 2018

Ever since I started programming and even today whenever I read the documentation I come across many acronyms or jargons which are pretty common ... [Read Full]
markdown guide
 
 

Single responsibility principle
a class should have only a single responsibility (i.e. changes to only one part of the software's specification should be able to affect the specification of the class).
Open/closed principle
"software entities … should be open for extension, but closed for modification."
Liskov substitution principle
"objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program." See also design by contract.
Interface segregation principle
"many client-specific interfaces are better than one general-purpose interface."
Dependency inversion principle

 

I wonder if you could guess somebody's age from the acronyms they know.
:)

There's no reason to know what FTP means anymore. It's an outdated insecure standard. Things like ssh-fs and https have replaced it.

The CLOB/LOB stuff is also highly relational DB biased. Do non-relational DBs have similar terms? That is, I'm not sure these terms are helpful to a newbie as you can build modern systems and never encounter them.

WYSIWYG seems dated now in the world of adaptive and responsive designs. What you see is never what you get anymore. I refer to things as just editors, visual editors, or source editors.

 

Very good summary! Thanks for that :) Minor correction: afaik CLI means Command Line Interface, not Interpreter.🤓

 

Very, very, very useful article/reference. Thank you for this. I only knew more or less half of the terms here. Glad to learn something new today.

 

GRASP - General Responsibility Assignment Software Patterns

 
 
code of conduct - report abuse