This is the correct answer. Don’t overthink this. Just go, have a look and that’s it. Tell everybody involved that you don’t have to proof anything if they ask.

I know people who could afford this house easily that walk around like a regular farmer. Sales people having regular contact with wealthy people know this.

42

What about a GOpher?

I agree. I maintained a dyson (I think it was a V6) for a couple of years. They are generally designed so well, it literally pokes your eye where they made the materials extra thin to break earlier (for example the pipe connection mechanism and the electrical connectors)

I gave up when the main body started to break. Using a Philips now. Better in many ways but still far from perfect.

The availability of spare parts is really good though for dysons. Lot of cheap stuff on Amazon and eBay. Buying a spare battery for the Philips for example is much harder.

It behaves like a pocket of air trapped under some wrap/sticker: It moves around without loosing its shape or density 😂

Good old brainfuck 👌

IMHO assembly isn’t hard. When you gain enough experience you start to see „visual patterns“ in your code. For example jumping over some lines often equals to a if/else statement or jumping back is often a loop etc. Then you are able to skim code without the necessity to read each line.

The most difficult part is to keep track of the big picture because it is so verbose. Otherwise it’s a handful or two of instructions you use 90+% of the time.

I needed it often in the past in the PLC world but it is dying out slowly. Nonetheless, when I encounter 30+ year old software I’m happy to be able to get along. And your experience transitions to other architectures like changing from one higher language to another.

Nonetheless, if I’m able to choose, I’ll take Go. Please and thank you 😊

Your answer doesn’t solve the issue and is a duplicate. I’ll double downvote you right now

😉

The highest level of achievement is missing: Getting only two downvotes on Stackoverflow