frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
1008•speedping•7h ago•464 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
394•gmays•7h ago•272 comments

Inside Deutsche Bank

https://www.inside-db.com/
503•gyre007•7h ago•182 comments

AI agents ask better questions than KPMG accountants in audit trial

https://europeanbusinessmagazine.com/ai-agents-better-questions-kpmg/
302•Betelbuddy•7h ago•138 comments

DaisyRose-27B: 1,200-task RL took Qwen3.8 from 5.6% to 12% on Terminal-Bench 4.1

https://www.radixark.com/blog/daisyrose-27b
98•de_sty•3h ago•26 comments

DNS resolvers are the wrong place to fight piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
551•ritzaco•9h ago•204 comments

Gemini 4 Neon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
295•yigitdemirag•1h ago•286 comments

Cuttlefish on Mac: Android's Virtual Device Framework on Apple Silicon

https://engineering.fb.com/2026/11/13/android/cuttlefish-on-mac/
21•acossta•3d ago•3 comments

Advancing chip design with OpenAI models

https://openai.com/index/advancing-chip-design-with-our-models/
137•vighneshiyer•5h ago•76 comments

The Cambridge Dictionary has named ‘human’ as the Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
220•DeepLogin•8h ago•164 comments

Show HN: ExitPath – Open-source ways out of Slack, Notion and Microsoft 365

https://exitpath-ruddy.vercel.app/
134•zerocool0101•7h ago•36 comments

Show HN: Take Voyager 1 apart, down to a single memory chip

https://rshekhar.com/voyager/
134•raj-shekhar•6h ago•28 comments

A Collage Showing 49 Drill Holes Made by NASA's Curiosity Mars Rover

https://science.nasa.gov/photojournal/a-collage-showing-49-drill-holes-made-by-nasas-curiosity-ma...
11•wawayanda•2d ago•2 comments

The Magic of Partial Evaluation

https://jimmyhmiller.com/magic-of-partial-evaluation
83•aray07•4h ago•20 comments

Genie 4 is now available

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/genie-4-now-available-p...
165•leumon•4h ago•138 comments

CrossPoint Reader

https://crosspointreader.com
85•kristianpaul•6h ago•47 comments

The First Revolver: How We Got from Blackbeard's Six Pistols to the Six-Shooter

https://americanhandgunner.com/handguns/revolvers/the-first-revolver/
50•bushwart•3d ago•31 comments

KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312)

https://www.cve.org/CVERecord?id=CVE-2026-99312
164•Kozmik1•7h ago•113 comments

Show HN: Mastra Factory, the open-source software factory we use to build Mastra

74•codekarate•6h ago•25 comments

Search Browser – Minimalist WebKit browser with Chrome extension support

https://searchbrowser.app/
46•rsaz•3h ago•28 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
127•ibobev•8h ago•41 comments

GTA6-like as a 942Kb UEFI bootable image

https://github.com/eklavya-raj/gta6-uefi
9•bananaboy•51m ago•3 comments

Sexp Matrix

https://lisper.cc/ideas/entangle.html
26•todsacerdoti•3h ago•7 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
293•frenchmajesty•13h ago•50 comments

A Primer on Fourier Series (2025)

https://arxiv.org/abs/2510.18203
102•teleforce•8h ago•27 comments

Why educational system is broken

https://keycybermonk.com/edu
8•makosst•35m ago•2 comments

F-22 Next-Generation micro–Data Transfer Cartridge (mDTC)

https://sam.gov/workspace/contract/opp/8948e8601e964c6aba9c801eee16b1be/view
137•birdboat00•7h ago•101 comments

Horizon Labs Report

https://horizon-labs.ai/
16•gmays•3h ago•3 comments

Evidence (YC S21) Is Hiring

https://www.ycombinator.com/companies/evidence/jobs/1xb9PpP-founding-gtm-lead
1•amcaskill•11h ago

A live service duress prototype

https://github.com/Ymsniper/vault-share
13•Ymsniper•3d ago•2 comments
Open in hackernews

Throwaway Code: Don't recycle, throw it away (2017)

