June 2024 Summaries

Financial institutions are facing challenges in achieving return on investment (ROI) from their technology spend due to issues such as incorrect initial investment decisions and not considering 'day 2' overhead. The financial sector has unique demands, with security and compliance being top priorities. Recent analyst research highlights a shift from the traditional 'build over buy' approach, with banks now allocating more than 70% of their tech budgets to automation, AI, developer productivity enhancements, blockchain, and other technologies. However, even between the highest tech spenders and lowest tech spenders, banks are seeing less than 45% return on their tech investments. One major contributor to this lack of ROI is 'day 2' overhead, which refers to the operations and maintenance expenses of software. To address these issues, financial institutions should consider platform as a product thinking and focus on supporting the inner loop, both of which can be immediately supported by automating and standardizing development environments. Gitpod offers a self-hosted, not self-managed solution for automated and standardized development environments that helps banks increase ROI on tech spend.

Financial institutions, traditionally slow to adopt technology due to concerns over stability and security, are now investing heavily in tech solutions like automation, AI, and developer productivity tools. Despite these investments, many banks are experiencing less than a 45% return on their tech expenditures. A significant issue contributing to this low ROI is the 'day 2' overhead, which includes the ongoing operations and maintenance costs of software. Many banks mistakenly believe that self-hosted solutions must also be self-managed, leading to increased overhead. Shifting to self-hosted, vendor-managed solutions can reduce these costs while maintaining security and compliance standards. Additionally, adopting a 'platform as a product' mindset, which focuses on user-centric solutions and supporting the 'inner loop' of development, can improve productivity and ROI. Ona's AI-native development platform exemplifies this approach by providing automated, standardized development environments that enhance security, productivity, and ease of adoption without the burdensome 'day 2' overhead, thereby offering a more efficient way for financial institutions to realize their technology investments.

The article discusses the importance of cloud development environments (CDEs) in driving platform adoption and improving developer efficiency. It highlights that many platform teams struggle with 'day 2' issues and developer adoption challenges, often overlooking developer experience. CDEs enable platform teams to balance control and freedom for developers by providing direct access to support them through development environments. Key benefits of using a CDE include automating dependencies, access management, extensions, and resources configuration. The article emphasizes that with Gitpod, a developer can maintain their usual access controls while the platform team manages standardization and updates seamlessly, ensuring maximum ROI for platform initiatives.

Platform Con 2024 in London highlighted a significant gap between discussions on standardization and developer efficiency and the actual awareness of cloud development environments (CDEs) among platform teams. Many teams faced challenges with 'day 2' issues, developer adoption, and the lack of a developer experience focus, often treating it as an afterthought. Talks at the conference emphasized the importance of treating platforms as products, prioritizing user and developer needs. Traditionally, platform teams have had limited influence over the development aspect of the software lifecycle, often publishing tools and leaving developers to independently configure and integrate them, resulting in slow adoption and fragmented standards. CDEs offer a solution by providing platform teams with direct access to support developers through centralized standardization and automation of dependencies, access management, extensions, and resources. This approach minimizes redundant setup and networking tasks, allowing platform, AI, and application engineers to focus on substantial improvements. CDEs ensure seamless updates and consistent, functional development environments, ultimately maximizing the return on investment for platform teams' efforts.

This guide explains how to set up and automate the mounting of a directory in a Gitpod workspace so that files are automatically synced with an Amazon S3 bucket using "s3fs". The process involves installing AWS CLI and s3fs, authenticating with S3, creating an S3 bucket, creating a directory and linking it to S3, and automating access to AWS S3. By following these steps, users can create shared storage across workspaces where files added, deleted or renamed in the shared directory sync automatically to S3 for access by other team members.