2020 did something remarkable: it compressed five years of digital transformation into twelve months. The pandemic forced organizations to adopt remote work, cloud infrastructure, and digital-first services faster than any consultant could have planned. The technology trajectories that were supposed to be five-year bets became one-year realities. If you were thinking about cloud migration, you suddenly had no choice. If you were building distributed teams, you had three weeks to figure it out.
The remote work forcing function
In March 2020, engineering organisations that had never seriously invested in remote work tooling had three weeks to figure it out. Teams that had modern DevOps practices, cloud-hosted infrastructure, and asynchronous communication habits adapted quickly. Teams that depended on physical proximity for code reviews, architecture discussions, and incident response had a much harder time. The gap between digitally mature and digitally lagging organisations widened sharply.
Cloud acceleration
AWS, Azure, and GCP all reported accelerated cloud adoption in 2020. The combination of rapidly growing remote workloads, the need for scalable video conferencing and collaboration infrastructure, and increased e-commerce volumes drove cloud growth. Organisations that had deferred cloud migration as a three-year project found themselves needing cloud scalability immediately.
.NET 5 ships
November 2020 brought .NET 5, the first release of the unified .NET platform (merging .NET Core and .NET Framework into a single product line). Performance improvements, new C# 9 language features, and the clearer upgrade path made .NET 5 a milestone release. The unification message was clear: .NET Framework 4.x is maintenance mode; .NET 5 and beyond is the path forward.
The SolarWinds disclosure
December 13th brought the disclosure of the SolarWinds Orion supply chain compromise, one of the most significant cybersecurity events of the decade. The attack demonstrated the fragility of software supply chains and raised fundamental questions about build system security, code signing, and the trusted update mechanism. The full scope of the compromise took months to understand.