frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

There's a ridiculous amount of tech in a disposable vape

https://blog.jgc.org/2026/01/theres-ridiculous-amount-of-tech-in.html
185•abnercoimbre•1d ago•151 comments

1000 Blank White Cards

https://en.wikipedia.org/wiki/1000_Blank_White_Cards
76•eieio•3h ago•12 comments

ASCII Clouds

https://caidan.dev/portfolio/ascii_clouds/
105•majkinetor•4h ago•20 comments

Every GitHub object has two IDs

https://www.greptile.com/blog/github-ids
182•dakshgupta•14h ago•46 comments

A 40-line fix eliminated a 400x performance gap

https://questdb.com/blog/jvm-current-thread-user-time/
219•bluestreak•7h ago•45 comments

The Gleam Programming Language

https://gleam.run/
54•Alupis•3h ago•14 comments

Show HN: OSS AI agent that indexes and searches the Epstein files

https://epstein.trynia.ai/
50•jellyotsiro•4h ago•14 comments

Show HN: Cachekit – High performance caching policies library in Rust

https://github.com/OxidizeLabs/cachekit
26•failsafe•4h ago•0 comments

vLLM large scale serving: DeepSeek 2.2k tok/s/h200 with wide-ep

https://blog.vllm.ai/2025/12/17/large-scale-serving.html
81•robertnishihara•14h ago•7 comments

The $LANG Programming Language

148•dang•6h ago•27 comments

Show HN: The Tsonic Programming Language

https://tsonic.org
15•jeswin•13h ago•3 comments

Show HN: 1D-Pong Game at 39C3

https://github.com/ogermer/1d-pong
7•oger•2d ago•0 comments

The truth behind the 2026 J.P. Morgan Healthcare Conference

https://www.owlposting.com/p/the-truth-behind-the-2026-jp-morgan
170•abhishaike•12h ago•34 comments

The Emacs Widget Library: A Critique and Case Study

https://www.d12frosted.io/posts/2025-11-26-emacs-widget-library
41•whacked_new•2d ago•9 comments

No management needed: anti-patterns in early-stage engineering teams

https://www.ablg.io/blog/no-management-needed
142•tonioab•11h ago•162 comments

Stop using natural language interfaces

https://tidepool.leaflet.pub/3mcbegnuf2k2i
41•steveklabnik•4h ago•5 comments

Sei (YC W22) Is Hiring a DevOps Engineer (India/In-Office/Chennai/Gurgaon)

https://www.ycombinator.com/companies/sei/jobs/Rn0KPXR-devops-platform-ai-infrastructure-engineer
1•ramkumarvenkat•5h ago

Are two heads better than one?

https://eieio.games/blog/two-heads-arent-better-than-one/
146•evakhoury•14h ago•43 comments

The Tulip Creative Computer

https://github.com/shorepine/tulipcc
206•apitman•13h ago•47 comments

Handling secrets (somewhat) securely in shells

https://linus.schreibt.jetzt/posts/shell-secrets.html
36•todsacerdoti•4d ago•17 comments

AI generated music barred from Bandcamp

https://old.reddit.com/r/BandCamp/comments/1qbw8ba/ai_generated_music_on_bandcamp/
706•cdrnsf•12h ago•497 comments

Agonist-Antagonist Myoneural Interface

https://www.media.mit.edu/projects/agonist-antagonist-myoneural-interface-ami/overview/
51•kaycebasques•5d ago•3 comments

Scott Adams has died

https://www.youtube.com/watch?v=Rs_JrOIo3SE
875•ekianjo•15h ago•1381 comments

How to make a damn website (2024)

https://lmnt.me/blog/how-to-make-a-damn-website.html
172•birdculture•13h ago•54 comments

Why we built our own background agent

https://builders.ramp.com/post/why-we-built-our-background-agent
84•jrsj•1d ago•10 comments

April 9, 1940 a Dish Best Served Cold

https://todayinhistory.blog/2021/04/09/april-9-1940-a-dish-best-served-cold/
7•vinnyglennon•4d ago•2 comments

Exa-d: How to store the web in S3

https://exa.ai/blog/exa-d
18•willbryk•5h ago•0 comments

When hardware goes end-of-life, companies need to open-source the software

https://www.marcia.no/words/eol
248•Marciplan•7h ago•77 comments

Show HN: Nogic – VS Code extension that visualizes your codebase as a graph

https://marketplace.visualstudio.com/items?itemName=Nogic.nogic
99•davelradindra•11h ago•36 comments

We can't have nice things because of AI scrapers

https://blog.metabrainz.org/2025/12/11/we-cant-have-nice-things-because-of-ai-scrapers/
357•LorenDB•8h ago•187 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