substack concurrent
Shipping software to production so it’s available to real users is the ultimate goal of every digital product development team. There is no value in specs, designs, or changes committed to git, unless the code has made it to the production system and thus into the hands of users. The best teams ship dozens of times per day, every day, instead of every 2 weeks on particularly designated release days, or only at the end of the sprint – for those teams, shipping is a permanent state rather than an occasional event.
Clients (hopefully bots) that disregard robots.txt and connect to your instance of HellPot will suffer eternal consequences.
HellPot will send an infinite stream of data that is just close enough to being a real website that they might just stick around until their soul is ripped apart and they cease to exist.
Under the hood of this eternal suffering is a markov engine that chucks bits and pieces of The Birth of Tragedy (Hellenism and Pessimism) by Friedrich Nietzsche at the client using fasthttp.
A live ranking of airlines by how much luggage they are losing right now
A simple testing library for bash scripts
Test your bash scripts in the fastest and simplest way, discover the most modern bash testing library.
This branching model was facilitated with the advent of very lightweight branching that came with Git and Mercurial in the mid-2000’s, though there is evidence that Google were effectively doing the same in their Monorepo for some years before.
FrankenPHP 1.2 is out 🎉
- Caddy 2.8
- X-Sendfile/X-Accel-Redirect support
- full-duplex support for HTTP/1
- simplified config
- countless bug fixes and docs improvements
Upgrade now!
Fastly Edge Cloud Platform
Comment rendre une organisation aussi adaptable et polyvalente que son environnement ? Comment pouvons-nous préparer une entreprise à survivre et à prospérer au 21e siècle ? De nombreux modèles et frameworks vous proposent des solutions statiques ou pré-packagées. Il est temps de trouver une alternative à SAFe, LeSS, l’holacracy, le “modèle Spotify” ou encore aux organisations matricielles. Nous avons besoin de quelque chose qui porte la flexibilité à un nouveau niveau. Voici ma suggestion. Je l’appelle UNFIX.
Ah juste un truc absolument génial avec zstd :
Imaginez que vous voulez compresser la sortie d'un dd, netcat ou scp.
Si vous prenez un taux de compression trop bas, vous perdez en ratio de compression.
Si vous le choisissez trop haut, vous perdez du débit (le CPU prenant trop de temps).
Et bien zstd peut s'adapter au débit I/O ou réseau avec l'option --adapt.
Vous aurez ainsi la meilleure compression possible sans ralentir votre débit.