corpus.blog
41554 blogs · 4,417,066 posts Claim your blog
Record · corpus.blog/posts/01a0cce4-0139-716b-9d88-548314a8d5ff

Modelling time to next reported fault

shape-of-code.com · published 4 January 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at shape-of-code.com Wayback capture
0blogs citing
First cited
—
Most recent
—
Rank this month
not ranked
Links from this post
12
Words captured
1,021

Cited by

No blog we hold has cited this post yet.

Links from this post

Link
Host
Top, must-read paper on software fault analysis Read at the source ↗
shape-of-code.com
Extracting information from duplicate fault reports Read at the source ↗
shape-of-code.com
https://www.shape-of-code.com/code-data/dup-fault-info.tgz
shape-of-code.com
Half-life of software as a service, services Read at the source ↗
shape-of-code.com
Cost-effectiveness decision for fixing a known coding mistake Read at the source ↗
shape-of-code.com
https://en.wikipedia.org/wiki/Cumulative_distribution_function
en.wikipedia.org
https://chatgpt.com/share/695ac398-ed94-800f-a707-f5231f4af78a
chatgpt.com
https://x.com/i/grok/share/aNpJBex8uVto1zvQXkrhhbJ0t
x.com
https://en.wikipedia.org/wiki/Hypergeometric_function
en.wikipedia.org
https://www.shape-of-code.com/code-data/between-fault-time.deepseek
shape-of-code.com
Program fault reports are caused by its users Read at the source ↗
shape-of-code.com
Almost all published analysis of fault data is worthless Read at the source ↗
shape-of-code.com