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

source: dragonflydigest

Plan 9 was intended to be Unix, done better. It preemptively replaced a lot of what we now bodge together with virtual machines, containers, and even microkernels, and it did it more simply and cleanly. But it wasn’t compatible enough to replace its ancestor. With off-the-shelf existing 21st century tech, we can fix that.

source: fosdem2024

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

What is the even loop and how it is supposed to work?

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

source: communications of the acm

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.

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.

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

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

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

Lawrence Gilman Roberts (December 21, 1937 – December 26, 2018) was an American engineer...

As a program manager and later office director at the Advanced Research Projects Agency, Roberts and his team created the ARPANET using packet switching techniques invented by British computer scientist Donald Davies and American Paul Baran.

source: book; where wizards stay up late

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

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

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

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.

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

source: queue.acm.org