FixCache

Dev tools

code review bot

SHOW HN2020

40points
11comments
#1,205of 3,028 in 2020
Top 40%of 2020 by points

How HN took it

CuriousMostly questions and neutral comments

0 positive, 3 neutral or asking, 1 mixed, 2 critical, out of 6 comments about the project. Thread score -0.13.

Idea: 0 for, 2 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Interesting idea based on a published paper

    From 1 comment
    • Looks really cool, although it's a shame the description isn't a bit more "plain language" - a simple summary of what it is intended for, before going into jargon would help…
      nmstoker on HN

Objections

  • Description is jargon-heavy and unclear about purpose

    From 2 comments
    • Looks really cool, although it's a shame the description isn't a bit more "plain language" - a simple summary of what it is intended for, before going into jargon would help…
      nmstoker on HN
    • I read the whole README but have no idea what this does. Is it letting you know when you change files that have had a large number of bug fixes recently? With the assumption that…
      remram on HN
  • Bug-fix locations may be biased by reporting and management attention

    From 1 comment
    • Are you sure it's not discovering bad developers? Maybe critical areas, e.g. that have the same amount of bugs as the rest but are complained about more? (since the algorithm can…
      remram on HN
  • Keyword matching may miss bugs that GitHub issue or PR metadata would catch

    From 1 comment
    • Based on the existence of the config option "FIX_KEY_WORDS", it seems like this detects bugs just using keyword matching? Github also tracks when issues are fixed by commits (and…
      rcthompson on HN

Requests

  • Plain-language README describing intended use and value

    From 1 comment
    • Looks really cool, although it's a shame the description isn't a bit more "plain language" - a simple summary of what it is intended for, before going into jargon would help…
      nmstoker on HN
  • Pluggable hook to define what counts as a bug fix

    From 1 comment
    • One way to support this would be to make FixCache support an optional hook that would be responsible for deciding if a given commit was a bug fix or not. Naively, it could have…
      shoo on HN
  • Use GitHub issue or PR metadata to detect fixes

    From 1 comment
    • Based on the existence of the config option "FIX_KEY_WORDS", it seems like this detects bugs just using keyword matching? Github also tracks when issues are fixed by commits (and…
      rcthompson on HN

Questions

  • How is spatial locality defined

    From 1 comment
    • Neato. How is "spatial locality" defined? Just distance in the filesystem tree?
      bjackman on HN
  • Why recently fixed files would be more bug-prone

    From 1 comment
    • I read the whole README but have no idea what this does. Is it letting you know when you change files that have had a large number of bug fixes recently? With the assumption that…
      remram on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/24363326)