Hi! My name is Kabir. I'm a teen developer, behavioral science enthusiast, author, and composer, and these are a few projects I’ve been working on (maybe too much!). CHECK OUT SOME OF MY KAZWIRE SIMULATIONS BELOW! :) Here is my LinkedIn: https://www.linkedin.com/in/kabirkutty/
LoopLess is a student-founded productivity startup on a mission to help people break the endless scroll and live with intent. I built an iOS app that blends CBT concepts, mindfulness science, and structured reflection into a focused, modern experience, a personal “focus trainer” that nudges you toward healthier digital routines.
I work on Kazwire’s infrastructure and performance. Most of my time is spent keeping the site fast and stable as traffic grows, setting up monitoring, understanding latency issues, and making backend/deployment changes so updates don’t break things. I also built analytics dashboards so we can see what’s actually happening on the site and make decisions based on usage. It’s been a mix of practical engineering and problem-solving, teaching me a lot about reliability and iteration.
Through Kazwire, I’ve grown more aware about what distinguishes a site that works from a site that keeps working. The work is incredibly fun, but ultimately, it serves to elevate user experience in a subtler way than they may first notice (that’s where the nitty gritty comes in: cache hit ratios, tail latency, noisy alerts, etc.). I enjoy keeping the site working and serving users through principles of behavioral health and just fundamental UX.
Budgets for bundles and responses, compress aggressively (Brotli/gzip), and keep the slow paths isolated.
Containers that build cleanly (multi-stage), consistent env config, and predictable boot behavior.
Index the real access patterns, watch query plans, and avoid “surprise” sequential scans under load.
Rate limiting, validation, and guardrails so a weird traffic spike doesn’t become a system-wide fire.
Staged rollouts, health checks, rollback paths, and changes sized small enough to reason about quickly.
Where’s it slow? Where’s it failing? What changed? If the dashboard can’t answer that, it’s decoration.
| Surface | What I look for | Fast check |
|---|---|---|
| Edge / CDN | hit rate drops, cache stampede, headers drifting | cache-hit%, TTL, swr |
| Backend | timeouts, queueing, tail spikes | p95/p99 by route |
| Database | plan regressions, missing index, lock contention | EXPLAIN, slow queries |
| Deploy / Config | mismatch between environments, drift, secrets changes | diff + rollback test |
| Abuse / Bots | weird patterns, bursty load, scraping loops | rate limit + WAF |
The shape I aim for is straightforward: cache what you can at the edge and keep API boundaries clean, making the slow stuff obvious (and measurable). Quite a disciplined separation of concerns.
If something regresses, I want answers in minutes. That's what determines a smooth user experience. The dashboards I build focus on: route timing (p95/p99), error spikes.
Thresholds that matter. No endless spam. If it pages you, it should be real.
Link spikes to deploy windows so you can bisect quickly and roll back cleanly.
Track the routes users actually hit. The “slowest endpoint” list is always on-screen.
The stuff I find myself obsessing over is basically the “production checklist”: making things measurable and reversible on the rare occasions that traffic behaves badly.
Edge caching + sensible invalidation beats adding more servers nine times out of ten.
Rate limits + sane timeouts prevent one weird pattern from turning into a cascade.
If it fails, write it down. The system improves when you treat failures like data.
Split by route → compare p95/p99 → look for a single hot path causing the tail.
Diff deploy + config → rollback if needed → bisect in smaller steps until it’s undeniable.
Scan slow query list → check plan changes → validate indexes against real access patterns.
Confirm headers (TTL/SWR) → verify hit rate → watch for stampedes under burst.
Rate limit + validation → isolate endpoints → block obvious automation without collateral damage.
Write it down → fix the root → add guardrail → update runbook so it never repeats.
BetLess is a recovery platform built to help people break gambling addiction through reflective habit loops and structured tracking. Ultimately, the goal is clarity (as well as momentum), giving people tools that make it easier to spot their triggers and stay in control of their cravings.
I wrote Amenhotep IV as a five-act Shakespearean tragedy about one of the most controversial pharaohs in Egyptian history. The story imagines Akhenaten’s inner world as he defies tradition and declares a new god, only to descend into isolation.
Read More