frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

What an unprocessed photo looks like

https://maurycyz.com/misc/raw_photo/
1128•zdw•9h ago•207 comments

Staying ahead of censors in 2025

https://forum.torproject.org/t/staying-ahead-of-censors-in-2025-what-weve-learned-from-fighting-c...
66•ggeorgovassilis•2h ago•19 comments

Show HN: Z80-μLM, a 'Conversational AI' That Fits in 40KB

https://github.com/HarryR/z80ai
60•quesomaster9000•2h ago•14 comments

You can make up HTML tags

https://maurycyz.com/misc/make-up-tags/
186•todsacerdoti•5h ago•80 comments

My First Meshtastic Network

https://rickcarlino.com/notes/electronics/my-first-meshtastic-network.html
32•rickcarlino•2h ago•7 comments

Show HN: My not-for-profit search engine with no ads, no AI, & all DDG bangs

https://nilch.org
31•UnmappedStack•2h ago•9 comments

Binaries

https://fzakaria.com/2025/12/28/huge-binaries
19•todsacerdoti•2h ago•9 comments

Unity's Mono problem: Why your C# code runs slower than it should

https://marekfiser.com/blog/mono-vs-dot-net-in-unity/
175•iliketrains•10h ago•78 comments

As AI gobbles up chips, prices for devices may rise

https://www.npr.org/2025/12/28/nx-s1-5656190/ai-chips-memory-prices-ram
125•geox•9h ago•139 comments

Software engineers should be a little bit cynical

https://www.seangoedecke.com/a-little-bit-cynical/
172•zdw•10h ago•116 comments

MongoBleed Explained Simply

https://bigdata.2minutestreaming.com/p/mongobleed-explained-simply
169•todsacerdoti•10h ago•64 comments

Researchers discover molecular difference in autistic brains

https://medicine.yale.edu/news-article/molecular-difference-in-autistic-brains/
115•amichail•9h ago•64 comments

Growing up in “404 Not Found”: China's nuclear city in the Gobi Desert

https://substack.com/inbox/post/182743659
753•Vincent_Yan404•1d ago•334 comments

PySDR: A Guide to SDR and DSP Using Python

https://pysdr.org/content/intro.html
166•kklisura•11h ago•8 comments

Line scan camera image processing

https://daniel.lawrence.lu/blog/2025-09-21-line-scan-camera-image-processing/
25•vasco•3d ago•1 comments

Spherical Cow

https://lib.rs/crates/spherical-cow
86•Natfan•8h ago•7 comments

Show HN: My app just won best iOS Japanese learning tool of 2025 award (blog)

https://skerritt.blog/best-japanese-learning-tools-2025-award-show/
99•wahnfrieden•7h ago•14 comments

Fast GPU Interconnect over Radio

https://spectrum.ieee.org/rf-over-fiber
17•montroser•4h ago•1 comments

A bitwise reproducible deep learning framework

https://github.com/microsoft/RepDL
20•noosphr•6d ago•0 comments

Formulaic Delimiters in the Iliad and the Odyssey

https://glthr.com/formulaic-delimiters-in-the-iliad-and-the-odyssey
10•glth•1d ago•3 comments

Mouse: Computer Programming Language

http://mouse.davidgsimpson.com/
6•gappy•2d ago•2 comments

Slaughtering Competition Problems with Quantifier Elimination (2021)

https://grossack.site/2021/12/22/qe-competition.html
47•todsacerdoti•8h ago•0 comments

Finding Jingle Town: Debugging an N64 Game Without Symbols

https://blog.chrislewis.au/finding-jingle-town-debugging-an-n64-game-without-symbols/
26•knackers•5d ago•1 comments

Why I think Valve’s retiring the Steam Deck LCD

https://gardinerbryant.com/why-valves-retiring-the-steam-deck-lcd/
48•Ariarule•4h ago•44 comments

Panoramas of Star Trek Sets

https://mijofr.github.io/st-panorama/
31•jfil•2h ago•3 comments

Why I Disappeared – My week with minimal internet in a remote island chain

https://www.kenklippenstein.com/p/why-i-disappeared
77•eh_why_not•10h ago•75 comments

Learn computer graphics from scratch and for free

https://www.scratchapixel.com
250•theusus•20h ago•26 comments

How to complain (2024)

https://outerproduct.net/trivial/2024-03-25_complain.html
53•ysangkok•8h ago•10 comments

62 years in the making: NYC's newest water tunnel nears the finish line

https://ny1.com/nyc/all-boroughs/news/2025/11/09/water--dep--tunnels-
117•eatonphil•8h ago•71 comments

Fast CVVDP implementation in C

https://github.com/halidecx/fcvvdp
29•todsacerdoti•8h ago•1 comments
Open in hackernews

A Taxonomy of Bugs

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

Comments

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

With the stock eyeroll dismissal phrase.

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