So, it’s still not here :P

Ringworld :)

You know how they say there is a difference between what people need and what they want? This is one of those cases. We gave up privacy in exchange for convenience. E.g. Cloud storage is convenient. For files, for documents, for code. It’s so convenient that apart from acting in outrage when we discover that companies are scanning our data to train AIs, among other things, we are willing to do absolute nothing. And I think that’s because we fear to lose that convenience if we force a change (not that we could even if we wanted). In other words, we are getting what we pay for (which makes sense because often all those cloud services are “free”).

There is also another problem: some personal data is irrelevant to us, but it makes companies money when the data is all aggregate together. So, it’s easy to let it pass (apart from some outrage) when you are informed that there is a leak and everyone can know how many hours you spend using a service. We don’t feel it’s very relevant. But having this kind of data about everyone can help companies to tailor their service to tske advantage of our habits, bringing THEM a lot of money. Most data they have is irrelevant for you but very relevant for companies that try to sell services.

Ideally I’d like to get paid. I’ll allow you to track me, but I get 1$ every time records on the database with my data are returned by a query. See if they like it…

Code review can’t fix incompence though. I lost count of how many times my boss told me “review that PR well because X is not very good”. Also my point is that they are overrated, not that they are useless.

Probably unpopular opinion, but peer reviews are overrated. If coders are good AND know the project, the only thing you can do in a PR is nitpicking. They are more useful for open source collaborators because you want to double-check their code fits with the current architecture. But people here are reacting as if peer reviews could actually spot bugs that tests can’t catch. That happens rarely unless the contributor is junion/not good.

I would fire you for incompetence and sabotage. Problem solved.

I salute the author of this for drawing a CRT monitor.

Follow up of: “Mmm… should I put lifecycle annotation in these 10 structs or just use and Rc and call it a day?”. Rc and Box FTW.