Demo Data from EDBT 2026 / reviewers in the wild / expert
Ted Tenny
dblp:63/423
· DBLP profile ↗
2ranked-venue papers
2as first author
0since 2021 · last 1988
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-authorHuman-computer interaction and ubiquitous computing · 1 · 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 |
Empirical software engineering · 61% Software maintenance and evolution · 39% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
controlled experiment |
0.0 | 1 | 1988 | Program Readability: Procedures Versus Comments · IEEE Trans. Software Eng. 1988 |
Empirical software engineering
developer studies |
0.0 | 1 | 1988 | Program Readability: Procedures Versus Comments · IEEE Trans. Software Eng. 1988 |
Software maintenance and evolution
program comprehension |
0.0 | 1 | 1988 | Program Readability: Procedures Versus Comments · IEEE Trans. Software Eng. 1988 |
Software maintenance and evolution
software documentation |
0.0 | 1 | 1988 | Program Readability: Procedures Versus Comments · IEEE Trans. Software Eng. 1988 |
Methods — techniques the papers use, named apart from their topics
factorial experiment · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1988 | Program Readability: Procedures Versus CommentsabstractA 3*2 factorial experiment was performed to compare the effects of procedure format (none, internal, or external) with those of comments (absent or present) on the readability of a PL/1 program. The readability of six editions of the program, each having a different combination of these factors, was inferred from the accuracy with which students could answer questions about the program after reading it. Both extremes in readability occurred in the program editions having no procedures: without comments the procedureless program was the least readable and with comments it was the most readable.> Ted Tenny |
IEEE Trans. Software Eng. | 1 |
| 1987 | Leadership style vs. succssus in student chief programmer teamsabstractThe style of leadership on chief programmer teams was inferred from student peer evaluations, using a sample of 87 teams over a seven-year period.The strongest correlations with team success resulted from diligent attention (or lack thereof) to the duties of the Chief Programmer, Backup, and Librarian, rather than from leadership personality factors. Ted Tenny |
SIGCSE | 1 |