{
"name": "Punit",
"role": "Software Engineer",
"location": "India",
"stack": {
"languages": ["TypeScript", "JavaScript", "SQL"],
"frontend": ["React", "HTML5", "CSS3"],
"backend": ["Node.js", "REST APIs"],
"database": ["PostgreSQL"],
"tools": ["Git", "GitHub", "VS Code", "Docker"]
},
"focus_areas": [
"production-grade full-stack systems",
"secure payment & webhook integrations",
"role-based access & multi-tenant architecture",
"real-time browser APIs (WebRTC / WebSockets)",
"system design for scale"
],
"currently_learning": ["cloud infra & deployment strategy", "distributed systems"],
"philosophy": "boring technology, exciting outcomes",
"fun_fact": "has strong opinions about tabs vs spaces (spaces, obviously)"
}|
Think in systems Every feature is a node in a larger graph. I trace the blast radius before I write the first line. |
Security is not optional Idempotency keys, signature verification, circuit breakers — resilience is a feature, not an afterthought. |
Ship, then sharpen Working code today beats perfect code next sprint. I iterate in the open and refactor with intent. |
|
Read before you write Every framework, library, and API has an origin story. I read the docs before I fight the stack trace. |
Own the whole stack Frontend state, backend contracts, database schema — I hold the entire picture in my head, not just my layer. |
Debug like a detective No guessing. Reproduce, isolate, hypothesize, verify. The bug always leaves a trail. |
| Layer | Tools |
|---|---|
| Languages |   |
| Frontend |    |
| Backend |  |
| Database |  |
| Tooling |    |
name: punit-dev-loop
on: [new_problem]
jobs:
understand:
steps:
- read: requirements twice
- ask: "what breaks this?"
- sketch: data flow before code flow
build:
steps:
- write: smallest working version
- test: edge cases, not just happy path
- commit: small, atomic, meaningful messages
harden:
steps:
- add: error boundaries & fallbacks
- add: logging that future-me will thank present-me for
- review: "would I approve this PR from a stranger?"
ship:
steps:
- deploy: with a rollback plan
- monitor: don't ship and disappear
- iterate: based on real usage, not assumptions+ [learning] started with the fundamentals — HTML, CSS, JS, the classics
+ [leveling up] moved into React, learned to think in components & state
+ [going deep] picked up TypeScript for type-safety across large codebases
+ [full-stack] added PostgreSQL & Node.js to own the entire request lifecycle
+ [production] shipped features that real users depend on daily
+ [scaling] now studying system design & infra to build for scale
! [ongoing] still reading docs at 1am when something "should just work"
#!/bin/bash
echo "Open to interesting problems, good engineering conversations, and collaboration."
echo "Best way to reach me → GitHub profile / issues / discussions."
exit 0