7. Premise of Big Data
Analysis is a “systems” task?
• Better conclusions =
same algorithms + more
data + more cpu
• If so, then …
– No role for human error
– All insight is auto-generated
Analysis is a “human” task?
• Current results on “software
– A human-intensive process
8. Q: Is Big Data a “Systems” or “Human”-task?
9. Code used in my
(1100 LOC of Python
10. Use a Higher-Level languages?
• ECL solves this problem?
• But if you can write it quick,
– you can write it wrong, quick.
11. Is this really a problem?
• Q: What would we expect
to see if…
– Top experts, publishing in top
– Many of the same data sets
– 8 years of trying
– Perhaps some upward
– Perhaps a little less variance
So, what do
12. • Software analytics
– Defect prediction
– Many of the same learners,
– Many of the same data sets
• 42 papers,
• 23 author groups
• 2002 to 2010
• Y-axis measures
Researcher Bias: The Use of Machine Learning in Software Defect Prediction, Martin Shepperd,
David Bowes, and Tracy Hall, IEEE TRANS on Soft. Eng. , 40(6), JUNE 2014
14. A little theory
• James D. Herbsleb, CMU
• Socio-Technical Coordination
• A predictor for higher defects:
– Groups of programmers working
on similar functions then,
– but do not sharing that expertise
15. Q: How to find expertise groups
within the HPCC community?
A: using data mining
16. Static features and commit history
can act as a cue for expertise
● Our motivation
o “relation between embodiment and language
acquisition by locating the ‘minimal set of
necessary features’ that enable language of any
kind to be learned” - The Philosophy of Expertise
17. Software analytics results:
learn predictors for expertise
● “...counts of the cumulative number of different
developers changing a file over its lifetime can help
to improve defect predictions…”
● “Quantify person's experience with a part of code
using change history of the code”
● “RevFinder, a file location-based code-reviewer
recommendation approach” 
● “30% of its code entities has more than 0.3 of
similarity with at least one developer vocabulary”
 Ostrand, Thomas J., Elaine J. Weyuker, and Robert M. Bell.
"Programmer-based fault prediction." Proceedings of the 6th
International Conference on Predictive Models in Software Engineering.
 Mockus, Audris, and James D. Herbsleb. "Expertise browser: a
quantitative approach to identifying expertise." Proceedings of the
24th international conference on software engineering. ACM, 2002.
 Thongtanunam, Patanamon, et al. "Who should review my code? A
file location-based code-reviewer recommendation approach for
Modern Code Review."Software Analysis, Evolution and Reengineering
(SANER), 2015 IEEE 22nd International Conference on. IEEE, 2015.
 Santos, Katyusco de F., Dalton DS Guerrero, and Jorge CA de
Figueiredo. "Using Developers Contributions on Software Vocabularies
to Identify Experts."Information Technology-New Generations (ITNG),
2015 12th International Conference on. IEEE, 2015.
18. Q: And what data mining suite will we
use to mine data about programmers?
• A: need you ask?
23. Data processing
1. Github repos (for code) ➔ Social media(for years of work)
2. Static code analysis: frequency counts of AST features
(e.g. count loops, returns, var comparisons, map, etc )
3. Bayes classifier
- Features: Nodes of AST
- Algorithms Used: Simple Cart, Random
Forest, Naive Bayes etc.
- Can distinguish expert from novice
•precision= 78% early career
•precision = 74% later career
* Using Weka
25. Current status
The good news
• Can auto-find groups of
• Can do that for very large
– The ECL advantages
The other news
• Seeking larger data sets
• Talking to HackerRank
• Looking at ways to
instrument the HPCC
– Matchmaker tools
– Affinity groups