Bug Finding Considered Harmful?
0 comments · testing
- Comments1
0 comments · testing
Story details from Lobsters ↗ · linked article on alperenkeles.com.
Bug Finding Considered Harmful? was first seen on Lobsters · Hottest on Nov 6, 2026. Since then it has appeared in 29 checks on 2 different days. Its best position was #7 of 25, reached on Nov 7, 15:51 UTC. It dropped off the list after Nov 7, 15:51 UTC. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #7 | 2 | 29 | |
| YHacker News · Front page Bug Finding Considered Harmful? | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
From the [linked Z3 thread](https://github.com/Z3Prover/z3/issues/4461): >You only want these issues fixed so you can find your "next batch", not because you've building something awesome that needs this "broken" functionality. Is an unfortunate dynamic that plays out in open source. Also: >Localize and even submit…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 7, 15:51 UTC, after 2 days of trending.
#7 on Lobsters · Hottest, on Nov 7, 15:51 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 6, 2026 and has been on the list on 2 days (29 checks) since.