nitter
Mark Finkle
@mfinkle
12 Sep 2016
Tool idea: Code coverage, but for crashes. How many lines of your codebase has crashed at some point.
2
2
7
L. David Baron @dbaron@w3c.social
@davidbaron
12 Sep 2016
Replying to
@mfinkle
Would be very distorted by crashes due to bad RAM/disk/etc.
Sep 12, 2016 · 5:23 PM UTC
1
Mark Finkle
@mfinkle
12 Sep 2016
Replying to
@davidbaron
Shade by crash quantity. Darker lines = more crashes. More a fun idea to show that all code will find a way to crash at scale.