Definitions in programming (principles)
What are different principles in Programming?
Principles in programming are often higher level concepts which are often design decisions or ways of how to program and less about a specific thing.
Why are they relevant?
Principles in programming are relevant because they keep things organized when people adhere to them. You wouldn't want 10 different charging port types your phone could have, no? (Unifying and having specific requirements for something to be held to a standard is what standardization is about)
How are they executed in different programming languages?
Principles can be more prominent in one programming language than it is in another. Some might prioritize keeping things more readable, others focus more on speed. Though more universal things are standardization or modularization are often to be found because it makes working with a programming language(especially setup and general usability of their ecosystem) easier.
Terms about how to program (paridigms)
A programming paradigm is the way you write code. The following terms are different ways to write code. Be aware that not every programming language supports every way of writing code.
Introduction to the programming world
OOP(Object Oriented Programming)
Object Oriented Programming works - as its name might suggest - with objects.Concepts like encapsulation, inheritance as well as polymorphism play a crucial role in this programming paradigm.
Capsulation
Capsulation means having the dependencies and requirements of a specific thing in a seperate area rather than having everything in the main part of an application for example.
Module A (dependencies and requirements) is part of the big program M with its own dependencies+requirements.
Modularization
Modularization often goes hand in hand with capsulation. You outsource specific functionality to specified parts.
For example part A handles user input, part B handles payment processing and part C takes care of logging your inventory.
The goal with modularization is a seemless integration with the core application without overloading with unnecessary functionality right from the start. It also helps identifying problems as you can pinpoint them more easily.
Readability
Readability is often key for how easy a programming language is to pick up. The worst example for this would be the language brainfuck while the best one would be Python.
Python stands out in readability because of its close resemblance to the English language(which is a pretty universal language).
But not only resemblance to real-world languages makes a programming language readable, it's also the volume of the code needed to achieve a specific result. The more lines you have to write, the more you're prone to making a mistake.
Standardization
Even though standardization isn't always enforced through syntax, it's often wise to adhere to the norms agreed upon by the community (online or in your workspace) when writing code.
While hard standardization means a rule is essential to write syntactically correct code, soft standardization like naming conventions are more about professionality and goodwill.
For example when everyone adhears to a naming scheme for certain things, it will be easier to differentiate stuff from each other without having to go into detail.
Note that you'll often have different soft standardization, especially regarding things like naming schemes depending on your workplace where you'll have to adhere to standards not set by a broad community but rather locally.
--> It's best to be adaptable and act based upon the informations you receive from your surroundings regarding soft standardization. Especially if you collaborate!
