There are two main ideas behind this article: `security` and `mobility`
Depend in the direction of abstraction. High level modules should not depend upon low level details.
Clients should not be forced to depend upon interfaces that they do not use.
Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
A software module (class or method) should be open for extension but closed for modification.
A class should have only a single responsibility (i.e. only one potential change in the software’s specification should be able to affect the specification of the class)
Overview I once did an automated script for a reformatted Word document. Opening the word file and editing it is the interesting part, which is not very easy, but I found a useful python library. There is a nice book Python Programming On Win32, which I recommend to read. That is why I decided to choose python as my main language.
Overview In this article I would like to give some good examples of azure pipeline features that can be difficult to implement for the first time and are very often used in many other variants.
Overview Nowadays, with multiple environments and many developers involved in a single project, it is difficult to properly test everything at a high level. Unit or any small tests are easy to run everywhere nowadays, on a local machine, in the cloud, in the pipeline, etc. But what happens when I want to test some complex functionality or dependencies.