Monolith vs microservices ... small server vs big server...

We have all gotten so familiar with virtualization and abstractions between our software and the servers that run it. These days, “serverless” computing is all the rage, and even “bare metal” is a class of virtual machine. However, every piece of software runs on a server. Since we now live in a world of virtualization, most of these servers are a lot bigger and a lot cheaper than we actually think.

It’s hard to believe, looking at the modern computing world, but there is still more to life than Windows or Unix… and today, most of the alternatives run on vanilla x86 hardware and are free.

this collection of thoughts on software development gathered by grug brain developer

grug brain developer not so smart, but grug brain developer program many long year and learn some things although mostly still confused

There is something special in simple code. Here I’m not referring to simplicity to fight complexity or over engineering, but to simplicity per se, auto referential, without goals if not beauty, understandability and elegance.

Simplicity is the heart of the Unix philosophy. The more code lines you have removed, the more progress you have made. As the number of lines of code in your software shrinks, the more skilled you have become and the less your software sucks.

With the “Web Development Manifesto” we strive to maintain minimalism and clarity to drive web development to a completion that result in a much more sane World Wide Web.

source: https://unixsheikh.com

The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed does not mean you should stop others from building one just because you do not like the color they plan to paint it. This is a metaphor indicating that you need not argue about every little feature just because you know enough to do so. Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change.

a. Learn to learn
b. Learn to question things
c. Acquire the permanent habit of learning

A curated list of openbsd’s innovations

Adoring admirers have fed Linux goodies to a disheartening state of obesity.
If only some reincarnation with the genius and sensibility of Ken Thompson and Dennis Ritchie were still guiding the evolution of Unix!

source: https://www.wikiwand.com/en/Unix_philosophy

Long ago, as the design of the Unix file system was being worked out, the entries . and .. appeared, to make navigation easier....

Make something. Participate in something. Engage with someone. All of it might feel as unnatural as strapping on those running shoes after too long of a break, but once you’re back to creating, the energy comes by itself.

There are hackers—believe it or not—who just love the art of building software. They do it for the challenge, for the fun of it. They aren’t trying to make a million dollars.

Architecture is hard sometimes--people keep offering up some new idea that quickly becomes the mainstream “way to do it” without any context or nuance, and the industry, desperate to find ways to improve their architecture, snaps it up without hesitation. Microservices was the latest in the trend, and it’s time we dissected the idea and got to the real root of what’s going on.

source: CaptainPatate

Did Ken, Dennis, and Brian choose wrong with NUL-terminated text strings?

source: communications of the acm

* Décongestion de réseaux
* Débuggage de logiciels
* Protection contre les virus
* Protection contre les tentatives d’intrusions
* Restructuration de services
* Partage de connexion Internet sans connexion
* Suppression aléatoire de compte utilisateur
* Protection anti-spoofing basée sur les adresses MAC
* Définition de politique de gestion et de sécurité aléatoire
* Elimination systématique des fichiers de log (journaux)
* Protection contre les DoS et DDoS grâce au système exclusif InUranus®
* Support de IPoT
* Rend vos données importantes accessibles à tout moment et à tout endroit
* Débloque les claviers qui se bl

source: CaptainPatate

Talk from Andrew Kelley about data oriented design and how it can help to reduce memory footprint from workload with careful design.

What happens inside the cpu? how things get delayed...