Stop Hardcoding Your Timeouts
0 comments · a11y, practices
- Comments26
0 comments · a11y, practices
Story details from Lobsters ↗ · linked article on alfy.blog.
Stop Hardcoding Your Timeouts was first seen on Lobsters · Hottest on Nov 2, 2026. Since then it has appeared in 80 checks on 3 different days. Its best position was #3 of 25, reached on Nov 3, 01:21 UTC. It dropped off the list after Nov 4, 11:51 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
If you _actually fucking test timeouts properly_, you'll quickly (ahem) realize why they need to be injected instead of hardcoded!
I do actually appreciate go's new timetravel testing; with some setup you can make time fast forward under the condition that all other threads are blocked, then you can even test multi-minute timeouts in under a second total. Just fast forward time to "just before timeout", check there is none, then forward past the…
https://github.com/vercel-labs/skills/issues/278 (by someone else) quite ridiculous—just skim its first two comments, absurd amounts of unnecessary detail and a preposterous solution, all very obviously slop. All that needed to be said was “cloning repositories can take arbitrarily long, so putting a 60 second…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 4, 11:51 UTC, after 3 days of trending.
#3 on Lobsters · Hottest, on Nov 3, 01:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 2, 2026 and has been on the list on 3 days (80 checks) since.