frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
1849•jasondavies•12h ago•851 comments

Levent Alpöge claims proof of the Generalized Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
2508•iamronaldo•16h ago•1733 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
872•jasondavies•10h ago•162 comments

NINLIVE: The Nine Inch Nails live archive

https://ninlive.com/
206•CharlesW•8h ago•54 comments

We promoted developers into architects without informing them

https://manidoraisamy.com/developer-to-architect.html
378•QueensGambit•12h ago•218 comments

Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis

https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singu...
398•archon1410•13h ago•164 comments

Valkey kills the skiplist, cuts sorted set overhead by up to 43%

https://valkey.io/blog/from-skiplist-to-b+tree/
97•reconditerose•3d ago•37 comments

Clojure will affect the way you think about programming (2017)

https://eli.thegreenplace.net/2017/clojure-the-perfect-language-to-expand-your-brain/
41•sammatilda•3h ago•8 comments

Sir Brian May adds new dimension to Hera asteroid

https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-add...
81•mooreds•7h ago•17 comments

Language Models Can Rewrite Their Own Weights

https://arxiv.org/abs/2611.21885
381•lwhsiao•14h ago•116 comments

ClawDOS – An AI coding agent for DOS

http://ricapar.net/ClawDOS/
4•Ricapar•59m ago•1 comments

DreamCoder: Coding harness and IDE from the author of Mastering Emacs

https://www.masteringemacs.org/article/announcing-dreamcoder
174•facundo_olano•10h ago•40 comments

BlackBlaze now explicitly states selling your data for advertisement

https://www.backblaze.com/company/policy/privacy
140•meysamazad•3h ago•39 comments

Finite-time blow-up for the Navier–Stokes equations

https://github.com/tristanbuckmaster/navier-stokes/
273•trotro•15h ago•86 comments

Vibecoding an inference chip

https://ankitg.me/blog/vibecoding-inference-chip/
133•ankitvgupta•12h ago•54 comments

Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?

77•LetThingsBeDiff•7h ago•81 comments

Serious cyberattack thought backed by wealthy operators

https://www.ruv.is/english/2026-11-20-serious-cyberattack-thought-backed-by-wealthy-operators-493411
59•Bender•7h ago•31 comments

Nasdaq erases all 2026 gains as AI sell-off dampens Anthropic’s second day

https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell...
231•cdrnsf•17h ago•510 comments

The stochastic parrots have apparently proved the Riemann Hypothesis

https://scottaaronson.blog/?p=10344
266•stratos123•10h ago•238 comments

Fewer slides, more dragons

https://www.breakingchange.blog/p/fewer-slides-more-dragons
5•firloop•2d ago•0 comments

Show HN: Tinnitus frequency finder and audio notch tool

https://trynotched.com/find
151•brianrhea•3d ago•109 comments

Winedroid – run Android apps without Android (WASM demo)

https://winedroid.soham.sh/demo/
127•sohzm•11h ago•36 comments

Why the Airbus A321XLR often gets stuck climbing for first few hours of flight

https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/
105•edward•6d ago•72 comments

And yet, it moves

https://signoregalilei.com/2026/11/20/and-yet-it-moves/
131•notfried•10h ago•82 comments

I can’t believe it’s 1

https://aperiodical.com/2026/11/i-cant-believe-its-1/
56•ColinWright•4d ago•59 comments

Slopstrap – Make your site look hastily vibecoded

https://slopstrap.mikelacher.com/
173•mlacher•15h ago•29 comments

Show HN: I made an audio-to-MIDI model 60x more efficient

https://kobi.music/research/dettato
267•hidude562•4d ago•56 comments

The Hungry Butler Effect: Concealed Commercial Incentives in LLMs

https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_...
31•undefinedmethod•8h ago•9 comments

Show HN: OpenComputer – an open source alternative to Devin

https://github.com/diggerhq/opencomputer
95•iacguy•10h ago•24 comments

I Don't Trust Visual Recordings Anymore. But One Day I Will Again

https://spectrum.ieee.org/fighting-back-against-deep-fakes
28•jnord•6h ago•4 comments
Open in hackernews

Requirements change until they don't

https://buttondown.com/hillelwayne/archive/requirements-change-until-they-dont/
74•azhenley•1y ago

