8000 GitHub - iamkanishka/iamkanishka: My Github Profile · GitHub
[go: up one dir, main page]

Skip to content

About

My Github Profile

Resources

Stars

0 stars

Watchers

1 watching

Forks

Latest commit

 

History

62 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

Kanishka Naik

Software Engineer & Open-Source Maintainer
JS/TS · Elixir · Go · Solidity
Exploring payments, ledgers, and distributed systems
Astrophile · Tech Blogger

Kanishka Naik


About

I'm a Full Stack Engineer with 6+ years of experience building production-grade systems designed to scale. My work sits at the intersection of backend performance, distributed architecture, and cloud-native infrastructure — with a growing focus on payments, financial ledgers, and blockchain systems.

I care deeply about writing software that is not only functional, but maintainable, observable, and resilient under pressure.

Beyond engineering, I contribute to open-source, write about distributed systems and infrastructure on my blog, and spend my nights thinking about the universe.


What I Work With

Languages TypeScript · JavaScript · Elixir · Go · Solidity

Backend Node.js · NestJS · Express · Phoenix (Elixir)

Frontend Angular · NgRx · NGXS · Sass · Material UI

Databases & Caching PostgreSQL · MySQL · MongoDB · Redis · Firebase

Infrastructure & DevOps Docker · Kubernetes · Kafka · AWS · GitHub Actions · CircleCI

Architecture Patterns Microservices · Event-Driven Systems · Domain-Driven Design · Clean Architecture · Nx Monorepos


Focus Areas

  • Payments & Ledgers — Designing reliable, audit-ready financial systems with strong consistency guarantees
  • Distributed Systems — Architecting services that scale horizontally and degrade gracefully under load
  • Open Source — Maintaining libraries and tooling that improve developer experience across the ecosystem
  • Blockchain & Web3 — Smart contract development in Solidity; exploring decentralised financial primitives
  • Technical Writing — Breaking down complex systems thinking into accessible, practical content

Engineering Principles

  • Design for scale from the start — retrofitting is expensive
  • Build systems that fail gracefully, not catastrophically
  • Observability is not optional in production
  • Good architecture enables fast teams, not just fast software
  • Write code for the engineer who maintains it next

Writing & Open Source

I write about distributed systems, backend architecture, and engineering trade-offs. If you find something useful, a ⭐ on the repo goes a long way.

Always building. Always learning. Always scaling.


About

My Github Profile

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

0