• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Reviewing Code- The Naive Bayes Way
 

Reviewing Code- The Naive Bayes Way

on

  • 1,013 views

If you have nothing better to do and feel like hearing 2 programmers go on about mining intelligence from code metrics, watch this. Mark Needham and I spent some time after work learning some training ...

If you have nothing better to do and feel like hearing 2 programmers go on about mining intelligence from code metrics, watch this. Mark Needham and I spent some time after work learning some training algorithms and building a tool that will help a software company identify programmers that they wish to recruit :)

Statistics

Views

Total Views
1,013
Views on SlideShare
995
Embed Views
18

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 18

http://blog.ashwinraghav.com 11
http://ashwinraghav.wordpress.com 7

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Reviewing Code- The Naive Bayes Way Reviewing Code- The Naive Bayes Way Presentation Transcript

    • The Naïve Bayes approach to code reviews Mark Needham (Markeshwa) Ashwin Raghav (Ashley)
    •  
    • Why don’t we use code metrics to do code reviews?
    • Why don’t we use code metrics to do code reviews? We need a human to do it - quality of code isn’t only about code metrics, it’s a subjective thing
    • Why don’t we use code metrics to do code reviews? We need a human to do it - quality of code isn’t only about code metrics, it’s a subjective thing But what if we based it on the outcome of code reviews that have already been done? It’d be more consistent and less effort!
    • Why don’t we use code metrics to do code reviews? We need a human to do it - quality of code isn’t only about code metrics, it’s a subjective thing But what if we based it on the outcome of code reviews that have already been done? It’d be more consistent and less effort! Let’s do it!
    • SIQ Initiative “ We think that we can help people better understand the internal quality of software. We plan to do this by employing visualisation techniques for metrics and other characteristics of software. Our approach is reflective and we want to evolve our visualisations towards a commonly useful set.”
    • Erik Doernenburg
    • Notes C API Erik’s shell script Metrics + code Mercurial Repository Java NCSS Code Reviews
    • Metrics + code Some sort of algorithm Would a code review be passed/pursued?
    • Naïve Bayes Classifier “ A simple probabilistic classifier based on applying Bayes' theorem (from Bayesian statistics) with strong (naive) independence assumptions. In simple terms, a naive Bayes classifier assumes that the presence (or absence) of a particular feature of a class is unrelated to the presence (or absence) of any other feature.”
    • Metrics + class Bayes Algorithm Training
    • Metrics + class Bayes Algorithm Training Metrics Bayes Algorithm Predicting Class