El análisis póstumo de la elección de Kamala Harris y su posterior desastre.
https://democrats.org/wp-content/uploads/2026/05/May-20-2026.pdf
Баги, которые нас воспитали: инженерные истории с Go Loto
Каждый разработчик помнит тот самый момент, когда система, которая только что работала идеально, вдруг начинает вести себя так, будто сошла с ума. Когда дашборд в Grafana показывает что-то страшное, а ты стоишь перед ним с кружкой остывшего кофе и не понимаешь, с чего начать. На нашем мероприятии Avito Go Loto разработчики поделились своим опытом без прикрас. О блоате в полтора терабайта, о девяти инстансах, которые передрались за один звонок, о бэкенд-разработчице, которая в пятницу вечером открыла чужой фронтовый проект, о нагрузочных тестах за несколько месяцев до большой рекламной кампании, и о транзакции, которую забыли закоммитить тоже в пятницу вечером. Спойлер: все выжили. Но стали другими людьми.
https://habr.com/ru/companies/avito/articles/1037846/
#go #bloat #vacuum #микросервисы #распределенные_системы #нагрузочное_тестирование #postmortem
Как auto-update n8n нашёл мину которая лежала 8 месяцев в node_modules
20 мая в 06:01:55 МСК Watchtower по расписанию проверил 14 контейнеров на нашем VPS, нашёл 5 обновлений и пересоздал. Среди обновлённых - n8n, который крутит production-вебхуки нескольких проектов студии (в том числе SaaS Подробнее
https://habr.com/ru/articles/1037434/
#n8n #docker #watchtower #monitoring #incident #postmortem #selfhosted #observability #crashloop #devops
Hello and welcome to Melanculia.
The brand new album Post Mortem is out now. You can listen to it here -> https://melanculia.bandcamp.com/album/post-mortem-2
✨💀✨
#melanculia #postmortem #music #newrelease #gothic #indie #alternative #ninosable
The Post-Mortem Problem
소프트웨어 엔지니어링에서 포스트모템(post-mortem)은 흔히 형식적 절차로 전락해 실질적 학습 도구로서의 역할을 하지 못하는 문제가 있다. 효과적인 포스트모템은 사건 직후 감정과 맥락이 생생할 때 빠르게 작성되어야 하며, 단순 로그 나열이 아닌 사건의 경험을 이야기 형식으로 전달해야 한다. AI는 사건 요약과 초안 작성 같은 반복 작업을 지원할 수 있으나, 분석과 교훈 도출은 인간이 주도해야 한다. 또한, 포스트모템 작성 기준을 낮추고 읽기 기준을 높이며, 후속 조치를 구체적이고 책임 있게 관리하는 문화가 중요하다.
https://incident.io/blog/the-post-mortem-problem
#postmortem #incidentmanagement #softwareengineering #aiassistedwriting #devculture
Post-mortems are one of the most consistently underperforming rituals in software engineering. Most teams do them. Most teams know theirs aren't working. And most teams reach for the same diagnosis: the templates are too long, nobody has time, nobody reads them anyway.
When two Hetzner servers died at the same time
On May 12, 2026, two of my Arch Linux + LUKS servers at Hetzner became unreachable at the same moment. Both had been running for 4+ months without issue. Both had received the same pacman -Syyu the day before, but had stayed on the old kernel until the morning the websites stopped responding. I rebooted — SSH never came back. nmap -Pn -p 22 showed filtered from anywhere. No ping. No banner. The Hetzner Robot panel insisted the hardware was fine.
Several hours went into hypotheses that turned out to be wrong:
Mathrubhumi English
lord pthenq1
Habr
melanculia
sayzard
Kevinencryptssh initcpio hook referencing a /usr/lib/initcpio/udev/11-dm-initramfs.rules file that no longer exists. Real bug, no boot impact — the initramfs rebuilds anyway.PermitRootLogin no in sshd_config. Real misconfiguration, fixed it, didn’t help. A refusing sshd shows closed, not filtered..network config to match by MAC. Useful hardening; not the cause.core.img in the MBR. Arch never re-runs grub-install after a grub package upgrade. Refreshed it. Still filtered.The clue was in the persistent journal: a single recorded boot from December 31 to May 12 10:13 UTC, and absolutely nothing after. Every reboot since the upgrade was failing before systemd-journald could flush to disk — so the failure had to be in the initramfs, before the root filesystem was even mounted.
What it almost certainly was
Hetzner Dedicated servers configure the initramfs network with ip=dhcp on the kernel command line. That depends on Hetzner’s DHCP server replying to whatever request format the current kernel sends. Somewhere between kernel 6.18 / iproute2 6.18 and kernel 7.0 / iproute2 7.0, the request format changed enough that Hetzner’s DHCP stopped responding. Effects:
filtered.Hetzner’s own documentation has been quietly moving away from ip=dhcp toward static IPv4 in the kernel command line. The fix is exactly that:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/md1:cryptroot ip=A.B.C.D::GATEWAY:255.255.255.255:hostname:eth0:none"
One line in /etc/default/grub, grub-mkconfig, reboot. No more dependency on Hetzner’s DHCP responding to whatever your current kernel sends.
Why it matters for anyone running this stack
If you run Arch on Hetzner Dedicated with full-disk encryption and remote unlock via dropbear, the ip=dhcp shipped by installimage is a latent bug. It can keep working for years and then break overnight, on every machine you have, after a routine pacman -Syyu. The static-IP version is what Hetzner now recommends and removes the entire dependency.
Tooling
While debugging, I turned the whole rescue / chroot / diagnose / fix workflow into a Python CLI (hal) — including hal fix static-ip, which derives the static cmdline directly from your existing systemd-networkd .network file:
→ github.com/kevinveenbirkenbach/hetzner-arch-luks
Single command, idempotent, reversible (the original /etc/default/grub is backed up to .hal-backup). If you’re on this stack, switch to static IP before the next kernel upgrade catches you.
Someone shared a cool thread about his #vibe-coding experience :
#vibe_coding #ai #llm #slop #aislop #fraud #scam #dev #postmortem #gamedev
Holy civilised AI thread. And good on you for not only noticing that it doesn’t work but also telling others about it. I see a lot of people justify vibe coding by saying that the programmer telling them already knows how to code so it’s different. And this is great for that. Thnx.
The Disturbing Origins of the Camera
Ordinary objects. Disturbing origins. Taking a photo feels natural. You capture a moment. Save a memory. Move on. It’s something you do without thinking. But in its earliest days, photography had a very different purpose. It wasn’t about preserving life. It was about preserving death. A Time Before Easy Memories In the 19th century, photography was still new, expensive, and far from accessible. Most people would never have their picture taken. Not while they were alive. For […]https://darkbydesign7.wordpress.com/2026/05/05/the-disturbing-origins-of-the-camera/
Harold Cath
Denis Salem
Dark By Design