frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Search engines alternatives now that Google isn't Google anymore

https://techcrunch.com/2026/05/21/six-search-engines-worth-trying-now-that-google-isnt-really-goo...
88•elorant•46m ago•55 comments

Magnifica Humanitas (Encyclical Letter)

https://www.vatican.va/content/leo-xiv/en/encyclicals/documents/20260515-magnifica-humanitas.html
259•theletterf•3h ago•82 comments

Leave Me Behind

http://androidessence.com/leave-me-behind/
41•mooreds•1h ago•13 comments

GPT Guesses Between 1 and 100

https://github.com/exmergo/research-chatgpt-guesses-between-1-and-100
54•adunk•1h ago•37 comments

IBM Spins Off the First Pure-Play Quantum Chip Foundry

https://futurumgroup.com/insights/2-billion-chips-act-investment-in-quantum-bets-on-ibms-300mm-su...
36•rbanffy•3h ago•6 comments

Didgeridoo playing as alternative treatment for obstructive sleep apnoea (2006)

https://pmc.ncbi.nlm.nih.gov/articles/PMC1360393/
187•kelseyfrog•2d ago•83 comments

Show HN: Audiomass – a free, open-source multitrack audio editor for the web

https://audiomass.co/?multitrack=1
418•pantelisk•21h ago•88 comments

Show HN: Geomatic – a command-driven geometry studio enabled with autodiff

https://www.tinyvolt.com/geomatic
34•nivter•4h ago•9 comments

you_can::turn_off_the_borrow_checker

https://docs.rs/you-can/latest/you_can/attr.turn_off_the_borrow_checker.html
32•striking•2d ago•6 comments

AI errno(2) values

https://www.netmeister.org/blog/ai-errno.html
31•zdw•2d ago•6 comments

DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

https://esengine.github.io/DeepSeek-Reasonix/
607•Alifatisk•1d ago•253 comments

Migrating from Go to Rust

https://corrode.dev/learn/migration-guides/go-to-rust/
331•jabits•18h ago•325 comments

White Rabbit – sub-nanosecond synchronization for large distributed systems

https://ohwr.org/projects/white-rabbit/
134•michaelsbradley•2d ago•29 comments

Jira Is Turing-Complete

https://seriot.ch/computation/jira.html
215•vinhnx•9h ago•95 comments

Bytecode VMs in surprising places (2024)

https://dubroy.com/blog/bytecode-vms-in-surprising-places/
55•azhenley•2d ago•20 comments

Notes about reading messages with the Python email packages

https://utcc.utoronto.ca/~cks/space/blog/python/EmailPackagesNotes
28•ankitg12•5d ago•1 comments

I spent 50 hours drawing a line graph

https://www.dougmacdowell.com/50-hours-to-draw-some-lines.html
574•dougdude3339•3d ago•96 comments

Bug 1950764: Work Around Crash on Intel Raptor Lake CPU

https://phabricator.services.mozilla.com/D301917
121•luu•2d ago•40 comments

A fundamental principle of aeronautical engineering has been overturned

https://www.wired.com/story/a-fundamental-principle-of-aeronautical-engineering-has-been-overturned/
190•littlexsparkee•18h ago•91 comments

Rising seas will swallow New Orleans. People need to start relocating now

https://www.cnn.com/2026/05/25/climate/new-orleans-sea-level-rise-relocation
29•breve•3h ago•11 comments

Microsoft open-sources “the earliest DOS source code discovered to date”

https://arstechnica.com/gadgets/2026/04/microsoft-open-sources-the-earliest-dos-source-code-disco...
485•DamnInteresting•1d ago•174 comments

I love my Bluetooth keyboard

https://liquidbrain.net/blog/i-love-my-bluetooth-keyboard/
113•evakhoury•2d ago•116 comments

Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

https://arxiv.org/abs/2605.06445
258•wek•1d ago•151 comments

Defeating Git Rigour Fatigue with Jujutsu

https://ikesau.co/blog/defeating-git-rigour-fatigue-with-jujutsu/
144•ikesau•18h ago•147 comments

Scientists solve 200-year-old puzzle of how tobacco plants make nicotine

https://www.york.ac.uk/news-and-events/news/2026/research/200-year-old-puzzle-tobacco-plants-nico...
104•sohkamyung•3d ago•38 comments

C constructs that still don't work in C++

https://lospino.so/blog/c-constructs-that-still-dont-work-in-cpp/
98•jalospinoso•3d ago•91 comments

Building Pi with Pi

https://lucumr.pocoo.org/2026/5/24/pi-oss/
125•mplanchard•19h ago•102 comments

Childhood Computing

https://susam.net/childhood-computing.html
223•blenderob•1d ago•107 comments

Memory has grown to nearly two-thirds of AI chip component costs

https://epoch.ai/data-insights/ai-chip-component-cost-shares
406•intelkishan•20h ago•431 comments

Scammers are abusing an internal Microsoft account to send spam links

https://techcrunch.com/2026/05/21/scammers-are-abusing-an-internal-microsoft-account-to-send-spam/
297•spike021•1d ago•171 comments
Open in hackernews

A Taxonomy of Bugs

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

Comments

mannykannot•1y 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•1y 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•1y 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•1y 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•1y 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•1y ago
Congratz, you've invented regression tests.
quantadev•1y 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•1y 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•1y ago
> And my intentions were not to belittle, but to praise.

With the stock eyeroll dismissal phrase.

quantadev•1y 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•1y ago
Good thing he has knights in shining armor like you to defend him from my nasty insults.
quantadev•1y ago
Good thing you can admit what you were doing.
bheadmaster•1y ago
Good thing you can understand sarcasm.
quantadev•1y ago
but your sarcasm was truthful.
bheadmaster•1y ago
but it wasn't.
quantadev•1y ago
Well in that case...Congratz, you've invented sarcasm.
bheadmaster•1y ago
Congratz, you've invented obnoxiousness.
quantadev•1y ago
Not "independently reinvented" ?
readthenotes1•1y ago
I was aware of unit testing before it had a name ... Desperation is the mother of intervention
quantadev•1y ago
Yep, I "independently reinvent" the wheel every day I guess, because I, ya know...use wheels.
alilleybrinker•1y 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•1y 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•1y 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•1y ago
John Carmack uses a debugger