Commit 2c23c50b authored by Chris Kaburu's avatar Chris Kaburu
Browse files

Bio-Readme-Refresh

parent 62029e9d
Loading
Loading
Loading
Loading
+15 −10
Original line number Diff line number Diff line
---
title: "Chris 'CK' README"
description: "Personal readme page for CK, Support Engineer, GitLab"
description: "Personal readme page for CK, Sr. Support Engineer, GitLab"
job: "Support Engineering"
---
## Chris Kaburu's README

Here you'll get a glimpse of who I am and how I work. You wanna chat, got some questions, a brainwave, or just fancy a chinwag, don't hesitate to ping me. Let's share stories!
Welcome! Here's a glimpse into who I am and how I work. If you’d like to chat, have a question, a bright idea, or just fancy a chinwag, dont hesitate to ping me. I’m always happy to share stories and connect.

## A Little About Me 🌆

I am Chris, hailing from Nairobi, Kenya (a city with a National Park in it). Raised amidst Nairobi's dynamic culture and natural beauty, I developed a love for exploration, continuous learning, and the celebration of diversity, which has inspired my adventurous move to the Netherlands. For me, life is about cherishing little joys and infusing them into our daily work and passions.
I’m Chris, originally from Nairobi, Kenya (a city so wild it has a national park in it). Growing up surrounded by Nairobi’s vibrant culture and natural beauty, I developed a deep love for exploration, lifelong learning, and celebrating diversity. These passions eventually led me on an adventurous path to the Netherlands.

To me, life is about appreciating small joys and weaving them into how I live, work, and engage with others.

## My Professional Journey  💼

I embarked on my GitLab journey in September 2022 as a Support Engineer. Over time I realized that support is not only about problem-solving, but also about empathy, effective communication, and going the extra mile to make someone else's day better, traits that have been consistent accross my diverse experiences prior to this.
I embarked on my GitLab journey in September 2022 as a Support Engineer. Over time I realized that support is not only about problem-solving, but also about empathy, effective communication, and going the extra mile to make someone else's day better, traits that have been consistent across my diverse experiences prior to this.

While the allure of working on numerous areas is tempting, I focus on my strengths and rely on the expertise of my colleagues in areas where I'm still learning. My current interests include Kubernetes, Geo, and Performance in distributed systems. I'm dedicated to learning and improving each day, as I explore and discover these technologies and many more!
While I continue to enjoy exploring different technical domains, my experience now spans Kubernetes, failover systems, cluster management, and performance in distributed systems. I focus on deepening this expertise while staying curious and open to learning in adjacent areas. I'm also committed to sharing what I’ve learned, whether through collaboration, documentation, or mentorship, as these technologies evolve.

### My Assumptions 🌱

I was captivated to [GitLab Values](/handbook/values/), and now as part of the team, I've had the pleasure to experience and live by these values. Now, I hold the following assumptions about my colleagues:
What drew me to GitLab was its strong [value system](/handbook/values/), and being here has only reinforced that. I live by these values daily and hold the following assumptions about those I work with:

- You [mean well](/handbook/values/#assume-positive-intent)
- You'll [fulfill your commitments](/handbook/values/#have-ownership--accountability).
- You're [direct](/handbook/values/#directness).

Hold me accountable whenever I fall short of these values. I pledge to do the same for you.
If I ever fall short of these, please hold me accountable, I’ll do the same for you, with respect and openness.

## How I Work ⏰

I adhere to a strict work schedule from 6 am to 3 pm CEST, which is when I'm most productive and responsive. Post 3 pm, my response might be slower, and I generally reserve this time for @mentions on slack. Occasionally, I may adjust my schedule based on specific needs or projects.
I typically work from 6:00 AM to 3:00 PM CEST, which aligns with when Im most productive and responsive. After 3 PM, I check Slack less frequently and primarily respond to direct mentions. My schedule may occasionally shift based on project needs.

## Availability and Communication Preferences 📞

My approach to communication is straightforward: be direct, be respectful, and be open. I believe that clear communication is the key to resolving most problems and achieving effective teamwork. If there's something you'd like to discuss, ask, or need help with, please feel free to reach out. "I'll either assist directly or direct you to someone who can help.
I am always game for a coffee chat! Conversations over a good brew are among my favourite ways to connect here with colleagues, to discuss ideas, or just have a pleasant, casual chat.
I believe in clear, respectful, and direct communication. Most problems can be solved or better understood through open conversation.

If you need support, want to explore an idea, or just have something on your mind, feel free to reach out. I’ll do my best to help directly or connect you with someone who can.

And yes; I'm always up for a coffee chat! Few things beat a good brew and a great conversation, whether we’re exchanging ideas or just catching up casually.