frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

A 26,000-year astronomical monument hidden in plain sight (2019)

https://longnow.org/ideas/the-26000-year-astronomical-monument-hidden-in-plain-sight/
371•mkmk•8h ago•81 comments

Are arrays functions?

https://futhark-lang.org/blog/2026-01-16-are-arrays-functions.html
56•todsacerdoti•1d ago•33 comments

California is free of drought for the first time in 25 years

https://www.latimes.com/california/story/2026-01-09/california-has-no-areas-of-dryness-first-time...
276•thnaks•4h ago•131 comments

Claude Chill: Fix Claude Code's Flickering in Terminal

https://github.com/davidbeesley/claude-chill
101•behnamoh•3h ago•53 comments

Instabridge has acquired Nova Launcher

https://novalauncher.com/nova-is-here-to-stay
144•KORraN•8h ago•102 comments

Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

https://github.com/mastra-ai/mastra
95•calcsam•10h ago•37 comments

The Unix Pipe Card Game

https://punkx.org/unix-pipe-game/
186•kykeonaut•10h ago•58 comments

Provably unmasking malicious behavior through execution traces

https://arxiv.org/abs/2512.13821
26•PaulHoule•4h ago•3 comments

I'm addicted to being useful

https://www.seangoedecke.com/addicted-to-being-useful/
510•swah•16h ago•259 comments

Which AI Lies Best? A game theory classic designed by John Nash

https://so-long-sucker.vercel.app/
53•lout332•5h ago•36 comments

Running Claude Code dangerously (safely)

https://blog.emilburzo.com/2026/01/running-claude-code-dangerously-safely/
292•emilburzo•15h ago•233 comments

Who owns Rudolph's nose?

https://creativelawcenter.com/copyright-rudolph-reindeer/
16•ohjeez•2h ago•5 comments

Building Robust Helm Charts

https://www.willmunn.xyz/devops/helm/kubernetes/2026/01/17/building-robust-helm-charts.html
32•will_munn•1d ago•0 comments

Unconventional PostgreSQL Optimizations

https://hakibenita.com/postgresql-unconventional-optimizations
275•haki•12h ago•45 comments

The challenges of soft delete

https://atlas9.dev/blog/soft-delete.html
90•buchanae•5h ago•61 comments

Catching API regressions with snapshot testing

https://kreya.app/blog/api-snapshot-testing/
10•CommonGuy•5d ago•0 comments

Our approach to age prediction

https://openai.com/index/our-approach-to-age-prediction/
65•pretext•7h ago•131 comments

Maintenance: Of Everything, Part One

https://press.stripe.com/maintenance-part-one
75•mitchbob•8h ago•13 comments

The world of Japanese snack bars

https://www.bbc.com/travel/article/20260116-inside-the-secret-world-of-japanese-snack-bars
110•rmason•5h ago•67 comments

Apples, Trees, and Quasimodes

https://systemstack.dev/2025/09/humane-computing/
29•entaloneralie•3d ago•2 comments

Dockerhub for Skill.md

https://skillregistry.io/
25•tomaspiaggio12•11h ago•16 comments

IP Addresses Through 2025

https://www.potaroo.net/ispcol/2026-01/addr2025.html
161•petercooper•13h ago•123 comments

Lunar Radio Telescope to Unlock Cosmic Mysteries

https://spectrum.ieee.org/lunar-radio-telescope
14•rbanffy•4h ago•1 comments

Cloudflare zero-day: Accessing any host globally

https://fearsoff.org/research/cloudflare-acme
62•2bluesc•10h ago•14 comments

Show HN: macOS native DAW with Git branching model

https://www.scratchtrackaudio.com
20•hpen•3h ago•16 comments

Show HN: TopicRadar – Track trending topics across HN, GitHub, ArXiv, and more

https://apify.com/mick-johnson/topic-radar
20•MickolasJae•12h ago•3 comments

Show HN: Agent Skills Leaderboard

https://skills.sh
41•andrewqu•5h ago•16 comments

Fast Concordance: Instant concordance on a corpus of >1,200 books

