There is a well known Github Gist
“Latency Numbers Every Programmer Should Know”,
which explains which things take how long.
Here is a user story for
implementors of security systems and platform hardening initiatives:
Seriously, HR people ask the weirdest questions.
Today is a weird day. First thing is a friend asking about help with
community management. And next thing is Fefe reiterating his longstanding
fallacy (Rant in German) that
programmers are able to do anything just because they are able to do one
thing (here: Community Management). The TL;DR is that he rants against
non-programmers showing interest into programming projects because they
like the software, thereby ruining everything by not being programmers.
The history of serialize() and unserialize() in PHP begins with Boris
Erdmann and me, and we have to go 20 years back in time. This is the day of
the prerelease versions of PHP 3,
some time in 1998.
So you are running systems in production and you want to collect data from
your systems. You need to build a monitoring system. That won’t work and it
won’t scale. So please stop for a moment, and think. What kind of monitoring
do you want do build? I know at least three different types of monitoring
system, and they have very different objectives, and consequently designs.
There is an interesting article by Brendan Gregg out there, about
the actual data that goes into the Load Average
metrics of Linux. The article has a few funnily contrasting lines. Brendan
So why is everything so complicated? At work, I mean.
So some people, companies even, have
guidelines that describe how to write shell scripts, or even
unit tests for shell scripts,
as if “UNIX Shell” was a programming language.
»@mipsytipsy I thought “You have to test in production” was a bold statement
and would love to hear more of your thoughts on the