https://www.sung.codes/blog/2017/throwaway-code-dont-recycle-throw-away
26•sails•1y ago

Comments

RedShift1•1y ago
It'll be a cold day in hell before I start throwing away my 80+ "New" notepad++ tabs.
notTooFarGone•1y ago
i feel called out.

I had to manage my 350 notepad++ new tabs as I migrated to a new PC - it was not pretty.

mehulashah•1y ago
There’s something beautiful about not being riddled with previous artifacts and starting clean with how you imagine you want to build your system. If the system is large enough, you can’t do it that often.
gherkinnn•1y ago
It is a mistake to believe that the code written is the only valuable artefact.

What you've learned along the way is so much more important.

eternityforest•1y ago
I usually find most of the learning happens a year later when I see if my approach is maintainable and handles new requirements.

When I'm actually coding, I'm usually not learning as much, because I'm generally intentionally choosing boring tech everyone already knows.

Most of the learning is less about deeply internalizing concepts and more about things like new features in the Python stdlib.

gitroom•1y ago
Ive got a million messy files saved up, honestly, even when I know just letting go could help me think clearer. Ever wonder if holding onto old stuff slows you down or actually helps you get smarter over time?
1dom•1y ago
I don't think the author is necessarily advocating the throwing away of code here, they're advocating the value of being able to rapidly prototype and move on from seemingly incomplete things.

The whole value proposition of the digital world is that we can store and manipulate it for virtually nothing: there isn't the same cost to having digital stuff, and so there isn't the same gains from throwing it away IMO.

athrowaway3z•1y ago
Create a ~/Archive and throw it in there.

A quick grep every blue moon can be faster than wrangling a LLM into place, and as an added bonus you can look back and laugh at how big of an idiot you were.

klabb3•1y ago
In my experience, if you have a medium sized task with multiple unknowns, it is best to prototype aggressively without a thought about quality, and then start a second iteration with quality in mind. The purpose of the prototyping is learning.

It’s faster (yes) than prototype-then-fixup. Why? Because the ”live refactor” is harder than the greenfield writing phase. The new knowledge often makes the impl straightforward.

It’s also better quality than design-then-build. The optimal architecture and modularization change with knowledge increase, which is best to get via experience. You can design fully upfront but it’s riddled with analysis paralysis - it’s notoriously hard (and slow) to predict unknowns.

Sounds like good advice? Well, the hardest part isn’t to follow it – it’s to know upfront what size of task it is. If it turns out to be easier, you waste a bit of work (prototype-fixup is faster). However, if it’s bigger than you thought – you’re in the best possible position to break down the new problem into subtasks, with no wasted work.

perrygeo•1y ago
If you could package this up in a motivational poster, it belongs in every company meeting room. Speed and quality are not two opposing forces to tradeoff. We can have both.

But we need to get rid of this silly, infantile, unwavering attachment to our source code files. Throw code away. All. the. time. The first version of code is, by definition, being built in the absence of critical information. Why on earth would we get so attached to that which was built in ignorance? In this case we're not "reusing code", we're throwing away knowledge!

Why would you discard everything valuable you learned in favor of a code artifact written before you learned it? Throw away the code instead! Surely the code written AFTER gaining the knoweldge will be both faster and better quality. (and more clear, less tech debt, etc)

dsabanin•1y ago
Very well said. This is such an important point.

I believe that if you truly accept what Hemingway said, that writing is rewriting, you get less attached to the idea of reaching the best design on the first try, and feel better when starting with a suboptimal solution.

Of course this sometimes conflicts with organizational pressures, where that quick and dirty solution may be deemed as enough by some and you won't get to finish with the proper design. For me the trick is to consider first version just an internal stage of work on a feature, not even communicated outwards most of the times, until the appropriate design is reached.

cadamsdotcom•1y ago
We need better words for the different code written for different purposes.

Code written to learn and explore a problem space? Sure.

Code written in response to a prompt, which could easily be rewritten - things like a throwaway “please tell me a story about the contents of this CSV for me and also write code to graph it”. Yep throw it away.

Or keep it as an example for a later model.

That’s very different to code written to high standards intended for others’ use.

We need different words for all of those 3 varieties of code.