Welcome to the site, my name is Jeff and I have been working in the IT field since the early 90's. Most of what I post here is related to work that I do for the various companies that I have worked for over the years. Please feel free to look around ask questions or post comments (if available).

Feel free to reach out:

Recent Posts

  • SchemaModule 3.0.1 Release

    I’ve just released a new version of my PowerShell SchemaModule.

  • Week In Review: 02/18/2022

    Welcome to another Friday! Congratulations you made it!

  • The tedious side of development

    So I’ve been working on things both personally and for work. Both projects have similar goals but are implemented differently. But one of the things that I ran up against early on was the idea of defaults. In a json schema you can have default values among a vast array of other options.

  • Language Parsing

    Yesterday I talked about changing up the framework to make it more flexible. Ideally the framework shouldn’t need to know all the details about a given template, it should discover that and then do something with it. After that post I spent a fair amount of time trying to figure out what I meant!

  • Multi-Cloud Deployment Framework

    So the way the original framework was designed was from a console perspective. While it was designed to be run from an Azure Devops Build Agent an engineer could run this locally. So there were command-line arguments and all sorts of things you would expect from a script/utility. So as I began working on this version it started out more or less in the same vein. But I find myself sitting here looking at the code and thinking, this seems rather restrictive and redundant. For example, I’m defining in code an arm template that exists in a repository. You can then take that to the nth degree 1 template per templating language per cloud, that’s a massive amount of duplication. Where is the source of truth for the templates? Does it live in the framework code? Does it live with the templates themselves?