frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
1331•jasondavies•5h ago•611 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
526•jasondavies•3h ago•85 comments

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

https://alpo.ge/remark.pdf
2263•iamronaldo•9h ago•1539 comments

NINLIVE: The Nine Inch Nails live archive

https://ninlive.com/
40•CharlesW•1h ago•5 comments

We promoted developers into architects without informing them

https://manidoraisamy.com/developer-to-architect.html
243•QueensGambit•5h ago•155 comments

Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis

https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singu...
292•archon1410•6h ago•112 comments

Language Models Can Rewrite Their Own Weights

https://arxiv.org/abs/2611.21885
314•lwhsiao•7h ago•104 comments

A few hours ago Google DeepMind created a math horizon repo

https://github.com/google-deepmind/math-horizon
34•RubenLtke•1h ago•21 comments

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

https://github.com/tristanbuckmaster/navier-stokes/
241•trotro•8h ago•77 comments

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

https://www.masteringemacs.org/article/announcing-dreamcoder
63•facundo_olano•3h ago•9 comments

Vibecoding an inference chip

https://ankitg.me/blog/vibecoding-inference-chip/
99•ankitvgupta•5h ago•31 comments

And Yet, It Moves

https://signoregalilei.com/2026/11/20/and-yet-it-moves/
55•notfried•3h ago•25 comments

If you can't explain something in simple terms, you don't understand it (2017)

https://kottke.org/17/06/if-you-cant-explain-something-in-simple-terms-you-dont-understand-it
598•sammatilda•13h ago•285 comments

The stochastic parrots have apparently proved the Riemann Hypothesis

https://scottaaronson.blog/?p=10344
174•stratos123•3h ago•140 comments

Winedroid – run Android apps without Android (WASM demo)

https://winedroid.soham.sh/demo/
81•sohzm•4h ago•25 comments

Frostbite: A new CPU architecture discovered, designed and verified by AI

https://architectlabs.com/blog/frostbite
607•shioyama•13h ago•316 comments

Signal Is Serious About Protecting Your Privacy

https://signal.org/blog/protecting-your-privacy/
476•dotcoma•13h ago•290 comments

Show HN: OpenComputer – an open source alternative to Devin

https://github.com/diggerhq/opencomputer
45•iacguy•3h ago•14 comments

Nvidia accounting under SEC investigation, sources say

https://finance.yahoo.com/markets/article/nvidia-stock-extends-25-trillion-rout-as-sec-probe-repo...
184•ftchd•3h ago•82 comments

Show HN: An API for word timestamps from speech, 75% within 20ms

https://quebec.yarn.so
49•jasperstory•3d ago•8 comments

Show HN: Professor Euler – Offline math desk, 300-function CAS, workbooks

https://euler.dawei7.com
8•dawei7•3d ago•0 comments

Nasdaq erases all 2026 gains

https://www.cnbc.com/2026/11/19/stock-market-today-live-updates.html
38•mv4•1h ago•4 comments

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

91•proberts•6h ago•126 comments

Microsoft announces Windows Server 2028 with hardened security

https://www.bleepingcomputer.com/news/microsoft/microsoft-announces-windows-server-2028-with-hard...
60•N19PEDL2•2d ago•64 comments

The Hungry Butler Effect: Concealed Commercial Incentives in LLMs

https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_...
6•undefinedmethod•1h ago•3 comments

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

https://kobi.music/research/dettato
222•hidude562•3d ago•48 comments

Google Workers Tell Their Employer Not to Punish Schools That Don't Want AI

https://www.motherjones.com/politics/2026/11/google-alphabet-union-school-ai-protest-gemini-worke...
241•cdrnsf•6h ago•176 comments

Reverse Engineering my cat's litter box

https://master--ytulsiani.netlify.app/blog/furrytails/
22•allidoisvim•3h ago•8 comments

Running two PSP emulators on one Switch 2 and sharing one via GameShare

https://github.com/XITRIX/ppsspp-nx2/blob/master/SWITCH2-GAMESHARE.md
51•khalidkhair•6h ago•0 comments

The G1 Garbage Collector

https://dev.java/learn/jvm/tool/garbage-collection/g1gc-overview/
96•ejboy•3d ago•50 comments
Open in hackernews

Production tests: a guidebook for better systems and more sleep

https://martincapodici.com/2025/05/13/production-tests-a-guidebook-for-better-systems-and-more-sleep/
78•mcapodici•1y ago

Comments

ashishb•1y ago
Here's a general rule that I follow along with this and that is "write tests along the axis of minimum change"[1]. Such tests are more valuable and require less maintenance over time.

1 - https://ashishb.net/programming/bad-and-good-ways-to-write-a...

