EDBT 2026 Demo / reviewers in the wild / expert
Sultan Wehaibi
dblp:180/7322
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 2017
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 70% Empirical software engineering · 30% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
mining software repositories |
0.3 | 1 | 2017 | Why do developers use trivial packages? an empirical case study on npm · ESEC/SIGSOFT FSE 2017 |
Software maintenance and evolution › software ecosystems
package dependencies |
0.3 | 1 | 2017 | Why do developers use trivial packages? an empirical case study on npm · ESEC/SIGSOFT FSE 2017 |
Software maintenance and evolution
software ecosystems |
0.3 | 1 | 2017 | Why do developers use trivial packages? an empirical case study on npm · ESEC/SIGSOFT FSE 2017 |
Software maintenance and evolution
code reuse |
0.1 | 1 | 2017 | Why do developers use trivial packages? an empirical case study on npm · ESEC/SIGSOFT FSE 2017 |
Methods — techniques the papers use, named apart from their topics
empirical case study · 0.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2017 | Why do developers use trivial packages? an empirical case study on npmabstractCode reuse is traditionally seen as good practice. Recent trends have pushed the concept of code reuse to an extreme, by using packages that implement simple and trivial tasks, which we call `trivial packages'. A recent incident where a trivial package led to the breakdown of some of the most popular web applications such as Facebook and Netflix made it imperative to question the growing use of trivial packages. Rabe Abdalkareem, Olivier Nourry, Sultan Wehaibi, Suhaib Mujahid, Emad Shihab |
ESEC/SIGSOFT FSE | 3 |
| 2016 | Examining the Impact of Self-Admitted Technical Debt on Software QualityabstractTechnical debt refers to incomplete or temporary workarounds that allow us to speed software development in the short term at the cost of paying a higher price later on. Recently, studies have shown that technical debt can be detected from source code comments, referred to as self-admitted technical debt. Researchers have examined the detection, classification and removal of self-admitted technical debt. However, to date there is no empirical evidence on the impact of self-admitted technical debt on software quality. Therefore, in this paper, we examine the relation between self-admitted technical debt and software quality by investigating whether (i) files with self-admitted technical debt have more defects compared to files without self-admitted technical debt, (ii) whether self-admitted technical debt changes introduce future defects, and (iii) whether self-admitted technical debt-related changes tend to be more difficult. We measured the difficulty of a change using well-known measures proposed in prior work such as the amount of churn, the number of files, the number of modified modules in a change, as well as the entropy of a change. An empirical study using five open source projects, namely Hadoop, Chromium, Cassandra, Spark and Tomcat, showed that: (i) there is no clear trend when it comes to defects and self-admitted technical debt, although the defectiveness of the technical debt files increases after the introduction of technical debt, (ii) self-admitted technical debt changes induce less future defects than none technical debt changes, however, (iii) self-admitted technical debt changes are more difficult to perform, i.e., they are more complex. Our study indicates that although technical debt may have negative effects, its impact is not only related to defects, rather making the system more difficult to change in the future. Sultan Wehaibi, Emad Shihab, Latifa Guerrouj |
SANER | 1 |