Ritik Kumar

[Ritik Kumar @ritik_kumar22]

Log 182 - Next.js & rendering fundamentals.

Explored how Next.js builds on React with file-based routing and server rendering for SEO. Learned static/dynamic routes and Server vs Client Components.

Build with purpose, not just components.

#NextJS #SEO #FullStackDevelopment

[Ritik Kumar @ritik_kumar22]

Log 181 - frontend-backend integration.

Integrated our 4-layer React app with the backend.

Learned Access & Refresh Tokens in practice: deleting the access token triggered Axios interceptors to call the get-accessToken API and obtain a new one.

Learn by building.

#FullStack

[Ritik Kumar @ritik_kumar22]

Log 180 - authentication & token security.

Learned Access & Refresh Tokens, implemented a complete auth system, and explored Axios interceptors for attaching access tokens and handling token refresh automatically.

Secure authentication, smoother API calls.

#BackendDevelopment

[Ritik Kumar @ritik_kumar22]

Log 179 - rendering & CI/CD

Learned EJS, SSR vs CSR, and when to choose EJS or React.

Also implemented a CI/CD pipeline using GitHub Actions, where automated tests run before deployment. If tests fail, deployment is blocked.

Day 179 - From writing code to shipping it reliably.

[Ritik Kumar @ritik_kumar22]

Log 178 - backend reliability.

Learned Redis caching & TTL, rate limiting and layered DDoS defence.

Also explored Jest, API testing with Supertest, and why developers must test their own code-not rely only on QA.

Day 178 - Build, protect, test.

#SoftwareEngineering #Redis

[Ritik Kumar @ritik_kumar22]

Log 177 - deployment on AWS.

Learned end-to-end deployment with EKS, ECR, S3, CloudFront, ACM, DNS & Skaffold.

Configured HTTPS, API routing, and autoscaling.

Debugging deployment and browser-specific auth issues was a key lesson.

Day 177 - Production demands more than code.

[Ritik Kumar @ritik_kumar22]

Log 176 - persistent workspaces.

Learned project ownership, auth middleware, and CRUD APIs.

Explored syncing workspace files to S3 using Chokidar + debouncing to avoid syncing every keystroke.

Day 176 - Compute is temporary. Data persists.

#AWS #AmazonS3 #SoftwareEngineering

[Ritik Kumar @ritik_kumar22]

Log 175 - Redis & message queues

Learned and implemented Redis TTL for expiration-based cleanup of idle Kubernetes resources.

Also explored LavinMQ + Nodemailer for queue-based background notifications.

Day 175 - Learn concepts by implementing them.

#BackendDevelopment #Redis

[Ritik Kumar @ritik_kumar22]

Log 174 - frontend integration.

Integrated frontend components with backend APIs, debugged errors, and got the application working end-to-end.

Then explored Google OAuth, MongoDB Atlas, and Docker + K8s setup for authentication.

Integration makes components work together.

[Ritik Kumar @ritik_kumar22]

Log 173 - learning the value of debugging.

Explored SSE and built an interactive terminal with Node-PTY + https://t.co/t096dZeCmA.

The key lesson: debugging requires tracing errors to their root cause.

Error → Root Cause → Fix → Test

Day 173 - Debugging requires patience.

[Ritik Kumar @ritik_kumar22]

Log 172 - connecting AI with infrastructure.

Containerized an AI service and deployed it with Kubernetes + Skaffold.

Connected an agent to a sandbox so AI-driven changes appear in the app.

Request → Agent → Tools → Sandbox → App

Debugged API, Kubernetes & Skaffold issues.

[Ritik Kumar @ritik_kumar22]

Log 171 - connecting APIs with AI agents.

Built file-operation APIs, then exposed them as tools for an AI agent.

Prompt → Agent → Tools → APIs → Workspace

Also solved a Windows networking issue during testing.

Day 171 - AI becomes useful when it can act.

#AI #LangChain

[Ritik Kumar @ritik_kumar22]

Log 170 - multi-container Kubernetes Pods.

Learned how containers share a Pod and filesystem using emptyDir + initContainers.

Also explored multi-port Services, subdomain routing, and wildcard Ingress.

InitContainer → Volume → Containers → Router → Ingress

#Kubernetes

[Ritik Kumar @ritik_kumar22]

Log 169 - dynamic sandbox orchestration.

Learned how Node.js can use the Kubernetes API to dynamically create Pods & Services.

Also explored RBAC, subdomain-based proxy routing, proxy caching, and WebSocket support.

sandboxId → Proxy → Service → Pod

#Kubernetes #Docker

[Ritik Kumar @ritik_kumar22]

Log 168 - sandbox orchestration

Learned how Kubernetes can provision isolated user environments using Pods, Services & Ingress.

Docker → Kubernetes → Pods → Service → Ingress

Also explored separating temporary compute from storage.

Day 168 - Separate compute from storage.

[Ritik Kumar @ritik_kumar22]

Log 167 - learning to navigate the unknown.

Given an unfamiliar codebase + docs, I implemented sandbox orchestration without step-by-step guidance.

Read, explored, implemented, hit errors, debugged, and iterated until it worked.

Day 167 - Learn to figure things out.

#DevOps

[Ritik Kumar @ritik_kumar22]

Log 166 - learning to solve the unknown.

Learned Skaffold independently from its docs and implemented it with Kubernetes.

It detects code/dependency changes and can rebuild, redeploy or sync based on rules.

The bigger lesson: Read → Experiment → Debug → Implement

#Skaffold

[Ritik Kumar @ritik_kumar22]

Log 165 - Kubernetes autoscaling.

Revised k8s, then deployed an Express API and tested HPA with Metrics Server.

Used hey for load testing and watch to monitor Pods scaling.

Also deployed a second Express server for service-to-service communication.

K8s responds to demand.

[Ritik Kumar @ritik_kumar22]

Log 164 - understanding Kubernetes

Learned how Pods, Deployments, Services & Ingress work together.

Built a Dockerized server and deployed it locally using Kubernetes manifests.

Docker Image → Deployment → Service → Ingress → App

Orchestration makes containers manageable.

[Ritik Kumar @ritik_kumar22]

Log 163 - understanding microservices.

Learned Monolith vs Microservices, when to shift, and synchronous vs asynchronous communication.

Also explored how load balancers route requests to service instances.

Day 163 - Architecture is about choosing the right boundaries.