Skip to main content


Showing posts from 2018

Not Robots, software

This is a non-technical blog post I felt like writing. Main focus will be the change being driven by the tremendous technological advances the last 5-10 years. The inspiration of this writing is mostly derived from a talk by Technical Fellow Jeffery Snower called “Software development in an age of social responsibility” (it is available on youtube) and my ever curious mind. Executive summary If you think the technological changes are moving fast, you are in for a surprise. It will accelerate exponentially as the  4 th  industrial revolution gains momentum. How will you adapt to the change and what are the things you should think about to avoid extinction for your business? Software is eating businesses and the world and if you think that software does not apply to your organization, you might want to rethink your approach. Recent history In 2011 a paper came out in the Wall Street Journal called “Why Software Is Eating The World”. The paper was written by Marc Andreess

The PowerShell Conference Book

“Imagine attending a PowerShell conference where over thirty speakers who are subject matter experts in the industry are each presenting one forty-five minute session. All of the sessions are at different times so there's no need to worry about choosing between them. You might be wondering how much a conference like this will cost by the time you pay for the conference, hotel, airfare, and meals? Well, there's no need to worry because this conference doesn't cost a fortune because it's actually a book that's designed to be like a conference.” - From “The PowerShell Conference book” There is a new book in town and it is not a regular book. It is designed to be like a PowerShell conference where the topics are divided into sections ranging from “PowerShell Scripting” to “CloudOps/DevOps”. Each chapter in the book is written by industry experts, hence every chapter is unique and independent. I am very humble and proud of being able to announce that I have wri

Developing PowerShell modules for REST APIs – Part2

This is part 2 of the REST API blogpost. In part1 we successfully setup two REST API endpoints using the UniversalDashboard PowerShell module. In this part we are going to create a simple module that support some CRUD operation against our API. As we are trying to keep things as simple as possible, we will not use any fancy framework (like Plaster) to build our module. We are also going to skip a very important step you should familiarize yourself with, Pester tests. Lets get to it. The module We will build a module called FilesAPI. The module folder will look like this: In the functions folder I have already added the 2 helper functions from part 1, Get-AuthorizationHeader and ConvertTo-Base64 . The other folders are just placeholders for important stuff like classes, private functions that you do not want to make available for the module consumer and tests for Pester tests. For such a small module that we are going to create, one could argue that it is much easier to just

Developing PowerShell modules for REST APIs – Part1

Over the years I have developed different PowerShell modules for different web APIs. I thought it would be a good idea to write a 2 series post about how you could go about to do this. This will be a 2 part blog series where we will run through the entire process of building a module for a REST API. I will try my best to keep this as simple as possible and leave more advanced stuff for a follow up post if the interest is there. What you need Depending on your experience with source control and PowerShell in general, you might want to use GIT or some other software repro for the code. In addition we are going to create a test REST API using the splendid UniversalDashboard PowerShell module created by Adam Driscoll. It is available on the PowershellGallery. Other prerequisites are built-in to Powershell. I will assume that you will be following along using at least PowerShell version 5 or greater. What is HTTP metods for REST API. The primary or most common HTTP verbs used are P