I’ve never had to do this sort of thing in a lab, but I now feel I know exactly what that feels like! You have my sympathy!

Isn’t dust what you get when things disintegrate?

It’s just psychologically nicer. It’s a bit like it being nicer to get on with work when my desk is tidy (not that I tidy it that often)

I do it, because it makes a massive difference to me how tidy my bedroom feels and how welcoming the bed looks at the end of the day. I just have a duvet though, so it’s 10 seconds of pulling on each corner until it’s reasonably even - not going for perfection!

Do not declare your undying love for someone. It puts way too much pressure on, and unless they’re in exactly the same mental place it’s unlikely to go anywhere.

Instead, just ask them if they’d like to go on a date. That obviously communicates that you’re interested in them, and gives a good starting point to build a connection.

deleted by creator

I think you’re close - someone well travelled is someone who has a broader view of how the world works than just the one country they were brought up in.

That happens when they go to countries and actually experience them. I’ve just been to the Canary Islands for a week - I went airport to hotel, sat beside the pool for a week and then went home again. This was lovely and relaxing (which I needed) but did nothing for expanding my cultural horizons.

Your instructions are completely correct, but it might make more sense to look at the bands of metal rather than the insulator between them.

TRS stands for “Tip, Ring, Sleeve”, referring to the 3 contacts on a TRS jack - one for the left channel, one for right and one for ground. TRRS as you might guess has an extra ring to provide a contact for the microphone as well. So you’re looking for the metal tip, two rings of metal and then the metal sleeve.

Yeah, I think you have to acknowledge it or they’ll feel (at best) incredibly awkward the whole time. Don’t make a big deal of it though - say you’re “sorry you ghosted her and no-one deserves that. If she wants to talk about it then you’re willing, but otherwise won’t mention it again”.

One more note on learning Rust: what Rust does is front-load the pain. If you write something in another low-level “direct control of memory” language you can often get something going much more easily than Rust because you don’t have to “fight the borrow checker” - it’ll just let you do what you want. In Rust, you need to learn how all the ownership stuff works and what types to use to keep the compiler happy.

But then as your project grows, or does a more unusual thing, or is just handed over to someone who didn’t know the original design idea, Rust begins to shine more and more. Your C/C++/whatever program might start randomly crashing because there’s a case where your pointer arithmetic doesn’t work, or it has a security hole because it’s possible to make a buffer overrun. But in Rust, the compiler has already made you prove that none of that is possible in your program.

So you pay a cost at the start (both at the start of learning, and at the start of getting your program going) but then over time Rust gives you a good return on that investment.

Context: I am an embedded software engineer. I write a lot of low level code that runs on microprocessors or in OS kernels, as well as networking applications and other things. I write a lot of C, I write some Rust, I write Elixir if I possibly can, I write a lot of Python (I hate C++ with a passion).

I don’t think you want Rust. Python is unbeatable on “idea to deployment” speed. Python’s downsides:

• Painful packaging/distribution if you want to get a load of people who don’t have Python installed to run your thing (e.g the GUI program we currently maintain for talking to our hardware)
• Performance under some circumstances. There are some things that are not quick in Python. They’re not always the things you expect because Python actually drops down to C modules for a lot of the number crunching that you might do. E.g. for ML you are basically using Python to plug a load of bits of fast C code together

Rust is good when you need at least one of:

• High speed
• Control over use of memory
• Low level systems programming (drivers etc.)
• Can’t cope with a Garbage Collector
• Compiling to a microcontroller

If you’re doing one of those and so have become expert in Rust, then it is actually excellent for a lot of other things. E.g. you might build your data processor in it, and then distribution is easy because it’s just a single binary.

One option you might look at is Go. You get a lot of performance, you get good parallelism if you need it, it’s designed to be easy to learn, and it also compiles programs to a single binary for easy distribution.

What can you possibly need more than 100TB of storage for?! Presumably some redundancy but still way more than I can imagine a personal need for.

Great article. Similar to “NASA’s booster size is the result of the size of a horse’s ass”: https://www.linkedin.com/pulse/4-feet-85-inches-space-shuttle-horses-ass-william-batch-batchelder

Carrying cash - particularly coins - is such a pain in the neck. I pay for everything on card whether I’m in this country (UK) or travelling abroad.

I’m almost at the point where I don’t need to carry a wallet at all - contactless on my phone takes care of a lot.

I’m lucky enough to be able to have a lot of choice where I work - in a software engineer and there are any number of places where I could work and be paid well. Given that I feel some responsibility to work somewhere ethical - not everyone else has the opportunity to decide.

Yeah, I agree that the above is excellent advice. Engaging in a way that comes off as “you’re a shit parent so I’m going to do it for you” isn’t likely to build conflict. It’s possible how the mother reacts regardless of what you say (due to insecurity about her parenting), but it’s going to be much better if everyone is working together rather than against each other, so that’s the best place to start.

Yes, but the public transport in Singapore is excellent. I wish more cities did it.

See the other message I have written - you should always recommend search. The URL only works if someone has already searched for that community. If you’re on a big instance, that’s almost always true, but on a smaller instance it often isn’t.

The above advice isn’t perfect - in general, use Search first.

Until the first person searches for a community on your instance, your instance doesn’t know about it and the URL won’t work. Searching (usually using the !community@instance.com form) should always work.

Equally, your instance doesn’t start pulling data on a community (messages etc.) until someone subscribes to it, and then when subscribed it will sometimes take a a few hours to get it all (it should immediately start getting new posts and comments).

The general concept you’re describing is called Risk Compensation. It feels intuitively correct, but in whatever context it’s been studied in almost all cases it turns out that the safety feature is actually better overall. Some people might be a bit riskier knowing about the safety net, but not enough to counteract the safety improvement.

Also - in the UK - road deaths go down over time, while miles driven goes up. Driving is getting safer. Cars are part of that, but so is road nd signal design and driver training.