frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Al Lowe on model trains, funny deaths and working with Disney

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
39•thelok•2h ago•3 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
101•AlexeyBrin•6h ago•18 comments

First Proof

https://arxiv.org/abs/2602.05192
52•samasblack•3h ago•39 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
789•klaussilveira•20h ago•243 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
39•vinhnx•3h ago•5 comments

Reinforcement Learning from Human Feedback

https://rlhfbook.com/
63•onurkanbkrc•5h ago•5 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
1040•xnx•1d ago•587 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
462•theblazehen•2d ago•165 comments

France's homegrown open source online office suite

https://github.com/suitenumerique
509•nar001•4h ago•235 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
184•jesperordrup•10h ago•65 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
63•1vuio0pswjnm7•7h ago•60 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
189•alainrk•5h ago•280 comments

Software factories and the agentic moment

https://factory.strongdm.ai/
50•mellosouls•3h ago•51 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
27•rbanffy•4d ago•5 comments

72M Points of Interest

https://tech.marksblogg.com/overture-places-pois.html
19•marklit•5d ago•0 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
108•videotopia•4d ago•27 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
59•speckx•4d ago•62 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
268•isitcontent•21h ago•34 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
197•limoce•4d ago•107 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
281•dmpetrov•21h ago•150 comments

British drivers over 70 to face eye tests every three years

https://www.bbc.com/news/articles/c205nxy0p31o
169•bookofjoe•2h ago•153 comments

Making geo joins faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
152•matheusalmeida•2d ago•47 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
549•todsacerdoti•1d ago•266 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
422•ostacke•1d ago•110 comments

Ga68, a GNU Algol 68 Compiler

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
39•matt_d•4d ago•14 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
365•vecti•23h ago•167 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
465•lstoll•1d ago•305 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
341•eljojo•23h ago•210 comments

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
66•helloplanets•4d ago•70 comments

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
18•sandGorgon•2d ago•8 comments
Open in hackernews

Debugging Humidity: Lessons from deploying software in the physical world

https://physical-ai.ghost.io/debugging-humidity-lessons-from-deploying-code-to-a-factory-floor/
16•boulevard•3mo ago

Comments

_wire_•3mo ago
When it rains, it cores
boulevard•3mo ago
Haha! That's brilliant. You have summarized my entire blog in four words :P
unwind•3mo ago
Obi-Wan, is that you? :)
boulevard•3mo ago
Hello there.
timerol•3mo ago
Okay, but what about humidity? I was excited to read about a failure mode where the moisture content of air mattered, or at least get mildly clickbaited into learning about a tool called Humidity. Instead there are no other references to humidity apart from the title
sokoloff•3mo ago
The cloud is 100% humidity, I suppose.
OptionOfT•3mo ago
Too much humidity makes it rain, and rain can make the Wi-Fi work: https://predr.ag/blog/wifi-only-works-when-its-raining/
boulevard•3mo ago
I chose "Debugging Humidity" as a metaphor for all the invisible, pervasive environmental factors that you have to deal with in the physical world. Latency, power flicker, interference, etc. It's the "stuff in the air" that messes up clean logic.

The title was actually inspired by a real incident where a device kept failing every afternoon. We eventually realized that condensation from the facility's massive air conditioning unit was dripping onto the enclosure right above the SoC. We were, quite literally, debugging the effects of humidity. I should have included that story in the post itself.

camtarn•3mo ago
Some of my code gets deployed to a PLC aboard a wave power generator hundreds of metres offshore, with a cellular link that might go down in a storm. If something gets unrecoverably wedged, retrieving the device starts at $10K to hire a ship.

I feel this blog post hard.

boulevard•3mo ago
Wow, that's a fantastic and terrifying example. "Retrieving the device starts at $10K" is about as high-stakes as it gets for software reliability. It perfectly crystallizes the difference between rebooting a cloud instance for pennies and the extreme costs of failure in the physical world.
rdtsc•3mo ago
> This is why so many “IoT platforms” die in pilot purgatory. They are built by cloud engineers who underestimate the friction of the real world and overestimate the availability of bandwidth.

Indeed. That's why it's important to send your engineers along with the sales folks to these sites. If anything just to get a perspective on things like that.

> The first time I deployed code to an actual factory floor, I learned that "edge compute" doesn’t live in climate-controlled racks. It lives next to dust, grease, and forklifts.

And bugs, real ones not just nice abstract software ones. So you may find yourself debugging spider webs and ants crawling around, which always makes for great puns and stories.

boulevard•3mo ago
There is absolutely no substitute for an engineer seeing, smelling, and hearing the environment where their code will actually run. The number of times a mysterious software glitch on a remote device has been traced back to insect nests, rodent chewed cables, or just a thick layer of industrial grime is not zero. It gives a whole new meaning to flushing the cache :)
OptionOfT•3mo ago
Isn't

> Now, imagine your request is actuator.rotate(90).

a good example of something that is not idempotent? As it is based on its current position. Actually idempotent would be: `actuator.rotateTo(Degrees(90))` with a predefined frame of reference, or a frame of reference that you can include in the request.

Like the difference between a servomotor vs stepper motor.

boulevard•3mo ago
Your suggestion of actuator.rotateTo(Degrees(90)) is precisely the right way to engineer a robust, idempotent command for the physical world.

I used the simpler, non-idempotent rotate(90) example intentionally to illustrate the default trap. How a pure software mindset can dangerously oversimplify a physical action.