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.

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

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.

In short, the argument goes, the ability to write scheduling policies in BPF greatly lowers the difficulty of experimenting with new approaches to scheduling. Both our workloads and the systems they run on have become much more complex since the completely fair scheduler was introduced; experimentation is needed to develop scheduling algorithms that are suited to current systems. The BPF scheduling class allows that experimentation in a safe manner without even needing to reboot the test machine. BPF-written schedulers can also improve performance for niche workloads that may not be worth supporting in the mainline kernel and are much easier to deploy to a large fleet of systems.

source: https://lwn.net

Think about all the things they’ve told you that you 𝑛𝑒𝑒𝑑. HTML is NOT the answer!

source: https://hackers.town/@lmorchard/109444911452419131

source: https://tratt.net/laurie/blog/2023/how_big_should_a_programming_language_be.html

In this article, we provide a holistic view of the Portable Operating System Interface (POSIX) abstractions by a systematic review of their historical evolution. We discuss some of the key factors that drove the evolution and identify the pitfalls that make them infeasible when building modern applications.

source: https://www.usenix.org

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

source: communications of the acm

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.

Meaningful problems are the most valuable human motivators. Made-up problems are a blight. Ensure you have not quite enough time and people available to tackle the former lest you start inventing the latter.

source: dhh

Paul Baran (born Pesach Baran /ˈbærən/; April 29, 1926 – March 26, 2011) was a Polish-American engineer who was a pioneer in the development of computer networks. He was one of the two independent inventors of packet switching.

source: book; where wizards stay up late

Real, productive workers are relentlessly squeezed and exploited. The remainder are divided between a terrorised stratum of the, universally reviled, unemployed and a larger stratum who are basically paid to do nothing, in positions designed to make them identify with the perspectives and sensibilities of the ruling class (managers, administrators, etc.)—and particularly its financial avatars—but, at the same time, foster a simmering resentment against anyone whose work has clear and undeniable social value.

source: dhh

* 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

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

source: dragonflydigest

Writing is key to have impact in large organizations. As a senior software engineer chances are that writing is the most important skill you have to acquire in order to increase your scope beyond the team and advance your career.

This article contains some learnings that have helped the author to become better and more productive as a writer over the past 15 years.

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