TobiasA

How do people handle versioning events, like adding/removing/changing properties? It seems like your application would always need to be aware of all previous event versions to be able to replay all events.

I don't see how it's despite of that. Original doesn't always mean better.

"Using GitHub for personal projects is stupid" is a hell of a take.

I have never heard of code ownership being a positive thing. Isn't this more an issue of encouraging internal knowledge sharing and confidence in refactoring?

Per your last point, why don't you think ORMs work well with complex domains?

Which headaches would that be?

JWTs are designed to be stored in the client that needs to be granted authorization to resources. Nothing wrong with storing tokens in the frontend.

Thank you so much, this is perfect!

I'm a self taught programmer with a very weak maths background. What's the best learning path for me if I want to be able to understand and create ML based applications?

The short answer is that they sell it to other countries/nations that can't produce energy that efficiently.

Way to miss the point.

I'm working on a project where we have two projects: a desktop app and a web backend. They each live in their own repo. However, this approach is proving tedious for us now, as every new feature often means two branches (one in each repo) which also means two separate pull requests when the feature is ready to be merged. Has anyone encountered this kind of issue, and is the solution to simply merge the two repos into one monorepo?