Everything is hard until you’ve done it at least once. Making shit work is hard (excluding cases when your particular task has been solved and shared with you)

If it was that easy I would never miss my ETAs.

Things are uncertain(were they ever certain?), every day there is another armageddon prophecy screaming at you from social media and newspapers.

So one can try to hedge, squeeze more out of oneself to make sure he did all he could.

I don't know how stringent the geo check for claims is, but as soon as you become an EEA resident you can invoke GDPR.

I would recommend to ask Google’s DPO anyway.

This has magically unbanned me in less than two days. In contrast to two months of tweeting, emailing support, nagging my google eng friends and even support folks via linkedin.

Only invoking GDPR and the ownership of a domain name allowed me to regain access and restore email service. Without GDPR I would've got nothing at all.

But at the same time it doesn’t have to be that bad. I don’t have this array of issues because I do: - query whitelisting for performance and security, - data loading to avoid n+1, authentication with whatever works(session cookies, tokens), - permission check based on the auth context in a resolver.

It works decently for us, allowing to stay away from getting into ESB. Yet have some shared domain, type safety, and easy integration of legacy and new systems/services.

I would say a bigger issue for us was to keep it all nicely organized / designed in terms of types and api contracts. But that’s manageable.

All people want is to live in a quiet and a nice place after all.

Why someone who doesn’t even live there but has a bigger buck should decide?

https://guides.rubyonrails.org/layouts_and_rendering.html#us...

There's no standard way for handling hot reloading, but there's a bunch of recipes on stackoverflow.