Comments

firesteelrain•1y ago
I feel like Wayne is taking the Agile Maxim “requirements always change” too literally. Agile doesn’t mean "every requirement always changes forever”.

In most live production environments today, requirements do keep changing — security, compliance, customer behavior, scaling — even when teams think they're done.

Agile isn’t making an empirical prediction ("all requirements will mutate endlessly"); it’s a philosophical posture toward uncertainty

Wayne misses this interpretative nuance.

fredo2025•1y ago
I agree with Wayne that the needs of the user don’t seem to end, even if your project or contract completes. Either the need is to keep maintaining it, put a twist on it, radically change it, or abandon it for something else.

I don’t agree on testing. It’s been a long time since I bought into that, and even tests for uncertain behavior to have confidence is a form of tech debt, as the developer that follows you must make a decision whether to maintain the test or to delete it; its value doesn’t usually last. An exception would be verifying expected behavior of a library or service that must stay consistent, but that is not the job of most developers.

tbrownaw•1y ago
> Agile isn’t making an empirical prediction ("all requirements will mutate endlessly"); it’s a philosophical posture toward uncertainty

At some point this philosophy has to result in something concrete.

How much ongoing effort should be put into handling the possibility that this particular requirement might change?

rTX5CMRXIfFG•1y ago
You have to be able to distinguish between general and specific theories, so that you don’t expect the general to provide you the specific.
Swizec•1y ago
> How much ongoing effort should be put into handling the possibility that this particular requirement might change?

How likely is it that the world freezes and stops changing around your software? This includes business processes, dependencies, end-user expectations, regulations, etc.

In general that’s the difference between a product and a project. Even Coca Cola keeps tweaking its recipe based on ingredient availability, changes in manufacturing, price optimizations, logistics developments, etc.

Hell, COBOL and FORTRAN still get regular updates every few years! Because the software that runs on them continues to stay under active maintenance and has evolving needs.

rightbyte•1y ago
> Even Coca Cola keeps tweaking its recipe

Ye and they should stop. Has there been any big changes except the "New Coke" that never reached my home town?

virgilp•1y ago
As a general rule, one should presume that they now less about running a business than the people that actually do that. There are exceptions but as with all rules, exceptions don't invalidate the rule.

"they should stop" is a fine rant to express your personal taste preferences, but objectively speaking, I would bet on Coca-Cola having good reasons when tweaking the recipes. If that happens, it's probably more necessary than a layman realizes.

rightbyte•
cjfd•1y ago
It seems the article is much wiser than this comment. It is a distinction without a difference whether 'requirements always change' or whether 'every requirement always changes forever'. If you don't know which requirement is going to change next week, it does not matter which of these two are true.
firesteelrain•1y ago
That’s fair from a practical design perspective. But, if you treat “requirements always change” as a hard truth rather than a heuristic or philosophical posture, you can end up in a mode where stability is viewed with suspicion, and architecture never settles. Some requirements do stabilize and knowing when that happens can help determine tradeoffs.
AndrewKemendo•1y ago
Preface: A Formally verified end to end application with associated state machine(s) is kind of my engineering holy grail - so I’m a likely mark for this article.

However the author never actually makes a good case for FV other than to satisfy hard-core OCD engineers like ourselves. Maybe the author feels like we all know their opinion - but it seems like the author is arguing against a poster of claude shannon.

If the system is - for all intents and purposes - deterministically solving the subset of problems for the customer, and you never build the state machine, then who cares?

My argument is “there isn’t one” — that’s provided we’re in a business context where new features are ALWAYS more beneficial to the business inputs than formal verification.

If a business requirement requires formal verification then the argument is also moot - because it is part of the business requirement - and so it’s not optional it’s a feature.

Come to think of it I’m not really sure I’ve ever seen software created on behalf of a business, that has formal verification, where FM is not mandatory requirement of the application or it’s not a research project.

The last time I saw formal state machines built against a Formally Verfied system it was from a bored 50 year old unicorn engineer doing it on a simple C application.

shoo•1y ago
> we’re in a business context where new features are ALWAYS more beneficial to the business inputs than formal verification.

