Category Archives: C#

End of the Road For Azure DevOps?

With Microsoft now owning GitHub, the technical teams have been integrated, resulting in Azure DevOps and GitHub having the same leadership and personnel. The long-term strategic direction will be GitHub, but there is no plan for Azure DevOps to go into maintenance/sunset; therefore, choosing Azure DevOps is entirely OK in short to (undefined) medium term. Azure DevOps is currently in the early stages of development. When migration tools are needed, Microsoft will give them.

Continue reading End of the Road For Azure DevOps?

GitHub Naming Repositories

As part of our customer engagement, we have defined a naming convention for GitHub repositories. 

We have ideas around what conventions made sense, although the type of work influences these. As we tend to spend some of your engineering time working with different languages, conventions around naming formats make sense to the engineers. These, of course, might not make sense to individuals in other fields. 

Continue reading GitHub Naming Repositories


GISTS – engage in chat or gossip. 
“I need a good friend I can always gist with.” 

It is always good to chat with others, which is how we learn from each other. So why don’t project teams chat with each other? In this day and age of working from home, it is becoming more and more critical to form a social network, which helps not only with mental health but also work-related ideas and time. 

Continue reading gists

Fault tolerance using Polly

What is a Resilience Framework?

Polly is classed as a resilience framework. A resilience framework is a set of libraries that help an application to recover from transient or more extended failures in services or infrastructure upon which it depends. When recovery is not possible, the resilience framework will facilitate graceful degradation of your application.

Polly has been around for many years and has been tried and tested in many applications

The source code for Polly can be found on GitHub here:

Continue reading Fault tolerance using Polly