Contributing to Open Source Software. It sounds so formal, doesn't it? I thought that for quite a long time, and it put a bit of a mental barrier in place for me to begin my journey. I am a classic over thinker, but that's perhaps another blog in its own right! Contributing to Open Source isn't as scary as it may first initially seem. Let's start with a few thoughts.

During the 2020 Festive Break, I had a lot of time on my hands. I took 4 weeks of my Annual Leave, which meant I had the majority of December to personal time. Personal time / time off is great, but I also wanted to push myself and catch up on some pieces that were on my personal learning or achievement list for some time. I started refreshing my knowledge around Rails (having developed in it some years ago, it's progressed quite a bit!), NodeJS, GoLang and Rust. All interesting to learn, and I'm sure I'll be continuing on my journey with these throughout 2021. But that's not the point in this blog post. One of the activities that I kicked off was contributing into the Hugo Community. Read on to find out more.

You may have noticed there are some posts preceding this one. I've had a few attempts at putting my blog together, but then dwindle out on my cadence… Well, given the recent success with my Cloud with Chris podcast, I'm beginning to consolidate… Starting with my blog! Here's an update on what you have to look forward to!

In my spare time, I work on a pet project called Theatreers. The aim of this is a microservice based platform focused on Theatre / Musical Theatre (bringing a few of my passion areas together). I've recently re-architected the project to align to a multi-region serverless technology stack.

Consider this scenario. You are managing a software project using Azure DevOps, and you have multiple teams working towards a common cadence. Perhaps that cadence is managed by a central team. To gain the most value from your sprint planning, you would need to associate the iterations from the project level with each individual team. This is a scenario that I have for my fictitious Theatreers project, but also a scenario I encountered recently with a colleague. I have been helping them setup an Azure DevOps project to track the development of IP and collateral, so that they can more accurately forecast what they expect to land and show the value being delivered by the team.

Cloud Governance seems to have come up a few times over the past few weeks, so I wanted to post a short, sharp blog about it!

Scalability is one of the common areas where I have seen common misconceptions, when customers begin building on the platform.

In case you had not already heard, Logic Apps have now reached general availability on Azure (or read an MSDN article by Jeff Hollan on the topic).

When designing a solution, you want to be sure that your communications are secure and that your users can trust your application. Typically, SSL certificates can be useful for this purpose.That is well and good from a design and development perspective, but there may some management headaches when operating and governing the solution. How do you keep track of the certificates? How do you guarantee that they are kept secure? How do you ensure that certificates renew on time?