Live data from Hacker News

Never trust a system that seems to be working

twitter.com

201–210 of 376 posts

Re: Never trust a system that seems to be working

#201
post #79

Earlier quoted context omitted.

Working with beginning programming students, "Yay, now we have an error message that makes sense" has become my catchphrase.

"Read the error message, no wait don't close that go back" when helping people is a definite feeling. Take a deep breath. Take off your headset. Go outside. Never look at a computer again. Start driving a bulldozer. Life is good.

It's amazing the number of junior engineers I've taught to simply read the error message properly.

Re: Never trust a system that seems to be working

#202
post #35

If your code has side effects, it only ever seems to be working. ---- > the newbie says "aww, why isn't it working?" > the intermediate says "yay, it's working!" > the expert goes "hmm, why is it working?" I've also seen this as My thing isn't working and I change X and now I get error J instead of error K, so now I have to change X back because it's still not working. Where K is a "better" error than J, such as K =…

No news is bad news.

I don’t like code that compiles cleanly or runs cleanly on the first try. The worst is when I know that code isn’t close to done yet. Without errors my list of actionable tasks is low. I know there are a certain number of problems, and if I can’t see any it’s because they’re invisible, not because I don’t have any.

Re: Never trust a system that seems to be working

#203
post #138
post #35

If your code has side effects, it only ever seems to be working. ---- > the newbie says "aww, why isn't it working?" > the intermediate says "yay, it's working!" > the expert goes "hmm, why is it working?" I've also seen this as My thing isn't working and I change X and now I get error J instead of error K, so now I have to change X back because it's still not working. Where K is a "better" error than J, such as K =…

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.

Re: Never trust a system that seems to be working

#204
post #42
post #20

Earlier quoted context omitted.

Quoted post unavailable.

Go around your office using "she" to refer to your male co-workers and see how long before someone gets cross.

The chance you get the gender correct when you know the real name, the voice, the look and the behavior of a person is significantly higher. Thus it makes more sense to raise an eyebrow when someone misgenders in real life.

Re: Never trust a system that seems to be working

#205
Tweet seems to be deleted now. A brief summary of what it was:

* In Factorio (game) you can have space stations that send supplies to your ground base

* If the supplies are not caught, then they cause damage to your base

* To avoid sending supplies that cannot be caught, you can use logic controls

* A common approach is to have the station say "if (ground supply * This fails if the ground supply loses power, as no signal is interpreted as 0 and 0 * Thus, the system will appear to work until your ground base loses power, at which point it will be destroyed

* A better system is to have the ground base use logic to say "if supply With a fun callout to https://en.wikipedia.org/wiki/The_Moon_Is_a_Harsh_Mistress

Re: Never trust a system that seems to be working

#206
post #138
post #35

If your code has side effects, it only ever seems to be working. ---- > the newbie says "aww, why isn't it working?" > the intermediate says "yay, it's working!" > the expert goes "hmm, why is it working?" I've also seen this as My thing isn't working and I change X and now I get error J instead of error K, so now I have to change X back because it's still not working. Where K is a "better" error than J, such as K =…

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”.

I used to do industrial tech support and this gives me the raging anxieties.

Re: Never trust a system that seems to be working

#208

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 white crossing indicator lead to a hilarious situation for me once. I am colorblind and always assumed the walking guy is green just like car signals. One day when a person I was hosting from Indonesia was walking in downtown San Francisco with me, we were talking about traffic conventions. He said to me “Here things are very easy. You just wait for the white man and then you cross!” I thought he was making an poor-taste joke about following the locals when traveling, and it took quite a while to clear everything up! And I learned something new about my own country’s traffic signals.

Re: Never trust a system that seems to be working

#209

While I have not really played SE (past initial launch, it was too daunting to build the ship in space, etc) I have run into these kind of "issues" in Factorio. While they can have disastrous effects, I often really enjoy finding the core problem and finding a solution to make it "fail-safe". Sometimes I wish I could go back and wipe all my Factorio knowledge and start from scratch again, most importantly refusing to…

I want to reinforce your plan. Somehow I played factorio for a few hundred hours before finding online communities and blueprints. It was a wonderful experience of discovery and exploration. I came up with a few "novel" designs during that time that I'm still proud of.

Once comparing my own work to the best online it took a lot of joy out of the game. But I found that the memory was short lived, once I cut myself off from those online communities it was easy to fall back into the "let me pull out my sketchbook and solve this problem" mindset. I think half the fun is that design process.

I'm well north of 1000 hours now, and still discovering new ways to play and solve problems. I've come full circle and now build spaghetti bases because they are so visually fun.

Post reply on HN