Heykuki News
Top
New
Best
Ask
Show
Jobs
Toggle theme
Login
Top
New
Best
Ask
Show
Jobs
151.
▲
Company Contributions to Open Source
(neverworkintheory.org)
1 point
zdw
4 years ago
discuss
152.
▲
Database-Access Performance Antipatterns in Database-Backed Web Applications
(neverworkintheory.org)
1 point
mpweiher
4 years ago
discuss
153.
▲
The Adoption of JavaScript Linters in Practice: A Case Study on ESLint
(neverworkintheory.org)
1 point
pabs3
4 years ago
discuss
154.
▲
A Large Scale Study of Long-Time Contributor Prediction for GitHub Projects
(neverworkintheory.org)
1 point
pabs3
4 years ago
discuss
155.
▲
Strategies to Improve Continuous Integration
(neverworkintheory.org)
1 point
pabs3
4 years ago
discuss
156.
▲
Resume-Driven Development
(neverworkintheory.org)
1 point
zdw
4 years ago
discuss
157.
▲
Characterizing Single-Statement Bugs in Popular Open-Source Python Projects
(neverworkintheory.org)
1 point
zdw
4 years ago
discuss
158.
▲
A case history analysis of software error cause-effect relationships
(neverworkintheory.org)
1 point
mpweiher
4 years ago
discuss
159.
▲
Short and approachable summaries of recent software engineering research
(neverworkintheory.org)
1 point
rohitpaulk
4 years ago
discuss
160.
▲
Three Empirical Evaluations of UML
(neverworkintheory.org)
1 point
chadaustin
15 years ago
discuss
161.
▲
Investigating Next Steps in Static API-Misuse Detection
(neverworkintheory.org)
1 point
mpweiher
5 years ago
discuss
162.
▲
Exploring Programmers' API Learning Processes
(neverworkintheory.org)
1 point
mpweiher
5 years ago
discuss
163.
▲
A Critical History of Logo and Constructionist Learning
(neverworkintheory.org)
1 point
mpweiher
5 years ago
discuss
164.
▲
The Relevance of Classic Fuzz Testing
(neverworkintheory.org)
1 point
mpweiher
5 years ago
discuss
165.
▲
Are Delayed Issues Harder to Resolve?
(neverworkintheory.org)
1 point
mpweiher
5 years ago
discuss
166.
▲
Are Delayed Issues Harder to Resolve?
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
167.
▲
The Secret Life of Bugs
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
168.
▲
Syntax, Predicates, Idioms–What Affects Code Complexity?
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
169.
▲
Program comprehension of domain-specific and general-purpose languages
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
170.
▲
Code of Conduct in Open Source Projects
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
171.
▲
Analyzing the effects of test driven development in GitHub
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
172.
▲
Analyzing the effects of test driven development in GitHub [repositories]]
(neverworkintheory.org)
1 point
rudenoise
5 years ago
discuss
173.
▲
Short summaries of recent results in empirical software engineering research
(neverworkintheory.org)
1 point
rolisz
5 years ago
discuss
174.
▲
Organizing for openness: models for developer involvement in hybrid OSS projects
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
175.
▲
Do Software Developers Understand Open Source Licenses?
(neverworkintheory.org)
1 point
zdw
5 years ago
discuss
176.
▲
Compiler Error Messages Considered Unhelpful
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
177.
▲
A Statistical Survival Analysis of Publicly Available Python Projects
(neverworkintheory.org)
1 point
pabs3
5 years ago
discuss
178.
▲
It Will Never Work In Theory - applicable software engineering research results
(neverworkintheory.org)
1 point
keyist
15 years ago
discuss
179.
▲
Fixing Faults in C and Java Code: Abbreviated vs. Full-Word Identifier Names
(neverworkintheory.org)
1 point
slacko
8 years ago
discuss
180.
▲
No significant difference between TDD and iterative test-last (ITL) development
(neverworkintheory.org)
1 point
vog
9 years ago
discuss
More