arXiv subjects

Serkan Kirbas

Publications and source records attributed to Serkan Kirbas.

3 recordsLinked to original sources

arXiv2026

Pomona: Continuous Code Quality Improvement via Small, Agentic Pull Requests at Bloomberg

In this industrial experience paper, we present Pomona, a lightweight agentic tool that utilises agent skills for continuous code quality improvement. Inspired by the Kaizen (TM) philosophy, Pomona automates a cycle of discovery and incremental repair: a Scanning skill identifies tasks and prioritises them in a backlog, while a Repair skill generates small, easily reviewable pull requests (PRs). This design enables frequent, low-risk improvements while maintaining engineer trust and reducing technical debt. We evaluated Pomona at Bloomberg through a three-month team deployment and a questionnaire distributed to senior engineers. The results are promising: 32/39 PRs (82.1%) were merged with a median time-to-close of just over two hours. Moreover, 10/12 surveyed engineers expressed a desire to adopt Pomona, praising its small diff sizes and focus on code quality. Since our evaluation, another team has adopted Pomona. We conclude with actionable insights for deploying agents in industry.

cs.SE↗

arXiv2026

BayesInsights: Modelling Software Delivery and Developer Experience with Bayesian Networks at Bloomberg

As software in industry grows in size and complexity, so does the volume of engineering data that companies generate and use. Ideally, this data could be used for many purposes, including informing decisions on engineering priorities. However, without a structured representation of the links between different aspects of software development, companies can struggle to identify the root causes of deficiencies or anticipate the effects of changes. In this paper, we report on our experience at Bloomberg in developing a novel tool, dubbed BayesInsights, which provides an interactive interface for visualising causal dependencies across various aspects of the software engineering (SE) process using Bayesian Networks (BNs). We describe our journey from defining network structures using a combination of established literature, expert insight, and structure learning algorithms, to integrating BayesInsights into existing data analytics solutions, and conclude with a mixed-methods evaluation of performance benchmarking and survey responses from 24 senior practitioners at Bloomberg. Our results revealed 95.8% of participants found the tool useful for identifying software delivery challenges at the team and organisational levels, cementing its value as a proof of concept for modelling software delivery and developer experience. BayesInsights is currently in preview, with access granted to seven engineering teams and a wider deployment roadmap in place for the future.

cs.SE↗

arXiv2023

User-Centric Deployment of Automated Program Repair at Bloomberg

Automated program repair (APR) tools have unlocked the potential for the rapid rectification of codebase issues. However, to encourage wider adoption of program repair in practice, it is necessary to address the usability concerns related to generating irrelevant or out-of-context patches. When software engineers are presented with patches they deem uninteresting or unhelpful, they are burdened with more "noise" in their workflows and become less likely to engage with APR tools in future. This paper presents a novel approach to optimally time, target, and present auto-generated patches to software engineers. To achieve this, we designed, developed, and deployed a new tool dubbed B-Assist, which leverages GitHub's Suggested Changes interface to seamlessly integrate automated suggestions into active pull requests (PRs), as opposed to creating new, potentially distracting PRs. This strategy ensures that suggestions are not only timely, but also contextually relevant and delivered to engineers most familiar with the affected code. Evaluation among Bloomberg software engineers demonstrated their preference for this approach. From our user study, B-Assist's efficacy is evident, with the acceptance rate of patch suggestions being as high as 74.56%; engineers also found the suggestions valuable, giving usefulness ratings of at least 4 out of 5 in 78.2% of cases. Further, this paper sheds light on persisting usability challenges in APR and lays the groundwork for enhancing the user experience in future APR tools.

cs.SE↗