I was surprised that PG supported this idea so publicly for so long. Best of luck for the team on their next product.

This reminds me of the ScriptMethod thing that asp.net has in the early days of AJAX. Was fun to use it, but didn’t stand the test of time. https://learn.microsoft.com/en-us/aspnet/web-forms/overview/...

Maybe there has been enough changes in the ecosystem now to be able to abstract network and write code that’s not too brittle.

I actually have plans to make Telefunc also have sensible defaults for network failure. So that the user doesn't have to take care of that (while the user can customize failure handling if he needs to).

I took this idea from my PhD supervisor and found it to be incredibly useful.

Before writing down a long form doc, make a quick mondmap answering the following:

1. What are the three core ideas you’re writing about? 2. What are the three main criticisms / counter arguments against your ideas? 3. How do you plan to respond to the criticisms?

Depending on the subject matter and length of the doc, you may need more or less than three. But see if you can get this mind map written first. Then, see if you’re convinced the ideas are worthy of writing. Only then write the long form.

*mindmap

If you have healthy kids, they become mostly independent at age 4-5. You may want to consider a 5 year plan in Germany, or even a 3 year plan, and then reassess. It doesn’t have to be a one way door.

You’ll have plenty of time to accumulate wealth beyond the next 5 years. And you’ll still accumulate some even in Germany.

Try doing a mock interview and really act on any feedback you get.

Microservices primarily solve a team scaling problem. Then comes technical.

The question is from what team size on microservices make things easier. I bet the number is much bigger than what people think.