> I don't think the government applying such levers to change how the market allocates capital probably won't be a win for economic output or quality of life.
We've got China cheating with their massively deflated currency, so how the market allocates capital is already screwed.
you probably didn't read news lately. your CNY deflation theory is no longer being cooked by your MSM for a good reason - if the CNY deflation claim is true, then it means the Chinese economy has probably already surpassed the US economy not just in PPP but in real term as well. That would cause huge load of issues for the US which is never prepared to be the No.2.
At that scale it is cheaper. If you have a requirement for only a few dozen, then webhostingtalk is all you need. When you need 100k servers, you will be managing the hardware yourself
>It wont be easy or painless but it wont be impossible either.
With data egress costs, all the security infrastructure built up is all bespoke to a provider, not to mention engineers relearning the new provider's APIs and all its warts. The cost would be HUGE. Would be something that would go to a board for approval.
The biggest problem is getting everyone aligned, designing a plan with minimal rework, and being able to hire incredible talent that is going to cost far more than most companies are willing to accept.
For most companies they'll try with their existing talent and it'll be +5 years and an absolute failure.
And the very sizable opportunity cost of the engineering time spent on that project and not in anything more pressing. If your platform team has nothing better to do then I guess that's 1.5 years well spent, but if they have nothing better to do I have some questions about your company's engineering decisions.
No this argument is not analogous. I worked for a bank that upped and moved offices on a commercial lease renewal. Let me know when you hear of a bank migrating Cloud providers and I will reconsider. It is 100% vendor lock in, no escape.
I like this, package.json starts to look really ugly when you build up lots of scripts that need to run interdependently. For example some stubbed back ends, front end, some auth service, etc. You end up with ugly long npm scripts with &&s everywhere. However for this sort of thing, personally I'd rather use docker compose, dependencies are explicit and declarative, like this I guess. You can define
health checks for services with docker compose too.
I feel like Slack is 80% of the problem. Honestly I'd like to get rid of it at our company, and just have everything come down/go back up through my manager. I realise some of you probably have never experienced this.
I heavily agree. It’s something I had at my first office job. I had no email address, no messaging app, everything came through my PM or manager. Ive never been as productive as that job. Straight to work with no distractions and had clear goals.
The fact that Dmitry was still pushing changes on the aeroplane, although he seemed to frame this as a positive, doesn't exactly inspire a lot of confidence in their professionalism, viewed from the outside.
OP learnt about idempotency in http the hard way. However the post reminded me that I don't particularly like this hydration step of NextJS apps where there is javascript executing that is difficult if not impossible to step debug.
We've got China cheating with their massively deflated currency, so how the market allocates capital is already screwed.
reply