Another way of framing this is "what is the impact (to the business / to the customers / to the users) of shipping a defect?". In a lot of contexts the impact of shipping defects is relatively low -- say SaaS applications providing a non-critical service, where defects, once noticed, can usually be fixed by rolling back to the last good version server side. In some contexts the impact of shipping defects is very high, say if the defect gets baked into hardware and ships before it is detected, and fixing it would require a recall that would bankrupt the company, or if a defect could kill the customers/users or crash the space probe or so on.

xlii•1y ago
> In some contexts the impact of shipping defects is very high (…)

I agree however I think that many overestimate how frequent those environments are. Almost everything can be updated (and that includes dumb appliances with hardware chips replaced by technician) and the only real question is what is your reliability vector.

At the end of the spectrum there’s Two Generals Problem and Space Bit Flip and so much complexity that’s mind blowing. I’ve seen on my own eyes industry wide screwups that were fixed with month full of phone calls and paper slips exchange, so it’s not like we (as humans) cannot live with unreliable systems.

I’ve been researching formal verification for a while and IMO they are not fit for general use through lack of ergonomics. I might have some ideas how to solve it but I rather try to put in a commercial box <insert dr evil meme>

taeric•1y ago
The diversion through phase changes is awkward, here? I would use that metaphor to point out that many of the properties and requirements to maintain one phase are not relevant when in another phase. More, some properties become harder with different phases. Sure, holding water is generally easier than holding steam. Neither is easy at large scale, of course.

I think you could stick with construction metaphors for a lot of learning. Scaffolding key stones is particularly instructive. You will build a large structure that is intended to be torn down in order to build another structure. And there is basically no avoiding it.

I'm not clear how to move those ideas to formal methods. Typically you do that by keeping different layers that you formalize to different degrees? Along with processes to confirm compliance at the different layers.

Software seems to get tough as we often wind up trying to expand solution and construction models to be fully inclusive of each other. We don't necessarily do this for any other construction. Do we?

1y ago
Sure I am no expert. But it goes both way.

They might also argue they know better than me and AB test the soda into something silly if they get hubris.

Swizec•1y ago
> Has there been any big changes

Yes and no. We’ll never know. There are small changes all the time. You and I wouldn’t even notice the difference.

But if you compared today’s flavor to the flavor of 100 years ago side-by-side, I bet it’s pretty noticeable. Today they use corn syrup instead of sugar, for example. Many of the flavoring ingredients from back then aren’t even legal for human consumption anymore either.

Exact ingredients also differ between markets so we’re not even all talking about the same coca cola.

rightbyte•1y ago
A part time bar owner I worked with claimed Mexican Coca Cola was the best due the sugar being made out of either corn or sugar cane, I don't remember which one, compared the US one.

It would have been interesting to do a blind test if that.

arkh•1y ago
The result of Agile (and DDD, TDD etc.) comes back to The Mythical Man Month: you're gonna throw one away. So plan the system for change.

And due to Conway's law: plan the organization for change.

From those ideas you derive Agile (make an organization easily changeable) and the tactical part of DDD (all the code architecture meant to be often and easily refactored).

hdjrudni•1y ago
Things are often fixable, but if you keep breaking things for your user you're going to develop a reputation for being unstable and your customers will leave.
xlii•1y ago
That's true, but "Real Metrics" matter.

Bugs are on the spectrum - some might increase resource usage, or some might crash for a percent of users. Some might always manifest for specific cohort of users and it might not be profitable to fix it for them. It's an ocean of possibilities between "perfect system" and "complete failure".

Sanity test are degrees of magnitude easier than FV and they can assure at least that.

LegionMammal978•1y ago
And even a "perfect system" might not be perfect for all users. I've seen lots of "old-school, battle-tested, rock-solid software" with bizarre behavior that supporters insist is an intended feature and can never be changed or configured, on account of it being convenient for some workflow back in the '80s or whatever. No system is so "perfect" that it can be all things to all people, unless it's truly trivial in scope.
AndrewKemendo•1y ago
Right but then it’s a requirement, the author frames the argument around FV when it’s NOT a written requirement

I mentioned exactly that:

> If a business requirement requires formal verification then the argument is also moot - because it is part of the business requirement - and so it’s not optional it’s a feature.

ipaddr•1y ago
This may seem counterintuitive but new features often alienate customers. It's not because of formal verification it's because a percentage of customers don't want change.