Hey everyone!
Week 5 is done, and wow - this was a big one. Chapters 11, 12, and 13 of "For the Love of Go" took me deep into how Go programs actually flow and execute. We're talking statements, conditionals, loops, switches, and a seriously deep dive into functions.
This week felt less like learning new features and more like understanding the fundamentals of how Go thinks. Let me break it down.
Hey everyone!
Week 4 is wrapped up, and honestly, this chapter was a game-changer. Chapter 10 of "For the Love of Go" was all about validation - making sure data can't be wrong in the first place. Instead of just hoping people use your code correctly, you make it impossible to use it incorrectly. Mind = blown.
The core idea? Use Go's type system and pointer methods to create "always valid" fields and structs. Let me show you what I mean.
Hey everyone!
Week 3 is done, and honestly, this week felt like leveling up. Chapters 7, 8, and 9 of "For the Love of Go" took me from basic data structures to understanding how objects work in Go, and my brain is still processing it all.
The big themes this week? Maps for fast lookups, methods for giving data behavior, and pointers for... well, that one's still sinking in. Let me break it down.
Hey everyone!
Week 2 of my Go journey is done, and honestly, this week felt different. Instead of just learning syntax, I started thinking like a product developer. Chapters 5 and 6 of "For the Love of Go" took me from single books to entire bookstore catalogs, and the approach was fascinating.
The biggest shift? Starting with user stories instead of jumping straight into code. Mind = blown.
Hey everyone!
I've started my Go learning journey with "For the Love of Go" by John Arundel, and wow - this book takes a completely different approach than most programming books. Instead of starting with "Hello World", we dive straight into testing!
This week I completed Chapters 1-4, and I'm already hooked. Let me share what I learned and why this approach is brilliant.
Hey everyone!
I've been part of the AWS Community Builders program for a while now, and honestly? It's been a game-changer for how I learn, share, and grow in the cloud space.
With 2026 applications open until January 21, 2026 (midnight PST), I wanted to share why this program is absolutely worth your time - especially if you're already creating content or helping others learn AWS.
Hello everyone!!
Welcome to my blog today where we will explore Kubernetes autoscaling. I have been learning Kubernetes for a while now, and every time I learn something new, more information occurs to me. It feels like I can never stop learning about Kubernetes!
I was thoroughly practicing Kubernetes where I was able to create pods, services, deployments, etc., and I know that I can manually replicate pods by changing the replica count in the deployment file. But what if I want to automate this process based on the load on my application?
I was still in the process of learning when I came across the concept of Kubernetes autoscaling.
In this hands-on tutorial, I'll walk you through deploying a complete WordPress application with MySQL database on Kubernetes, secured with NGINX Ingress and TLS certificates. This is a practical guide that covers everything from storage configuration to SSL/TLS setup using cert-manager.
This deployment demonstrates several key Kubernetes concepts including persistent volumes, secrets management, ingress controllers, and certificate management - making it perfect for anyone looking to understand how real-world applications are deployed on Kubernetes.
Installing Kubernetes 1.31 and create a cluster using kubeadm (with Containerd and Calico CNI), here's for setting up a basic cluster (1 master + N workers):
This guide sets up an Ubuntu EC2 instance as a Kubernetes node using containerd as the container runtime and Calico as the CNI (network plugin). It supports Kubernetes v1.31.
I'm excited to launch this knowledge base where I'll be sharing my notes, insights, and learnings across various technical topics. This site serves as both a personal reference and a way to share knowledge with the broader community.