I personally like to keep it on. Most of my messaging is with family and friends and it’s good to know if someone read or hasn’t read my message.

Especially if things are time critical. Picking someone up? Asking if they need anything from the supermarket? If I see that they read the message I know that they are going to reply in a moment. If they didn’t even read the message I won’t have to wait around / can guess that they are currently in the car or wherever.

Sometimes you also have a spotty connection, so the received + read receipt can tell you if they actually got your message.

In general if someone sends me a message and I read it… I’m going to fucking reply to it (if I’m not super busy, and even then I might send a quick message back). I seriously don’t get people who just leave things on read and then forget about it.

But the NAS is in your house… which basically means if it gets flooded/burns down all your data is gone too.

I already have my data on my PC, a second backup inside the same house isn’t worth that much. But instead of relying on a cloud service I just rent a virtual server (for various things) and use Seafile to keep my data in sync.

PC breaks? House burns down? My data is on my own server in a datacenter. My server gets cancelled? My data is on my PCs.

So even with your NAS you are 100% reliant on a cloud backup still, so why did you get the NAS when you already have a copy of your data on your devices?

On the other hand you can lose your email address at any time if you don’t own the domain. So if Google decides they don’t like something you wrote your @gmail.com address could be gone tomorrow. And with it all your accounts you set up (as you need email usually to login or do changes).

The whole e-mail ecosystem sucks :-/

My self-hosted mail server works fine for now, but that could change at any moment.

Having 4 active accounts is anything but leaving the platform. Hell, I thought they had a single account they are giving up (like most companies).

What bullshit.

That’s an interesting thought!

Like Asian earwax is super dry and flaky, while European earwax looks like yellow green toxic goop.

So you have different genes and on top of that different diets (I had Indian neighbors once, you could smell the curry in the entire hallway of the building 24/7. But they obviously use a ton of spices when cooking).

As a central European Caucasian guy I personally start to smell really bad without deodorant just after a day or so. No matter how often I shower or what I eat. I also tried to switch to deodorant without aluminum and that didn’t work out at all :-/

Ever left the house? You’ll change your opinion right quick when you’re behind a random guy in the grocery store and you get a strong whiff of sour milk that has been out in the sun for a week.

Thank god for deodorant (and regular showers).

TDD is great when you have a very narrow use case, for example an algorithm. Where you already know beforehand: If I throw A in B should come out. If I throw B in C should come out. If I throw Z in an error should be thrown. And so on.

For that it’s awesome, which is mostly algorithms.

In real CRUD apps though? You have to write the actual implementation before the tests. Because in the tests you have to mock all the dependencies you used. Come up with fake test data. Mock functions from other classes you aren’t currently testing and so on. You could try TDD for this, but then you probably spend ten times longer writing and re-writing tests :-/

After a while it boils down to: Small unit tests where they make sense. Then system wide integration tests for complex use-cases.