Same here. And it is not expensive.

In the Netherlands, anything you buy from Bol.com is automatically synced to your Kobo device. Not sure about other retailers.

It's because they're affiliates. Same goes for FNAC

For most males it should be possible to get enough calories and nutrients from just one meal, but I would not say easy. It is far easier with two meals, or maybe a time window of 4 hours.

It's probably also better to ease into it. So start with an 8 hour eating window and slowly decrease the window.

Getting enough calories and nutrients can be a challenge and is far from easy with the "standard western diet". I would really recommend seeking advice from a professional.

>Getting enough calories and nutrients can be a challenge and is far from easy with the "standard western diet".

Have you been to a grocery store in the last 100 years? Getting enough calories and nutrients is dead simple, our stores are overflowing with fresh fruit, vegetables, nuts and meat. What is the "standard western diet"?

> What is the "standard western diet"?

https://en.wikipedia.org/wiki/Western_pattern_diet, also referred to throughout the article as "The Standard American Diet".

Under normal circumstances the difficulty with the western diet is getting enough nutrients, but not too much calories.

I meant the combination can be a challenge if your on a narrow time feeding window.

This is why you have backups. Good on you to have them!

When I just started as a junior dev at a small company I made the classic mistake of emptying the prod db instead of my local dev db. This was a small and in hindsight insignificant project. But Google was our customer, so it didn't feel insignificant at the time.

In this case my inexperience was partly my savior. All the data was inputted by people via a web form. Normally you're supposed to use POST to submit a form. But I was quite clueless at the time, so I had used GET. This meant all requests were still in the Apache logs. I could simply replay all requests.

I still feel my hard pounding when I think about the moment I realized what had happened. I was really relieved when everything was back!

What I learned from this incident:

- make automated backups

- no access to prod db from anywhere but prod

Yea, I’ve wiped out an entire government’s form library once. Backups are a career saver.

I don't know. Disclaimer: just a happy customer. What I do know is that all you know about me is the account number you gave me and the IP address I'm connecting from. I always pay cash, so that would be hard to trace back.

So I know you do the absolute maximum you can do to know as little about me as possible. As far as not keeping logs and not spying on me, I suppose I'll have to trust the audit reports.

Not much more you can do in my opinion. It's definitely good enough for me! Thanks for this great service!

> Not much more you can do in my opinion. It's definitely good enough for me! Thanks for this great service!

Thank you. I happen to think there's a lot more we can do. Look forward to future blog posts. :)

Maybe you shouldn't feel bad about this, you're not always hurting feelings.

If I'm using an open source project and I need something changed, I'll usually just make the change and put the new code online, because I think that's how open source is supposed to work. Others can now benefit from my change.

I'll also make a PR to the original project. But I don't mind if it's rejected. I made the changes for myself. If you can use the changes, fine. If can't, also fine.

I think describing this article as a one sided rant isn't really fair. The author shows that Go makes a few design decisions that make it easy to shoot yourself in the foot. This is generally a bad idea. Rust may be the summum of correctness. In my view that makes it an ideal candidate for comparison. It shows the reader what a better solution would look like. And that this can work in practice. Does that mean you shouldn't write code in Go? No of course not. But I think the author has done a great job of showing why they don't want to use Go anymore.

It’s one sided when it points out the pitfalls without bothering to describe why they’re there, and what the upside is. There are sloppy mistakes in Go, just like in anything, but many of the common criticisms of go are about trade offs not about mistakes.

Sure, but the way I read the article, that's what the author shows. They don't like trade-offs that are made.

Maybe the tone of the article feels a little aggressive towards Go, I don't know. To me it felt more like an outcry of frustration with the chosen trade-offs.

Reminds me of all the hours I spent learning to program in QBasic.

Me too! Maybe that's why I like it

In Linux you can also use network namespaces for this. Although you can't have your application run in multiple namespaces simultaneously, I think.

The websocket approach is a lot easier to configure, so I'm definitely going to look in to this.

Email from the dutch government: You have a message from <organization>. Log in to My Government to view.

Me: logging in to My Government using DigiD, which takes some effort, like five steps between two different sites and an app, but at least seems to be secure.

My Government message: you have a message from <organization>. Log in to <organization> portal to view message.

Me: Logging in to <organization> portal, again using DigiD (same steps).

<organization> portal message: There is a new document for you to download at My Documents in our portal.

Me: Wow, I don't even have to log in again, that's great! Document is not in the list, though. O, you have to select unread documents, otherwise you only get the old ones. Sure, makes sense.

Document: You student loan interest has been changed. We will send you your new monthly repayment amount soon.

Me: Great, glad I spent an hour finding out what was in that document...