https://iafisher.com/concordance/
35•evakhoury•4d ago•3 comments

Nvidia Stock Crash Prediction

https://entropicthoughts.com/nvidia-stock-crash-prediction
360•todsacerdoti•11h ago•301 comments

Verizon starts requiring 365 days of paid service before it will unlock phones

https://arstechnica.com/tech-policy/2026/01/verizon-starts-requiring-365-days-of-paid-service-bef...
17•voxadam•1h ago•3 comments
Open in hackernews

A Taxonomy of Bugs

https://ruby0x1.github.io/machinery_blog_archive/post/a-taxonomy-of-bugs/index.html
52•lissine•8mo ago

Comments

mannykannot•8mo ago
Here's a step 0 for your debugging strategy: spend a few minutes thinking about what could account for the bug. Prior to its occurrence, you are thinking about what could go wrong, but now you are thinking about what did go wrong, which is a much less open-ended question.
marginalia_nu•8mo ago
I've had large success by treating the bug as a binary search problem as soon as I identify an initial state that's correct and a terminal state that's incorrect. It seems like a lot of work, but that's underestimating just how fast binary searches are.

Depends of course on the nature of the bug whether it's a good strategy.

readthenotes1•8mo ago
I was such a bad developer that I realized I had to automate the re-running of parts of the system to find the bugs.

Of course, the code I wrote to exercise the code I wrote had bugs, but usually I wouldn't make offsetting errors.

It didn't fix all the problems I made, but it helped. And it helped to have the humility when trying to fix code to realize I wouldn't get it the first time, so should automate replication

bheadmaster•8mo ago
> I had to automate the re-running of parts of the system to find the bugs

Congratz, you've independently invented integration tests.

tough•8mo ago
I don't always test but adding a lil test after finding and fixing a bug so you don't end up there again a second time is a great practice
bheadmaster•8mo ago
Congratz, you've invented regression tests.
quantadev•8mo ago
Congrats, you've found someone who failed to invoke a buzzword that you know.

EDIT: But Acktshally `the code I wrote to exercise the code I wrote` is a description of "Unit Testing", not integration testing.

bheadmaster•8mo ago
Unit/integration tests are anything but a buzzword. And my intentions were not to belittle, but to praise.

Some actions simply make so much sense to do, that any sensible person (unaware of the concept) will start doing them given enough practice, and in process they "reinvent" a common method.

keybored•8mo ago
> And my intentions were not to belittle, but to praise.

With the stock eyeroll dismissal phrase.

quantadev•8mo ago
As far as you knew that guy was aware what Unit Testing was since well before you were born. lol. I'm sure he appreciates all your nice compliments.
bheadmaster•8mo ago
Good thing he has knights in shining armor like you to defend him from my nasty insults.
quantadev•8mo ago
Good thing you can admit what you were doing.
bheadmaster•8mo ago
Good thing you can understand sarcasm.
quantadev•8mo ago
but your sarcasm was truthful.
bheadmaster•8mo ago
but it wasn't.
quantadev•8mo ago
Well in that case...Congratz, you've invented sarcasm.
bheadmaster•8mo ago
Congratz, you've invented obnoxiousness.
quantadev•8mo ago
Not "independently reinvented" ?
readthenotes1•8mo ago
I was aware of unit testing before it had a name ... Desperation is the mother of intervention
quantadev•8mo ago
Yep, I "independently reinvent" the wheel every day I guess, because I, ya know...use wheels.
alilleybrinker•8mo ago
There's also the Common Weakness Enumeration (CWE), a long-running taxonomy of software weaknesses (meaning types of bugs).

https://cwe.mitre.org/

Animats•8mo ago
The Third-Party Bug

Is the party responsible for the bug bigger than you? If yes, it's your problem. If no, it's their problem.

marginalia_nu•8mo ago
A subcategory of the design flaw I find quite a lot is the case where the code works exactly as intended, it's just not having the desired effect because of some erroneous premise.
djmips•8mo ago
John Carmack uses a debugger