Every week one of us writes about a case from our work: an end of support date, an upgrade, an incident or a vulnerability, and what it means for your own system. Every post names its author and its sources.
Editorial calendar 2027monthly
- PHP 8.2 without security updatesJanuaryin progress
- NISG 2026 and your clientsFebruaryplanned
- Node.js 22 reaches end of lifeMarchplanned
How we write our posts
Each post starts from an entry in Lobster7, our knowledge base, where we record what we learn at clients and on our own servers. Before a post goes online we check versions, dates and commands against the vendors’ documentation, and those sources are listed under every post.
The authors take turns, so each week it is someone else from the team. The person named as the author has read and approved the post. We do not name clients, and we make sure none can be recognised from the text. Every post appears in German and English at the same time.
The occasion often comes from the EOL calendar. When a version falls out of support, we write about the options and what each of them costs.