December 14, 2009 marked a significant milestone in my career as an engineer and platform architect. Looking back at this date now, it seems like another world—just one year after the global financial crisis started to hit hard, and three years before the ubiquity of cloud services would become mainstream. Yet, many of the battles we were fighting then still echo today.

The Cloud vs. Colo Debate

Back in 2009, the tech industry was grappling with a major shift: the move from traditional colocation (colo) facilities to cloud computing. I vividly remember heated discussions about which approach was better for our growing team at [Company Name]. The cloud offered flexibility and scalability, but we were concerned about vendor lock-in and security.

One particular argument revolved around AWS’s EC2 and S3 services. While some argued that the service level agreements (SLAs) made by Amazon provided a safety net we couldn’t get from colo providers, others feared that the costs would balloon as our footprint grew. I remember staying up late with my colleague John, debating whether to fully commit to AWS or keep a hybrid model with some servers still in a colo facility.

Git Adoption Spreads

On a lighter note (or perhaps more accurately, a less stressful one), Git was slowly but surely becoming the standard for version control. At our company, we were early adopters of Git and GitHub. The excitement around this new tool was palpable; developers could finally get away from the clunky Subversion repositories they had been using for years.

GitHub’s launch in 2008 had already started to change the landscape, but by December 2009, it seemed like every startup and established company was starting to use Git. The idea of a centralized repository on GitHub where pull requests could be reviewed and merged became a cultural norm within our team. We were spending more time learning how to effectively use Git than we would have imagined just a few years prior.

The iPhone SDK

The iPhone SDK had been released in July 2008, but the impact was still fresh. Apple’s decision to allow third-party developers into their ecosystem sparked a wave of innovation and competition. I remember the buzz around the App Store; everyone wanted to be part of it. Our team had discussions about whether developing for iOS made sense given our focus on web applications. The debate centered not just on technical feasibility but also on the business opportunity.

The Microsoft Plurk Issue

As a tech-savvy individual, I kept up with Hacker News regularly. One story that stuck out to me was Microsoft’s alleged rip-off of Plurk, an open-source social networking platform. This incident highlighted the tensions between proprietary and open-source software. It made me reflect on the balance between innovation and respect for intellectual property in a world increasingly dominated by large tech companies.

Agile vs. Scrum

Another topic that frequently came up was agile development methodologies versus Scrum. Our team had recently adopted Scrum, and there were debates about whether it was the right approach or if we should stick with our Waterfall practices. The economic downturn made us even more cautious, but the benefits of faster feedback loops and better collaboration among developers couldn’t be ignored.

Conclusion

Looking back, December 14, 2009 feels like a pivotal moment in my career. It was during this time that cloud computing started to gain real traction, Git adoption spread rapidly, and we were actively debating the future of our infrastructure and development processes. While the debates around “Cloud vs. Colo” may seem quaint today, they laid the groundwork for many of the discussions I continue to have in my current role as an engineering manager.

The tech world has changed a lot since 2009, but these foundational questions—about tools, platforms, and methodologies—continue to shape our industry. What started as simple arguments over Git repositories and AWS services has evolved into larger conversations about how technology impacts every aspect of our lives.