Heykuki News
Top
New
Best
Ask
Show
Jobs
Toggle theme
Login
Top
New
Best
Ask
Show
Jobs
91.
▲
From Closed to Open Source: Microsoft's experience with six internal projects
(neverworkintheory.org)
2 points
pabs3
4 years ago
discuss
92.
▲
How Effective Is Continuous Integration in Indicating Single-Statement Bugs?
(neverworkintheory.org)
2 points
mpweiher
4 years ago
discuss
93.
▲
Characterizing Single-Statement Bugs in Popular Open-Source Python Projects
(neverworkintheory.org)
2 points
pabs3
4 years ago
discuss
94.
▲
An empirical study of obsolete answers on stack overflow
(neverworkintheory.org)
2 points
pabs3
4 years ago
discuss
95.
▲
Where should I comment my code? Predicting locations needing comments
(neverworkintheory.org)
2 points
pabs3
4 years ago
discuss
96.
▲
App Store Effects on Software Engineering Practices
(neverworkintheory.org)
2 points
pabs3
5 years ago
discuss
97.
▲
What's Missing from 'The Missing Readme'
(neverworkintheory.org)
2 points
zdw
5 years ago
discuss
98.
▲
Two Studies of Software Evolution
(neverworkintheory.org)
2 points
pabs3
5 years ago
discuss
99.
▲
Why Do Developers Use Trivial Packages?
(neverworkintheory.org)
2 points
pabs3
5 years ago
discuss
100.
▲
Short summaries of recent results in empirical software engineering research
(neverworkintheory.org)
2 points
whymarrh
5 years ago
discuss
101.
▲
What Code Is Deliberately Excluded from Test Coverage, and Why?
(neverworkintheory.org)
2 points
zdw
5 years ago
discuss
102.
▲
Beyond the Code Itself: How Programmers Look at Pull Requests
(neverworkintheory.org)
2 points
pabs3
5 years ago
discuss
103.
▲
Toxic Code Snippets on Stack Overflow
(neverworkintheory.org)
2 points
pabs3
5 years ago
discuss
104.
▲
It Will Never Work in Theory
(neverworkintheory.org)
2 points
memexy
6 years ago
discuss
105.
▲
Developer Testing in the IDE
(neverworkintheory.org)
2 points
mpweiher
9 years ago
discuss
106.
▲
The Role of Ethnographic Studies in Empirical Software Engineering
(neverworkintheory.org)
2 points
vog
9 years ago
discuss
107.
▲
Hiatus
(neverworkintheory.org)
2 points
BuuQu9hu
10 years ago
discuss
108.
▲
Apex: Automatic Programming Assignment Error Explanation
(neverworkintheory.org)
2 points
mynameislegion
10 years ago
discuss
109.
▲
It Will Never Work in Theory
(neverworkintheory.org)
2 points
gry
10 years ago
discuss
110.
▲
Design Patterns Experiment W. Moderator Variables to Generalize Across Contexts
(neverworkintheory.org)
2 points
mpweiher
10 years ago
discuss
111.
▲
Perspectives on Data Science for Software Engineering
(neverworkintheory.org)
2 points
ashitlerferad
10 years ago
discuss
112.
▲
Frequency Distribution of Error Message
(neverworkintheory.org)
2 points
ashitlerferad
10 years ago
discuss
113.
▲
Too Many Knobs
(neverworkintheory.org)
2 points
henrik_w
10 years ago
discuss
114.
▲
Hidden Truths in Dead Software Paths
(neverworkintheory.org)
2 points
ashitlerferad
10 years ago
discuss
115.
▲
When, How, and Why Developers (Do Not) Test in Their IDEs
(neverworkintheory.org)
2 points
ashitlerferad
10 years ago
discuss
116.
▲
Do Developers Read Compiler Error Messages?
(neverworkintheory.org)
1 point
azhenley
5 years ago
2 comments
117.
▲
Do You Code?
(neverworkintheory.org)
1 point
pabs3
4 years ago
1 comment
118.
▲
Python Coding Style Compliance on Stack Overflow
(neverworkintheory.org)
1 point
zdw
5 years ago
1 comment
119.
▲
An Empirical Investigation into Programming Language Syntax
(neverworkintheory.org)
1 point
state
11 years ago
discuss
120.
▲
An Empirical Investigation into Programming Language Syntax
(neverworkintheory.org)
1 point
shawndumas
12 years ago
discuss
More