$ whoami
I build #SHIT, that somehow works.
- I write clean code. Then the requirements change.
- Frontend bugs. Backend bugs. All lovingly handcrafted.
- Most “simple changes” are three Jira tickets in a trench coat.
- Temporary fixes are permanent fixes with commitment issues.
- I avoid Friday deploys because weekends deserve boundaries.
- Documentation is like cardio. Everyone agrees it is important.
- “Works on my machine” remains a powerful legal defense.
- Based in Dhaka. Available in every inconvenient timezone.
- I debug with music because silence makes the bugs louder.
- Some meetings are about the code I would rather be writing.
- Technical debt is just a future sprint asking for revenge.
- My old code taught me humility. Your old code teaches me patience.
I'm Rathik. CTO at CODECONY. The title says strategy and leadership; my browser history still says “why is this VM suddenly out of disk space?” I lead the team, design the systems, and write code when PowerPoint fails to compile. This happens more often than you would think.
Not Playing
Spotify
# probably trapped in a meeting
$ cat focus.md
Making Things Work
Laravel, Next.js, Node, and whatever else keeps the nice mockup from becoming an expensive JPEG.
Preventing Future Regret
Leading engineering and still shipping code at CODECONY: making technical decisions that survive changing requirements, production traffic, and my own questionable shortcuts from six months ago.
Keeping Fires Small
CI/CD, Docker, Linux, security, and backups. “It worked locally” is not an incident response plan.
$ ls stack/
Credit where it is due. OpenAI and Claude helped me build this. I supplied the prompts and accepted responsibility for whatever passed review.
$ git log
$ ping rathik.dev
Got an idea that sounds slightly unhinged?
Perfect. The normal ideas are already being ruined by committees. Let’s build yours.
hello@rathik.dev→