Everything should start with a SOLID plan, not just influenced by the enthusiasm of a successful PoC, briefly tested and blessed/approved by the management where the implementation challenges are hidden in plain sight!
I wanted to write this article since I’ve started scriptinglibrary.com, but I will try to keep this article to a technical level where you can enjoy the first experience and avoid bad ones. Otherwise, you’ll find yourself overwhelmed or lost into the number of services and the possibilities offered by cloud computing. Continue reading “Cloud Tools for Azure: Powershell, Azure CLI, Azure Cloud Shell”
As a DevOps with work experiences as a Developer and System Engineer, I tend to give for granted that all my colleagues or peers have the same background knowledge or simply the same vocabulary.
But I’ve recently discussed with some seasoned sysadmins working for other companies and I was surprised to discover the barrier was around the vocabulary and the design principles (for developers or system engineers) used as a reference point.
Naturally, we try to solve problems with solutions or technologies that we already used in the past, without exploring all the possibilities. Sometimes we simply don’t get some context or benefits of doing it differently or we can’t measure how expensive can be the adoption of different models or strategies.
For instance: Microservices, RESTfulAPI, Webhooks are common terms that most of us are comfortable using every day, but these design implementations and functions are sometimes not so simple to break it down into small independent pieces. Continue reading “How to trigger incoming webhooks in Microsoft Teams with Powershell”