msiyer

Thank you! Happy to see a positive comment. Took a lot of effort.

I like long-form writing. However, it takes a lot of effort. So, I end up not writing often.

It is a hot topic especially among polyglots who have to deal with the same word meaning different in different languages.

... that is how you achieve a good design (for the time being).

> Avoid having five different services all write to the same table. Instead, have four of them send API requests (or emit events) to the first service, and keep the writing logic in that one service.

The ideal solution: Avoid having five different services all write to the same table.

If five different services have to write to the same table, there is a major overlap of logic too. Are the five services really different or one would suffice?

Taking practical realities into consideration, we can do what the author says. However, we risk implementing a lot of orchestration logic. We introduce a whole new layer of problems. Is that time not better spent refactoring the services: either give them their own DB tables or merge them into one servic?

move on.

A Reddit debate over C# vs. Java int, sparked by a Microsoft engineer’s claim that C#’s int is a primitive, revealed confusion amplified by `Type.IsPrimitive`. This led to the Lₐₓ/Lₐₜ/R (LAX/LAT/R) taxonomy: a framework to classify types by their language-level, atomic, and runtime properties, resolving disputes rooted in specs and tribal knowledge.

Learning biology to understand software-system concepts is underrated. For example:

- the way pain-killers work tells you a lot about how keyloggers or man-in-the-middle attacks work

- look at how DNA "syntax checking" happens during mitosis to learn about compiling in general

- a puppy swallows whatever it sees; this gives the immune system enough test data about the surroundings etc. (similar to ML)

- a huge amount of cyber-security concepts can be understood by learning biology

there is nothing "basic" about this. something that seems pretty obvious to you may not be natural to someone else.

i think the single-click navigation or opening of files was done to mimic how hyperlinks on the internet work. some people are wired that way.

on the other hand, some people have a completely different brain configuration: they think that a single-click should select whereas a double-click should open a file.

there are people who do not agree with both these options. maybe, they want everything to work via audio commands.

how do we decide what the default behavior should be? the answer is: leave it to the user.

WD screwed up. However, users must have a backup policy for when (not if) data hits the fan. For important data, having multiple onsite copies with few of them totally dumb (as opposed to smart IoT) and multiple offsite copies should become a habit.

I am not saying you are wrong; just providing another perspective. When every penny you *spend* or *save* is taxed, you end up paying more than 50% of what you made to The Man. Either tax the income or tax the spending, not both, is my argument.

It will trickle down one day. You just have to wait for it.