September 2025 Summaries

Feature toggles and feature flags, often used interchangeably, serve as critical tools in managing software functionality without redeploying code, yet they differ significantly in their implementation and application. Feature toggles, originating in the early 2000s, are simple boolean checks in code that allow developers to hide incomplete features, and are typically temporary. In contrast, feature flags offer more sophisticated control with multivariate values and real-time dashboards, enabling targeted user segments, gradual rollouts, and business-oriented experimentation. Engineering teams initially use feature toggles for quick and uncomplicated setups, but as complexity grows, they transition to feature flags to leverage advanced capabilities like A/B testing and canary releases. Effective management of these tools involves clear ownership, lifecycle governance, and addressing challenges such as scaling bottlenecks and cross-team coordination. Ultimately, the choice between feature toggles and feature flags depends on the maturity and needs of the team, with both leading to safer, faster software delivery and enhanced responsiveness to user feedback and market changes.

This tutorial provides a comprehensive guide on using the Flagsmith Java SDK to implement feature flags in a Java application, demonstrating how feature flags can enhance code functionality without requiring code merges or redeployment. Feature flags, or toggles, allow developers to control code behavior dynamically, facilitating efficient and low-risk feature rollouts, A/B testing, and phased deployments. The tutorial includes a hands-on walkthrough of creating a basic Java server application that manages book records and integrates Flagsmith to control features like adding new books based on flag settings. It illustrates the ease of toggling feature availability through Flagsmith's user interface, which requires minimal configuration and no code changes for functionality alterations. Additionally, the tutorial explores advanced usage of Flagsmith, such as leveraging feature flag values and utilizing local evaluation mode to optimize server performance by reducing repetitive API calls. The guide emphasizes the benefits of using Flagsmith, a free and open-source platform, for agile software development and deployment, offering flexibility, transparency, and seamless integration with existing tools and workflows.

Over the past decade, engineering teams have increasingly embraced faster deployment tempos, progressing from quarterly releases under Waterfall methodologies to more frequent, sprint-aligned Agile deployments. Influential research, such as that by the DORA team, suggests that teams deploying more frequently often achieve higher quality and stability. Practices like Trunk-Based Development and Continuous Deployment allow teams to push changes to production multiple times a day by integrating smaller batch sizes and feature flagging, which decouples deployment from release. This shift necessitates changes in software development life cycles (SDLCs), such as minimizing the "hardening" phase and leveraging automated testing to validate code post-deployment. While Continuous Deployment offers benefits like faster feedback and reduced risk through smaller, more frequent updates, it also requires careful management of feature flags and project tracking to prevent code clutter and ensure tasks are fully completed. By embracing these practices, teams can deliver value more efficiently and with greater stability, though the transition demands significant adjustments in testing and release management strategies.

Open source software has significantly infiltrated the corporate world, with an estimated 96% of all codebases containing open-source elements, and major companies like Google and Microsoft actively contributing to such projects. However, the financial services industry has been slower to engage with open source due to cultural, regulatory, and policy barriers, which often prevent firms from contributing back to the community. Despite these challenges, there is recognition within the industry of the benefits of open source, such as reducing dependency risks, avoiding excessive internal forks, and enhancing strategic positions. Organizations like FINOS are helping financial services firms navigate these challenges by offering projects and best practices that encourage collaboration and open source adoption. While financial services firms are beginning to take steps toward more open source engagement, including trial projects and policy revisions, there is still a journey ahead to balance in-house and open source development based on project merit.

Flagsmith has experienced significant growth over the past few years, achieving a 250% increase since 2023, and its journey highlights the complexities of building a successful commercial open-source business. This journey involved learning from renowned open-source founders, emphasizing the importance of community, addressing personal challenges ("scratching your itch"), selecting the appropriate open-source license, and leveraging the advantages of small teams. Despite the challenges, the founders of Flagsmith discovered that small teams can be highly responsive, transparent, and adaptable, allowing them to compete against larger, well-funded companies. The transition to a commercial entity is a lengthy process, taking Flagsmith five years to reach $1M ARR, but it is fueled by the growing influence of open-source software in the technology landscape. Open-source software continues to expand, offering solutions to modern challenges and fostering a community that thrives on shared knowledge and collaboration, a theme explored further in an upcoming podcast series on the subject.