> 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?
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.
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.
I am Mechanical Engineering graduate pursuing my Masters in Software Systems after 10+ years of industry experience.
Attack the Type System first. Do not read PhD research papers, just the practical aspects of it:
- Why is it that integers I am working with are 8-bit (or 16-bit or 32-bit ...)?
- What is "int x = 7;" translated into by the compiler?
- How is basic arithmetic implemented in the hardware? Integers, floating point etc.
- If my system has 16-bit integers, for example, how can I deal with larger numbers than what 16 bits can accommodate? Some SW implementation to hide HW limitations?
Then go on to understand how more complex types are implemented etc.
From there go on to things like Stack Frames and Heaps and Application Binary Interfaces.
From there go on to memory clean up and why we need Garbage Collectors etc.
...
To me, a Programming Language is a set of rules (enforced by a compiler or interpreter) for deterministic bits manipulation. The Type System is the core set of rules around which everything else revolves. Even lack of a Type System in a language is a Type System.
The "set of premises and goals" we currently operate upon are not ours, but planted by someone else (parents, teachers, media...).
Add to all this the fact that world may run however it wants, but the emotions are ours. If we alter the "set of premises and goals" we can alter our emotional response.
I do not mean to offend, but this is what schooling does to most humans - you commute to school, have clear distinction between home and school spaces, have clear distinction between school and neighborhood buddies (some overlap happens), various rituals...
Banning a word is pointless. The word itself has no power. It is the feeling piggybacking on the word that gives life to the word. The feeling will find another word as vehicle.
I am talking about efficient use of available space. A terabyte may store a lot of pictures, but if we can achieve the data density of DNA, we may be able to process (store, transmit, transform...) far more amount of data far more quickly. Then text vs multimedia will become irrelevant.
If we agree that a picture is worth 1000 words, then...
Given the current state of information technology, I agree that we are most efficient at processing text. However, that can change pretty quickly. Storage mechanisms similar to DNA can make the difference between text and multimedia irrelevant. It will happen because nature already does that.
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.