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.

I thought the same then I thought that maybe they should show instructions to create a user that only has the bare needed access. After you run, you revoke. I could see myself using something akin to this when tearing down old stuff.

Not sure that's gonna be enough assurance, my friend

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.

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 ?

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.

In other words, it's OK not to be paid according how well you do your job, but according to your negotiating skills?

You pay the asking price if the product provides you enough value. Negotiation is simply setting the asking price, which is absurdly mundane in a free market economy. In fact, not setting an asking price - thus letting the buyer decide what he pays - contradicts norms.

The metric of “how well you do your job” is highly subjective anyhow; between an employee, their manager, their product manager, their coworkers and HR there would be significant variance of opinion.

1. Negotiating skill is a skill as any other soft skill.

2. If somebody consider that he doing the same job (have the same skill) it doesn't mean that it's true.

If negotiation is not a skill that affects your job performance it seems unfair that it has such a big influence on your pay.

That’s how sales work unfortunately

Just because something is currently "perfectly normal" doesn't mean it should remain that way. People should be incentivized to do good work, not to be good negotiators (unless their job involves negotiation).