Being an OAuth provider is precisely what everyone expects from a self-described "open source authentication service". If Supertokens does not support that out of the box, it should not really be called an open source authentication service.

I understand you want to capitalize from your work, but I feel this is a gross misrepresentation of a project.

There have been a few variants that have a markedly change in their ability to spread and also their severity. They might be hitting people differently. I mean, if the same person is getting infected multiple times with carrying degrees of severity, something is changing in the infection.

People get work done by knowing what they're doing, which I'm not sure you are able to tell.

There is plenty of literature that explains quite thoroughly the process of software architecture. Basically all major software architecture styles from the past four decades reflect the need to encapsulate and insulate implementation details, including the need to specify a domain model and how it should be specific and exclusive to each project.

Somehow, you are oblivious to basic principles but still feel entitled to insult others based on domain knowledge you clearly lack.

Yes. I recommend you read "Domain-driven design" by Eric Evans, specially the part explaining the concept of a bounded context.

> Alternatively, if Galactus has a published schema that I refer to, isn't that a shared data structure?

No, that's the interface.

> not only we deduplicate code

You don't. You just needlessly add a constraint for no reason at all, and in the process make your life a mess.

It looks to me they recommended to never consider Datadog for anything whatsoever, ever again.

As a proficient LaTeX user, this is the stupidest take I ever saw on resume tips. I mean, your skills and experience do not vary with the document system you used to generate your CV. Some hiring managers swear by MS Word templates, other hiring managers ask for Europass, others ask you to fill in a form and request a cover letter. It would be stupid to assess the suitability of any candidate on this sort of bullshit.

I'm not sure you got it right. You still have a LaTeX doc if you compile it to generate a PDF. LaTeX can have a very unique and peculiar look and feel that pops up to those in the know.

This is stuff that precedes other policies like placing ICU patients prone/lying face down to improve breathing.

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8864017/

It makes absolutely no sense at all to fabricate conspiracy theories based on the assumption that everyone in the world was systematically subjected to a procedure which was rejected right from the start.

What other options do you think there are?

And consider that you're already talking about people which are fainting and suffocating.

Some sources point out that only 10-20% cases of covid are admitted to intensive care unit, and 80-90% of cases are mild.

I seriously doubt that up to 90% of the population has "optimum levels of vitamin D".

What microservices easily provide in this scenario that is far harder to pull off with a monolith is that with microservices the service owners are able to roll out a dedicated service as a deliverable from that dialogue. Whether the new microservice implements a new version of the API or handles a single endpoint, the service owners can deploy the new service as an extension to their service instead of a modification, and thus can do whatever they wish to do with it without risking any impact on their service's stability.

Technically it works, but it requires some work. You need to pass off ccache's executable as the target compiler, and you need to configure the settings in all vsproj files to allow calls to the compiler to be cacheable, like disabling compilation batching.

Using cmake to generate make/ninja projects and use compilers other than msvc is far simpler and straight-forward: set two cmake vars and you're done.

That's perfectly fine, because microservices excel in that scenario: just hand over the keys to the repo and the pipelines, and you're done.

This sort of specious reasoning just shows how pervasive is the fundamental misunderstanding of the whole point of microservices. Microservices solve organizational problems, and their advantages in scaling and reliability only show up as either nice-to-haves or as distant seconds.

Microservices can an do make sense even if you have 10 users making a hand full of requests, if those services are owned and maintained by distinct groups.

In professional software development projects, specially legacy projects, often times the complexity is not justified by the problem. There is always technical debt piling up, and eventually it starts getting in the way.

The main misconception about microservices is that people miss why they exist and what problems they solve. If you don't understand the problem, you don't understand the solution. The main problems microservices solve are not technical, but organizational and operational. Sure, there are plenty of advantages in scaling and reliability, but where microservices are worth their weight in gold is the way they impose hard boundaries on all responsibilities, from managerial down to operational, and force all dependencies to be loosely coupled and go through specific interfaces with concrete SLAs with clearly defined ownerships.

Projects where a single group owns the whole thing will benefit from running everything in one single service. Once you feel the need to assign ownership of specific responsibilities or features or data to dedicated teams, you quickly are better off if you specify the interface, and each team owns everything begind each interface.

Some build systems like cmake already support unity builds, as this is a popular strategy to speed up builds.

Nevertheless, if speed is the main concern them it's preferable to just use a build cache like ccache, and modularize a project appropriately.

What exactly leads you to have multiple declarations in sync, and thus creating the to "keep [multiple] declarations synced"?