"It's not a bug, it's an undocumented feature with a high-priority PR waiting to happen."
I'm an Integrated M.Sc. Math & Computing undergrad at BIT Mesra who spends way too much time convincing compilers that my logic is sound and convincing Git that I didn't mean to commit that. When Iβm not knee-deep in algorithms or wrestling with open-source codebases, I'm probably wondering why my production environment is crying while my local machine works fine.
- Languages: C++, Python, JavaScript, TypeScript, SQL
- Frontend: React.js, Next.js, TailwindCSS
- Backend & DB: Node.js, Express, MongoDB, Firebase
- DevOps & Tools: Docker, Git, Linux (WSL), AWS (Amplify, S3, SageMaker)
- Open Source Explorer: Refactoring time-window logic, optimizing real-time stats, and writing unit tests. (Translation: reading other people's code and fixing their edge cases so you don't have to).
- Competitive Programming: Solving DSA problems across LeetCode, Codeforces, and CodeChef because my brain apparently enjoys voluntary psychological torture.
- Building Things: From real-time customer support platforms and event dashboards to automated web scrapers like TrendFind that find trending products before your favorite influencer does.
- OpenClimateFix: Refactored core time-window logic and implemented rigorous unit tests to make climate data pipelines cleaner and more reliable.
- Mixxx DJ Software: Optimized real-time statistics tracking and refactored time-formatting logic using C++ and Qt (keeping the music playing smoothly without memory leaks).
- Other Explorations: Frequently diving into codebase issues, discussions, and contribution workflows for community projects like Accord Project Concerto and stdlib-js
(Where green squares are my only source of serotonin at 3:00 AM)
- π Portfolio Website: anujnayak108.vercel.app (Where I pretend my CSS spacing is intentional)
- πΌ LinkedIn: Connect with me
- Fun Fact: My code has bugs, your code has bugs, therefore my code is mathematically equivalent to industry standards.