compumike•1y ago
I'd add that, in terms of tactical implementation, production tests can be implemented at least two different ways:

(1) You set up an outside service to send an HTTP response (or run a headless browser session) every minute, and your endpoint runs some internal assertions that everything looks good, and returns 200 on success.

(2) You set up a scheduled job to run every minute internal to your service. This job does some internal assertions that everything looks good, and sends a heartbeat to an outside service on success.

For #2: most apps of any complexity will already have some system for background and scheduled jobs, so #2 can make a lot of sense. It can also serve as a production assertion that your background job system (Sidekiq, Celery, Resque, crond, systemd, etc) is healthy and running! But it doesn't test the HTTP side of your stack at all.

For #1: it has the advantage that you also get to assert that all the layers between your user and your application are up and running: DNS, load balancers, SSL certificates, etc. But this means that on failure, it may be less immediately clear whether the failure is internal to your application, or somewhere else in the stack.

My personal take has been to lean toward #2 more heavily (lots of individual check jobs that run once per minute inside Sidekiq, and then check-in on success), but with a little bit of #1 sprinkled in as well (some lightweight health-check endpoints, others that do more intense checks on various parts of the system, a few that monitor various redirects like www->root domain or http->https). And for our team we implement both #1 and #2 with Heii On-Call https://heiioncall.com/ : for #2, sending heartbeats from the cron-style check jobs to the "Inbound Liveness" triggers, and for #1, implementing a bunch of "Outbound Probe" HTTP uptime checks with various assertions on the response headers etc.

And this production monitoring is all in addition to a ton of rspec and capybara tests that run in CI before a build gets deployed. In terms of effort or lines of code, it's probably:

    90% rspec and capybara tests that run on CI (not production tests)
    9% various SystemXyzCheckJob tests that run every minute in production and send a heartbeat
    1% various health check endpoints with different assertions that are hit externally in production
And absolutely agree about requiring multiple consecutive failures before an alarm! Whenever I'm woken up by a false positive, my default timeout (i.e. # of consecutive failures required) gets a little bit higher :)
hugs•1y ago
yeah, full end-to-end tests/monitors are like fire alarms: they can often tell you something is wrong, but not exactly what is wrong. but that doesn't mean fire alarms have no value. most common failure mode for teams are having too many or none at all. but having a few in a few key places is the way to go.
mhw•1y ago
The fabulous blazer gem includes a feature for #2: https://github.com/ankane/blazer?tab=readme-ov-file#checks - it’s limited to checks that can be expressed as SQL queries, but that can get you quite a way
aleksiy123•1y ago
At Google we call these probers.

Does anyone know of any tools/saas that do this.

Was thinking it may be a good potential product.

Especially if it was super easy to generate/spin up for side projects.

hugs•1y ago
"testing in production" can be controversial, but this is a well-balanced take on it.

lately i've been working on a decentralized production testing network called 'valet network' [1] (full-disclosure: selenium creator here)

i suspect production tests are the killer app for this kind of network: test any site on a real device from anywhere on idle devices that more closely match real world conditions, but as mentioned in the article, it's not that simple. dev users will still need to be smart about creating test data and filtering out the tests from system logs. i'm still in the "is this something people want?" learning phase, even though this is definitely something i want and wish i had when i was helping to fix healthcare.gov back in 2013/2014.

[1]: https://gist.github.com/hugs/7ba46b32d3a21945e08e78510224610...

vasusen•1y ago
Thank you for the balanced take on an extremely spicy topic.

At WePay (YC S09) we debated this extensively and came up with a similar middle of the way solution. Making sure that a credit card can get tokenized is the critical flow and should run every minute. We ended up with about 4-5 very quick production tests. They helped with debugging as well as alerting.

I am now building a full, automated testing solution at Donobu (https://www.donobu.com), and production tests definitely come up as their own subcategory of e2e tests. I am going to use your guidelines to refine our prompt and bound our production test generator.

testthetest•1y ago
> Running a test every minute, or 1440 times a day, will show up quite a lot in logs, metrics, and traces.

...not to mention that automated tests are by definition bot traffic, and websites do/should have protections against spam. Cloudflare or AWS WAF tends to filter out some of our AWS DeviceFarm tests, and running automated tests directly from EC2 instances is pretty much guaranteed to be caught by Captcha. Which is not a complaint: this is literally what they were designed to do.

A way to mitigate this issue is to implement "test-only" user agents or tokens to make sure that synthetic requests are distinguishable from real ones, but that means that our code does something in testing that it doesn't do in "real life". (The full Volkswagen effect.)

burnt-resistor•1y ago
Also known as deep monitoring: checking that functionality is available and working correctly.