May 2025 Summaries

The text provides a detailed tutorial on implementing a feature flag in a Laravel application using the Flagsmith platform to manage the visibility of actions on a student CRUD application. It begins by outlining the prerequisites, such as familiarity with PHP and Laravel, and the need for a Flagsmith account. The guide walks through setting up a feature flag in Flagsmith, which controls the display of Edit and Delete actions on a student listing page. The tutorial covers cloning an open-source Laravel application, installing necessary dependencies using Composer, and integrating the Flagsmith PHP SDK to enable feature flagging. The implementation involves injecting the Flagsmith client into the Laravel application and modifying the application’s controller and view files to show or hide specific elements based on the feature flag's status. Testing the feature involves toggling the flag in Flagsmith's UI and observing changes in the application without needing to redeploy code. The text concludes with suggestions for optimization through PHP caching and deployment options, while emphasizing best practices for feature flag usage.

Flagsmith, a platform for managing feature flags across various applications, has introduced native integration with Amplitude to enhance the effectiveness of phased rollouts and A/B testing. This integration allows users to seamlessly manage and analyze feature rollouts by automatically syncing data with Amplitude, enabling further segmentation and performance analysis based on the feature flags experienced by different customer segments. The setup is straightforward for current users of both platforms, as the integration automatically transfers data without the need for manual tracking configuration, allowing users to explore and analyze results directly in Amplitude. For Amplitude users not yet utilizing Flagsmith, this integration offers an incentive to consider adopting Flagsmith for more streamlined and insightful A/B testing processes.

Jindrich Kubat, Head of Development & COE at Komerční Banka, discusses the bank's ongoing transformation project, which involves replacing its legacy infrastructure with a modern "Digital Hub" built on microservices and adopting agile and DevOps practices. The initiative, referred to as "The New Digital Bank," is a multi-year project that aims to modernize the bank's systems and culture, incorporating feature flags, OKRs, and the Spotify model for functional teams. The transition includes a focus on open-source technologies like Kafka and ElasticSearch, with a rigorous unification of development practices via the KB Speed framework. The bank has been using feature flags in non-production environments for a year and recently implemented them in production, overcoming security challenges. The feature flags are initially used on the front-end, enabling more agile deployment practices, and there are plans to extend their use to backend systems. The bank is also exploring further integration of feature flag systems with tools like JIRA to enhance coordination between QA teams and product owners.