Languages change. Tools change. Fundamentals stay.
I build across the stack frontend, backend, systems, infrastructure because I care less about which framework is trending and more about what's actually happening underneath it. Give me a new language or tool and I'll get comfortable fast; the underlying ideas rarely move.
Not "which framework" but data structures, algorithms, concurrency, memory, networking, system design. Frameworks are a thin layer on top of things that don't really change. I'd rather be fluent in the layer underneath.
| Languages | JavaScript, TypeScript, C, C++, Java, Go |
| Frontend | React, Redux, React Router, Angular, Tailwind CSS, Material UI, Bootstrap, HTML/CSS |
| Backend | Go (Gin), Node.js, Express, Socket.IO, Redis |
| Data | MongoDB, SQL |
| Infra | Linux, Docker, Nginx, Git, GitHub, Postman, VS Code |
| Cloud | AWS (EC2, S3, Amplify), Vercel, Railway |
- Understand the problem before touching the tool
- Prefer boring, well-understood solutions over clever ones
- Read the docs, then read the source when the docs run out
- Ship it, then make it better
Learn something new → build with it → break it on purpose → understand why it broke → repeat.
Reach me: athulkrishna736@gmail.com · LinkedIn · GitHub



