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.

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?

Comments URL: https://news.ycombinator.com/item?id=44920437

Points: 12

# Comments: 5

Comments URL: https://news.ycombinator.com/item?id=44914731

Points: 2

# Comments: 0

- 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

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.

Comments URL: https://news.ycombinator.com/item?id=36223232

Points: 2

# Comments: 0

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.

>> It runs on emotion

So, I think, you are right.