Live data from Hacker News

Never trust a system that seems to be working

twitter.com

261–270 of 376 posts

Re: Never trust a system that seems to be working

#261

A bit of an off-topic: I only ever saw white traffic lights in the US and Canada (specifically, pedestrian traffic lights) and they confused me a lot at first - the rest of the world uses green. The icons displayed (hands) are confusing too: the rest of the world uses an icon of a man walking or standing.

the rest of the world uses green. Only if you define the rest of the world to mean the very small percentage of places in the world you have been. From Wikipedia: In some countries, instead of "don't walk", a depiction of a red man or hand indicating when not to cross, the drawing of the person crossing appears with an "X" drawn over it. Some countries around the Baltic Sea in Scandinavia duplicate the red light. Ins…

I've been to all continents except maybe Australia. Only North America has the weird white light for pedestrians and a red palm (which also blinks, which is very counter-intuitive). I can assure, most countries of the world use red and green icons of man standing/walking for pedestrians.

Re: Never trust a system that seems to be working

#262
post #238

Earlier quoted context omitted.

It’s trendy to hate HN by some on Twitter. *edit to provide context. this isn’t unique to twitter/hn. it’s trendy on reddit to hate tiktok and instagram. it’s trendy on 4chan to hate reddit.

Sure, except in this case foone has explained exactly why they dislike their stuff showing up on HN.

They also seem to hate Factorio itself, which is the reason that while they play it and tweet about it so much, they mangle its name. I don't understand it, but everyone is free to remove what they want from their own Twitter I guess.

Re: Never trust a system that seems to be working

#263
post #177

It’s really interesting how factorio problems are pretty much the same as multiprocessing/distributed systems problems. It just shows how universal and fundamental the idea of “work” and “workers” are. An engineer on my old team came up with a credit system to solve this problem, the receiver issues credits to the sender, which only sends when there is a credit available - this ends up with the same better failure mo…

Semaphore, Dijkstra, around 1962-1963

Re: Never trust a system that seems to be working

#264

As I and others have previously pointed out [1] foone uses they/them pronouns and feels particularly frustrated when their posts get featured on HN, because users here seem unable to honor this simple preference of theirs. It looks like they deleted their tweet out of frustration with todays latest round of misgendering. I hope people on HN will learn to respect all members of our community. Yes that involves not ass…

[deleted]

Re: Never trust a system that seems to be working

#265

Earlier quoted context omitted.

Yeah, any design is going to be various trade-offs, and you have to understand them (and how they may relate to your mission) when determining what to do and what would be a bad decision. For example, cars have "fail open" brakes but have independent cylinders so that it is relatively hard to have all four wheels fail at the same time (older cars had single master cylinders) - and one of the tradeoffs is that people…

Pretty much every car made since the 1980s has had dual-circuit brakes with usually one front and one rear wheel cylinder on each circuit. Volvo being Volvo took it further with their 2-series cars in the 1970s and 1980s, where the front discs had four-pot calipers configured as two sets of two-pot calipers. Each braking circuit had one half of each front caliper and one rear caliper, so in the event of one half of t…

There is one subtle difference between automatic transmissions and manual ones and that is the manual one will allow a shift into a lower gear even when engine damage is likely.

An automatic one will not, and will hold the current gear until car speed falls within shifting range.

Ask me how I know :)

Re: Never trust a system that seems to be working

#266
post #138

Earlier quoted context omitted.

Similarly, the joke that the engineer’s second worst nightmare is, “it doesn’t work but it should”, while their worst nightmare is, “it works but it shouldn’t”.

That’s the surest way to nerd snipe some people. This code doesn’t work, and yet it does. After reading the commit history, it in fact never worked, and yet it has been up until yesterday. What in the actual fuck.

The buggy behaviour of A caused buggy behaviour of B that caused buggy behaviour of C, just so happened to align enough to "look like it is working".

Double fuckup if the thing is backups and your data is gone. Reason why we check not only "does the backup job finished" but also "does the size looks right", because backup with 0 files still returns OK...

Re: Never trust a system that seems to be working

#267

One reply tweet notes "a complex system always operates in a failure state", but to find more discussion on this point it's worth noting that this is a restatement of: > "The Fundamental Failure-Mode Theorem (F.F.T.): complex systems usually operate in a failure mode." -- John Gall, General Systemantics (aka Systemantics , aka The Systems Bible ), 1977 https://en.wikipedia.org/wiki/Systemantics > Searching for "funda…

The number of interactions of a system with n components increases according to O(n^2).

The probability of an interaction not going wrong decreases exponentially with each interaction.

Re: Never trust a system that seems to be working

#268

There are two good lessons here: 1) Robust system design involves identifying the parts of your system that are mission-critical and always monitoring them. NASA missions have great automation and a 24/7-staffed mission control. 2) If a system failure can result in massive secondary damage, isolate that system. Warehouses receiving orbital payloads should probably be nice and far away from the base you care about.

> 1) Robust system design involves identifying the parts of your system that are mission-critical and always monitoring them. NASA missions have great automation and a 24/7-staffed mission control.

You should alert on critical parts but you should monitor anything and everything you can. It might be critical in finding out why system broke later on. Easier said than done for hardware but easy for software

Re: Never trust a system that seems to be working

#269

This is why 4-20 mA is a common signaling standard in industrial automation. 4 mA means zero and 20 mA means one. 0 mA means broken transmitter !

Also why a standard keyboard has a Break key: used to be that a telegraph station would have a bell that rang if it detected a broken connection (a “break condition”), then people figured that deliberately inducing a break was a handy way to alert the remote operator. I think the first automated telegraph systems actually used current-loop signalling, but I’m not sure about the first practical ones; in any case, the…

I have a standard keyboard and it has no break key.

Re: Never trust a system that seems to be working

#270

"This Tweet has been deleted" -- does anybody have a mirror? Maybe @dang can update the main link to that.

https://threadreaderapp.com/thread/1581643415850098688.html

https://archive.ph/cToUl

but foone doesn't like the orange site so we probably shouldn't link (another advantage to running your own site, you can make refers you don't like see goats)

https://threadreaderapp.com/thread/1582089029096382464.html

Post reply on HN