sashokbg

A blog article I wrote with some thoughts regarding the productivity and complexity related to data and project fragmentation.

I wrote an article and created a sample repository showing how we can apply TDD & a rich non-anemic domain model as described in DDD in a frontend project.

The study case uses React and Signals, but is mainly about the principles and not the technologies involved.

I disagree with this article. The author takes some very edgy cases such as "undergraduate student" and "transgender CRP number".

Even the example for the restaurant and "time based id number" are bad because they all indicate that you just badly identified the entities (in DDD terms) and their identity.

So being bad at DDD doesn't mean that you can't use natural keys (although I myself have arguments against them)

I live in Europe (France) and I don't have the part "As part of the Facebook family of companies .." in the EULA that is presented to me. Maybe they have different versions and the one in EU is kinda still OK ?

You have to be completely nuts to put your secret keys in a site on the web.

So ? I know there is still slavery. There are still people who die, should I stop using the phrase "the server is dead" because I might offend you since you lost your grandma ?

If we spent our time changing specs every time someone somewhere gets offended by something that didn't even happen to their generation, we will be spending all our time doing only this.

I do not agree at all with this article. Most people are jealous haters and it is perfectly normal to have a lower salary if you don't have the guts to ask for more.