Functions that use pointers of references to base classes must be able to use objects of derived classes without knowing it.
This principle states that, if S is a subtype of T, then objects of type T should be replaced with the objects of type S.
“Ability to replace any instance of a parent class with an instance of one of its child classes without negative side effects”
This means that in a block of code an instance created by a child class can replace a parent instance and the result should be the same as when using the parent class.
For example, the father is a teacher whereas his son is a doctor. So here, in this case, the son can’t simply replace his father even though both belong to the same family. …
There are no limits to the things that you can create when you have the ability to write code. You can automate manual tasks, make things faster and easier for users, or solve almost any problem. It gives you the ability to create something that you can be proud of. This means you can finally combine your love of programming with your love of cold hard cash.
Technology is only becoming more and more a part of everyday life.
And the best part about all this is that the sweet thing we call the World Wide Web has opened up new possibilities for programmers to find work. …
You should be able to extend the behavior of a system without having to modify that system.
Think about that very carefully. If the behaviors of all the modules in your system could be extended, without modifying them, then you could add new features to that system without modifying any old code. The features would be added solely by writing new code.
What’s more, since none of the old code had changed, it would not need to be recompiled, and therefore it would not need to be redeployed. …
Every module or class should have responsibility for a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class, module, or function.
A class should have one and only one reason to change, meaning that a class should have only one job.
Serverless is currently a trending topic which will definitely be a major hit within the next few years. In the future, you won’t have to worry about the infrastructure, as your complete software life cycle will depend on cloud service providers.
Initially, the definition of serverless architecture was limited to applications that are dependent on third-party services in the cloud. These 3rd party apps or services would manage server-side logic and state. Alongside a related term — Mobile backend as a service (MBaaS) also became popular. …