Excited to share with y'all that I am now a CNCF Ambassador!. Looking forward to a new experience!

when dealing with people, let us remember we are not dealing with creatures of logic. we are dealing with creatures of emotion, creatures bristling with prejudices and motivated by pride and vanity.

Tax filing is such a painful process.

I'll be speaking at Chatloopbackoff episode 63 by @CloudNativeFdn in 5 minutes, feel free to join!.

Conversations like these remind me how much there is to learn every day at my workplace - @akuityio . Everyone here brings a unique perspective to the table, and there’s a genuine willingness to share knowledge and help each other grow.

Leave the frontend or database pieces to teammates who specialize in those areas. This approach ensures every part of the PR gets the attention it deserves and that reviews come from those who can provide the most meaningful feedback.

You don’t always have to review the entire PR by yourself, especially in large codebases. Instead, focus on the parts you're most familiar with. For example, if you understand the controller logic well, start there and provide a thorough review.

Reviewing feature PRs is often more challenging than reviewing bug fixes. Feature reviews require a clear understanding of why the feature exists, what it aims to solve, and why the code is written the way it is.

If test cases are failing, that’s usually a strong indicator that something is going wrong and deserves closer attention. When reviewing bug fixes, it’s important to verify that appropriate unit tests are included to confirm the issue is actually resolved and won’t resurface.

Start a code review by ensuring the PR passes all basic checks, even something as simple as linting. These automated checks might seem minor, but they often lead to changes in the code that can affect functionality or structure.

Yesterday, I had a great conversation with my manager about something that every developer deals with: code reviews and especially reviewing long PRs. I got to know some thoughtful suggestions and approaches on how to tackle these, and I believe they are worth sharing here too🧵.

I've recently been building a compression tool to compress your files, and I can clearly see the value of algorithms learnt during university days getting used for building the project end-to-end.

and the streak got broken

Focus on the long-term goal always!.

When working with systems, getting to know the RPO and RTO may not sound like one of the most important things but actually it is.

Love that dopamine strike after fixing a issue or seeing a PR getting merged!.

Go ahead and checkout this!. Finally, it looks like @kverma_ made his mind to release videos after 6 months, now that we are close to another KubeCon in India.

RT @kverma_: Upcoming Argo CD Feature: CLI Plugin Support 🚀. The @argoproj CD team is working on bringing plugin support to the argocd CLI,….

The first step to writing a neat test in Go is to understand when to use assert and require statement.

not bad

can anyone spot me in this picture?.