Piranha

Ramanathan, Murali; Clapp, Lazaro; Barik, Rajkishore; Sridharan, Manu

doi:10.1145/3377813.3381350

Cited by 12 publications

(1 citation statement)

References 35 publications

(32 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The authors also indicate that mobile code smells represent inadvertent technical debt (i.e., debt introduced by oversight than strategically). In [31], Ramanathan et al describe how their tool efficiently reduces technical debt related to state feature flags on mobile apps, including Android apps, through refactoring.…”

Section: A Android Appsmentioning

confidence: 99%

An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps

Wilder¹,

Riley²,

Watson³

et al. 2023

Preprint

View full text Add to dashboard Cite

Technical debt describes situations where developers write less-than-optimal code to meet project milestones. However, this debt accumulation often results in future developer effort to live with or fix these quality issues. To better manage this debt, developers may document their sub-optimal code as comments in the code (i.e., self-admitted technical debt or SATD). While prior research has investigated the occurrence and characteristics of SATD, this research has primarily focused on non-mobile systems. With millions of mobile applications (apps) in multiple genres available for end-users, there is a lack of research on sub-optimal code developers intentionally implement in mobile apps.In this study, we examine the occurrence and characteristics of SATD in 15,614 open-source Android apps. Our findings show that even though such apps contain occurrences of SATD, the volume per app (a median of 4) is lower than in non-mobile systems, with most debt categorized as Code Debt. Additionally, we identify typical elements in an app that are prone to intentional sub-optimal implementations. We envision our findings supporting researchers and tool vendors with building tools and techniques to support app developers with app maintenance.

show abstract

Section: A Android Appsmentioning

confidence: 99%

An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps

Wilder¹,

Riley²,

Watson³

et al. 2023

Preprint

View full text Add to dashboard Cite

show abstract

How the adoption of feature toggles correlates with branch merges and defects in open‐source projects?

2021

View full text Add to dashboard Cite

Branching has been widely adopted in version control to enable collaborative software development. However, the isolation caused by branches may impose challenges on the upcoming merging process. Recently, companies like Google, Microsoft, Facebook, and Spotify, among others, have adopted trunk-based development together with feature toggles. This strategy enables collaboration without the need for isolation through branches, potentially reducing the merging challenges. However, the literature lacks evidence about the benefits and limitations of feature toggles to collaborative software development.Objective/method: In this article, we study the effects of applying feature toggles on 949 open-source projects written in six different programming languages.We first identified the moment in which each project adopted a feature toggles framework. Then, we observed whether the adoption implied significant changes in the frequency or complexity of branch merges and the number of defects, and the average time to fix them. Finally, we compared the obtained results with results obtained from a set of control projects that do not use feature toggles frameworks. Results/conclusion:We could observe a reduction in the average merge effort and an increase in the average total time needed to fix defects after adopting feature toggles frameworks. However, we could not confirm that this increase was influenced by the use of feature toggles.

show abstract

SoK: A Tale of Reduction, Security, and Correctness - Evaluating Program Debloating Paradigms and Their Compositions

Ali,

Muzammil,

Karim

et al. 2024

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Piranha

Cited by 12 publications

References 35 publications

An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps

An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps

How the adoption of feature toggles correlates with branch merges and defects in open‐source projects?

SoK: A Tale of Reduction, Security, and Correctness - Evaluating Program Debloating Paradigms and Their Compositions

Contact Info

Product

Resources

About