frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

I Moved My Digital Stack to Europe

https://monokai.com/articles/how-i-moved-my-digital-stack-to-europe/
201•monokai_nl•1h ago•112 comments

Preserving Fisher-Price Pixter

https://dmitry.gr/?r=05.Projects&proj=37.%20Pixter
58•dmitrygr•2d ago•2 comments

New stainless steel can survive conditions for hydrogen production in seawater

https://www.sciencedaily.com/releases/2026/05/260510030950.htm
120•HardwareLust•2d ago•37 comments

Restore full BambuNetwork support for Bambu Lab printers

https://github.com/FULU-Foundation/OrcaSlicer-bambulab
514•Murfalo•15h ago•224 comments

Deterministic Fully-Static Whole-Binary Translation Without Heuristics

https://arxiv.org/abs/2605.08419
229•matt_d•8h ago•54 comments

Googlebook

https://googlebook.google/
831•tambourine_man•19h ago•1364 comments

Web Server on a Nintendo Wii

http://wii.sjmulder.nl/
30•adunk•3d ago•1 comments

Substrate (YC S24) Is Hiring a Technical Success Manager

https://www.ycombinator.com/companies/substrate/jobs/T2fMBhD-technical-success-manager
1•kunle•58m ago

Show HN: Needle: We Distilled Gemini Tool Calling into a 26M Model

https://github.com/cactus-compute/needle
517•HenryNdubuaku•18h ago•156 comments

The Boring Part of Bell Labs (2025)

https://acesounderglass.com/2025/11/15/the-boring-part-of-bell-labs/
49•surprisetalk•4d ago•6 comments

Using OR-Tools CP-SAT for Scheduling Problems

https://atalaykutlay.com/or-tools-cp-sat-for-scheduling-problems.html
15•akutlay•1h ago•1 comments

How to make your text look futuristic (2016)

https://typesetinthefuture.com/2016/02/18/futuristic/
404•_vaporwave_•16h ago•52 comments

Cost of enum-to-string: C++26 reflection vs. the old ways

https://vittorioromeo.com/index/blog/refl_enum_to_string.html
19•sagacity•4h ago•7 comments

Why senior developers fail to communicate their expertise

https://www.nair.sh/guides-and-opinions/communicating-your-expertise/why-senior-developers-fail-t...
644•nilirl•21h ago•284 comments

CERT is releasing six CVEs for serious security vulnerabilities in dnsmasq

https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2026q2/018471.html
338•chizhik-pyzhik•18h ago•174 comments

Scrcpy v4.0

https://github.com/Genymobile/scrcpy/releases/tag/v4.0
248•xnx•16h ago•39 comments

When “idle” isn't idle: how a Linux kernel optimization became a QUIC bug

https://blog.cloudflare.com/quic-death-spiral-fix/
117•sbulaev•13h ago•15 comments

An idiot's guide to lead optimisation for proteins

https://magnusross.github.io/posts/protein-lead-optimisation-1/
3•magni121•2d ago•0 comments

The vi family

https://lpar.ATH0.com/posts/2026/05/the-vi-family/
210•hggh•1w ago•132 comments

Traceway: MIT-licensed observability stack you can self-host in ~90s

https://github.com/tracewayapp/traceway
128•sebakubisz•2d ago•21 comments

Rendering the Sky, Sunsets, and Planets

https://blog.maximeheckel.com/posts/on-rendering-the-sky-sunsets-and-planets/
496•ibobev•23h ago•39 comments

SecurityBaseline.eu

https://internetcleanup.foundation/2026/05/european-governments-3000-tracking-sites-1000-phpmyadm...
188•aequitas•5h ago•97 comments

Quack: The DuckDB Client-Server Protocol

https://duckdb.org/2026/05/12/quack-remote-protocol
317•aduffy•19h ago•66 comments

Kraftwerk's radical 1976 track

https://www.bbc.com/culture/article/20260511-kraftwerks-radical-1976-track-radioactivity-became-a...
187•tcp_handshaker•13h ago•154 comments

My graduation cap runs Rust

https://ericswpark.com/blog/2026/2026-05-12-my-graduation-cap-runs-rust/
175•ericswpark•12h ago•66 comments

The Future of Obsidian Plugins

https://obsidian.md/blog/future-of-plugins/
403•xz18r•21h ago•148 comments

Reimagining the mouse pointer for the AI era

https://deepmind.google/blog/ai-pointer/
223•devhouse•19h ago•187 comments

What if there was no BASIC in EndBASIC?

https://blogsystem5.substack.com/p/no-basic-in-endbasic
32•rbanffy•4d ago•10 comments

As researchers age, they produce less disruptive work

https://nautil.us/is-this-why-science-advances-one-funeral-at-a-time-1280650
97•Brajeshwar•19h ago•95 comments

Fc, a lossless compressor for floating-point streams

https://github.com/xtellect/fc
82•enduku•3d ago•27 comments
Open in hackernews

A Taxonomy of Bugs

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

Comments

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

With the stock eyeroll dismissal phrase.

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