GitHub Codespaces

What I like most about GitHub Codespaces is how it removes the setup time. It keeps everything consistent and works seamlessly with GitHub. This makes collaboration, productivity, and overall development smoother, faster & most effecient.

It is an instant, fully configured development environment. Development experience feels almost identical to the local VS Code and the ability to install extensions and customize dev containers is a big plus.

What I appreciate most about GitHub Code Spaces is its ability to address key pain points and align with our organizational strategy. The main issues we aimed to resolve were faster developer onboarding and reducing hardware investments. Faster Onboarding & Resource Management: One of the most significant advantages is its ability to drastically accelerate the onboarding process for development resources. Previously, this took between one to two weeks, now, it's instantaneous. This saves an estimated half a month of unit cost per person. The tool makes it very easy to control and give quick access to vendor resources, eliminating the need for physical hardware distribution. This faster onboarding was a key pain point we aimed to fix. Seamless Integration & Enterprise Support: As a major Microsoft partner, and with Microsoft owning GitHub, the product naturally offers strong enterprise support. Integration with our Microsoft-based internal systems, like LDAP and access management, was critical. This seamless connection simplifies onboarding and removal of resources, especially for vendor organizations, making it easier to validate and revoke access. Cost Efficiency & Flexibility: GitHub Code Spaces offers a significant advantage by enabling the conversion of CapEx to OpEx. This shift away from large upfront hardware investments was a primary pain point, leading to reduced hardware investments. The business case is strong, indicating a good ROI. Scalability & Customization: There are no challenges in scaling GitHub Code Spaces to our needs. It allows us to tailor it perfectlylinking to code repositories, managing access rights, segregating duties between environments, and integrating with Visual Studio and other development tools without issues. Performance: We have not experienced downtime so far, mainly using it for proof of concept scenarios. The product promises 99.99% availability, which is more than sufficient, as developer downtime has minimal impact on our business.

What I dislike about this service is its reliance on a stable internet connection, which can slow down things in areas with poor connectivity. Resource heavy workloads task don't run quite as smoothly as would on a powerful local machine.

Reliance on an internet connection is the biggest drawback as it requires a fast and reliable connection because daily heavy usage for development can be expensive and performance depends upon network quality.

While GitHub Code Spaces largely meets our expectations, there are a couple of areas where I see potential for improvement or where minor friction points exist. My recommendations for changes or enhancements to the current product primarily revolve around: Legacy and Hybrid Environment Support: I would suggest that GitHub Code Spaces consider linking with or being available for legacy environments and languages. While it is clearly designed for new-age languages, there could be use cases for supporting older languages, although I do not envision its use with mainframes. Hybrid Work Environment Extensions: I would also like to see extensions that could work in a hybrid environment. This would be particularly valuable for highly controlled or secure environments, such as banking, where cloud deployment might not be feasible. I have not fully explored if this functionality already exists, but it would be a desirable addition. In terms of business challenges or unmet expectations, I can unequivocally state that we have not encountered any significant issues. For its specific use case, which is currently small scale, the product does what it is expected to do and it does it well. We have experienced no performance issues or downtime during our usage for proof of concept scenarios. The impact of any potential developer downtime is considered very low, and the product's high uptime satisfies our requirements. A minor point of friction relates to the evaluation and contract negotiation process. Despite being part of the same parent company, Microsoft and GitHub teams operate separately. This can occasionally lead to a scenario where an agreement with Microsoft does not automatically translate to an agreement with GitHub, causing a small delay in communication and engagement. However, it's important to note that they eventually take feedback and implement it, which is a positive outcome.