Aamit.raiBack
Stack

Tools I actually use, and how often.

A working inventory — what I reach for daily, what I keep sharp weekly, and what I pull off the shelf when a project asks for it. Everything here is from work I've shipped or maintain right now.

Daily driver
Weekly use
Occasional
Category

Languages

5 tools

  • TypeScript

    Daily driver

    Default for everything new — strict mode, narrow types, generics where they pay off.

    Used atKatanaPIMPowerkickTuktu.ca

  • JavaScript

    Daily driver

    Long-lived dialect — comfortable across ES5 quirks to modern ESM.

  • Go

    Weekly use

    Backend services, CLIs, and small concurrent tools. Lean on the stdlib.

    Used atTuktu.ca

  • C#

    Weekly use

    .NET Core services and migration work — async/await, LINQ, EF Core.

    Used atKatanaPIM

  • Java

    Occasional

    Used for academic and earlier work — Spring basics, Maven builds.

Category

Frontend

5 tools

  • React

    Daily driver

    Hooks, suspense, server components. Jotai or Zustand for state, React Query for server state.

    Used atKatanaPIMTuktu.ca

  • Next.js

    Daily driver

    App Router, server actions, edge proxies. Shipping this site on Next.js 16 + Turbopack.

  • Vue 3

    Weekly use

    Composition API, Pinia, Nuxt — used for Powerkick's customer-facing app.

    Used atPowerkick

  • React Native

    Occasional

    Cross-platform mobile shells — Expo, Reanimated, native modules when needed.

  • Tailwind CSS

    Daily driver

    v4 with CSS-variable tokens. Pair with shadcn for primitives.

Category

Backend

4 tools

  • Node.js

    Daily driver

    Express, Fastify, BullMQ. Comfortable in event-loop debugging and worker threads.

  • GraphQL

    Weekly use

    Apollo and urql on the client; codegen for end-to-end type safety.

    Used atPowerkick

  • .NET Core

    Weekly use

    Web APIs, background services, EF Core migrations. Containerized for Linux.

    Used atKatanaPIM

  • gRPC

    Occasional

    Service-to-service contracts with protobuf — used in Tuktu's microservices.

    Used atTuktu.ca
Category

Database

4 tools

  • PostgreSQL

    Daily driver

    Schema design, indexing, query plans. Comfortable with JSONB and CTEs.

  • MS SQL

    Weekly use

    KatanaPIM's primary store — millions of product records, tuned indexes and views.

    Used atKatanaPIM

  • MongoDB

    Weekly use

    Document modeling, aggregations, and Atlas — used where schema flexibility wins.

  • Redis

    Weekly use

    Caching, rate limits, BullMQ queues, pub/sub for realtime.

Category

Cloud & DevOps

7 tools

  • Docker

    Daily driver

    Multi-stage builds, slim images, compose for local stacks. Every service behind amitrai.fyi, overflowlabs.org, and raicomputer.com ships as a Docker image.

    Used atKatanaPIMPowerkickTuktu.ca

  • Kubernetes

    Daily driver

    Self-managed cluster running my full personal infra — amitrai.fyi, overflowlabs.org, raicomputer.com — with Helm charts, ingress, HPAs, and zero-downtime rollouts.

    Used atTuktu.ca

  • ArgoCD

    Daily driver

    GitOps controller for the same cluster. Every site (amitrai.fyi, overflowlabs.org, raicomputer.com) auto-syncs from a GitHub repo — push to main, ArgoCD reconciles.

  • GitOps

    Daily driver

    Git is the single source of truth for infra and app manifests. Pull-request review on every cluster change, no kubectl-from-laptop deploys.

  • GitLab CI

    Daily driver

    Pipelines for build, test, scan, deploy. Reusable templates and cache strategy.

    Used atKatanaPIM

  • Azure

    Weekly use

    App Services, Container Registry, Key Vault — where KatanaPIM lives.

    Used atKatanaPIM

  • AWS

    Occasional

    ECS, S3, CloudFront, Lambda — used for side projects and earlier work.