Kevin N.

@noel-kevin.be

Dev, K8s, Infra, SRE, Golang, ex-Java @kevinnoel_be@fosstodon.org

Et voilà ma chronique sur C'était ça ou mourir, de Thélyson Orélien, qui double mon avis littéraire avec un billet d'humeur, parce que ça s'imposait. Pour une fois, je me sentais légitime à l'ouvrir, dont acte. syndromequickson.com/2026/09/25/r... Salutations vulcaines.

RL26 #13 – C’était ça ou mourir, Thélyson Orélien

Fame is a Gun – Addison Rae (extrait l’album Addison) Je n’avais pas prévu de lire ce roman, au départ.Pour tout un tas de raisons plus ou moins mesquines. Grasset, d’abord.…

syndromequickson.com

With AI assistance, Operations now costs more than Development. The question is not “Build vs Buy” any more. Buying software and operating it yourself takes more effort than operating something you built and own. The question is “Staff it or Outsource it?”

JFrog Xray is defective, flagging unaffected binaries as vulnerable, and the cost is borne by maintainers who have to field requests to work around it. This is a real open source sustainability issue. (The problem here is JFrog, not the person who politely opened the issue.)

v1.3.1 release binaries embed Go toolchain vulnerable to CVE-2025-68121 (crypto/tls session resumption) · Issue #730 · FiloSottile/age

Summary The published v1.3.1 release binaries appear to be built with a Go toolchain that predates the fix for CVE-2025-68121 (Go issue golang/go#77217), a crypto/tls session-resumption vulnerabili...

github.com

Instrumenting apps on plain Linux hosts meant downloading agents by hand and wiring up env vars. Not anymore. The new OTel Packaging SIG shipped its first repo: the Injector plus auto-instrumentation for Java, .NET, Node.js and Python, as system packages. opentelemetry.io/blog/2026/pa...

One-command OpenTelemetry setup on Linux hosts

OpenTelemetry as system dependency Setting up OpenTelemetry for your applications and systems depends on where those apps and systems run. Some are very automated, especially Kubernetes, thanks to…

opentelemetry.io

I truly can’t get over the fact that we chose YAML-interpolated shell scripts as the default CI programming language. It’s so bad that we forgot how to handle untrusted inputs! (pull_request_target and issue_comment triggers should not be that unsafe! It’s just attacker controlled input.)

Chris Krycho@chriskrycho.com · 5mo ago

🧊 take: YAML pipelines are a pit of failure for CI/CD pipelines. They attract people because they seem declarative and the syntax is “easy”, and they have become “standard”, but everyone ends up encoding subroutines and data flow into them—and YAML is a terrible programming language!

I don't think tech at large understands how hard it is to be an open source maintainer right now. So many great folks are on the brink of burnout. Funding is drying out. We live in a security minefield. Companies think humans are disposable. If you're a maintainer, we care. You deserve the world.

The GitHub remote execution bug is fine and all, but the bigger story is the LLM (with IDA) quickly decompiling GH's binaries to enable the analysis. A lot of companies shipping "closed" binaries are going to learn the hard way that they might as well be shipping source. www.wiz.io/blog/github-...

Bild

Our third feature on real-world #OpenTelemetry deployments focuses on Skyscanner, a global travel search platform. With more than 1,000 microservices across two dozen production clusters, Skyscanner operates #OTel at scale. Read our latest post for their valuable insights! buff.ly/oIqBiJF

How Skyscanner scales OpenTelemetry: managing collectors across 24 production clusters

The Developer Experience SIG is publishing a series of blog posts featuring real-world OpenTelemetry deployments from companies across different industries and scales. This post features Skyscanner,…

opentelemetry.io