Software Engineer | Engineer focused on systems, scale, and failure.
Backend engineer working on systems that break under load.
I design like failure is expected β because it usually is.
.
βββ βοΈ cloud_infrastructure
β βββ aws # Lambda, EC2, S3, RDS, SNS/SQS
β βββ gcp # Cloud Run, Pub/Sub, BigQuery
β βββ devops # Docker, CI/CD, Load balancers, Observability
β
βββ ποΈ backend_core
β βββ nodejs_ts # Event loops, workers, distributed queues
β βββ microservices # Async flows, idempotency, reliability
β βββ rust # Performance, memory-safety flex
β
βββ ποΈ persistence_layer
β βββ postgresql # Weird queries β clean query plans
β βββ cassandra # Writes fast. Reads... depends π
β βββ mongodb # Schema-less until it isnβt
β βββ arangodb # Graphs when joins get ugly
β βββ redis # Pub/Sub, caching, rate limits, cuz speed fixes feelings.
β
βββ βοΈ web3_&_systems
β βββ solana # Parallel world of transactions
β βββ arduino_c++ # Sensors, signals, and soldering burns
β
βββ π scripting
βββ python # Automation, scripts, data pipelines$ ls -la projects/ --status --brief
PERMS PROJECT STATUS DESCRIPTION
drwxr-xr devutils.lol [ACTIVE] Built because I got tired of slow tools.
Runs on your Resource. If it lags, it's your fault π
drwxr-xr js-std [IN-DEV] JS package
$ readlink -f ./favorites: devutils.lol
[runtime]
state = "active"
process = "Call of Duty"
music = "Hard Techno" # BPM > 145
fuel = "caffeine, anime"
[connect]
linkedin = "https://www.linkedin.com/in/sunanda35"
twitter(X) = "https://x.com/0xSunanda"βSystems fail. Thatβs normal.β
So I design with that in mind β
retries arenβt optional, logs need to tell the truth, and one bad component shouldnβt take everything down.
Reliability>Shiny ToolsPerformance>HypeClarity>Cleverness
Everything else is just trade-offs.
echo "Boot sequence complete. Systems optimal. Deploying next idea..."




