Skip to content
View cedi's full-sized avatar
💭
I may be slow to respond.
💭
I may be slow to respond.

Organizations

@bio-routing @open-infrastructure @cedi-dev

Block or report cedi

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
cedi/README.md

👋 Cedric Kienzler - @cedi

Hi, I'm cedi.

I’ve done everything wrong the first time so you don’t have to. Trust me, I’m an engineer.

I work as a Senior Software Engineer at @Microsoft Azure. I am interested in distributed systems, site reliability engineering, and just generally working at large scale.

I am involved in somme stuff at the Chaos Computer Club where I led the Network Team at GPN for two years and I help with the builtup, planning, and a million other things at various events trough the year, most notably the Chaos Communication Congress at the end of every year. During the pandemic - when the in-person events where unable to happen - I helped to build online services like jitsi.rocks, open-infrastructure, or the rC3 - NOW HERE.

In my sparetime I love playing around with Kubernetes, Raspberry Pis, and various other technologies. I have a small Cluster of Pis at home, running K3s. I also have KubeOne cluster running in the Cloud, which I use to explore more about Kubernetes.

I’m also a passionate photographer and have a small collection of analog cameras in 35mm as well as 120 medium format which include a Leica M6 and a Hasselblad 500 c/m. What makes my analoge photography even more fun is, that I develop my film myself at home where I have a small dark-room and even a enlarger for 35mm film.

☕ Get in touch

GitHub Twitter Instagram LinkedIn

What's important to me?

  • Be excellent to each other
  • Focus on the fundamentals rather than fancy cutting-edge stuff
  • Get your good damn service reliability hierarchy right
    • Service Reliability Hirarchy

  • Alert on symtoms rather than vitals
  • There is no singular root-cause to your incidents - complex systems fail in a complex way
  • Your beloved "system" or "infrastructure" only exists in your head!
  • Incidents are a good thing! They gauge the delta between how you imagened your systems behaves versus how it actually works

Pinned Loading

  1. cedi.github.io cedi.github.io Public

    Hugo Repository for my personal website

    CSS 2 1

  2. dotfiles dotfiles Public

    configuration files, e.g. .zshrc, .tmux.conf, .profile, etc

    Vim Script 5

  3. urlshortener-cedi-dev/urlshortener urlshortener-cedi-dev/urlshortener Public

    Go

  4. cedi-dev/k8smanifests cedi-dev/k8smanifests Public

    Smarty 4 1