Experience

"It ain't much, but it's honest work"

TL;DR:

• I’ve been working as a freelance and open-source developer & designer for 7+ years.
• I’m comfortable working in any layer of the web or mobile development stack.
• I’m competent, reliable, and adaptable.

I started my development journey as an Android developer with occasional back-end development here and there. After that, I transitioned into Full Stack Web development alongside UI design.

I now consider myself a generalist. I am good at figuring out whatever needs to be done, learning the necessary skills, and getting things done. But I don’t mind diving deep into a specific area if the task requires it.

Currently, I enjoy working in the JavaScript ecosystem, but I’m not tied to any particular framework. For each project, I like to research and pick the best tool for the task. As technologies continuously evolve, I like to keep up with them.

Here’s a non-exhaustive list of tech that I’ve enjoyed shipping to production so far:

Full-Stack Web

• Next.js - The first web framework I learned, and it remains my first consideration for most of my client projects.

  

• Remix - I had a project where I was supposed to migrate a React Router SPA to Next.js, but I ended up choosing Remix because it was the better choice for SPAs (and it still is).

• Astro - I’m having the most delightful time building websites with this framework. It’s so good, in fact, that I’ve migrated most of my websites to Astro, including this one.

Front-end Web

• React - After years of battling imperative MV* architectures on Android, React’s declarative component model was a breath of fresh air. Now I battle with re-render optimization.

• SolidJS - I get the versatility of React’s rendering model that made it popular, but Solid’s Signal feels like the true Reactive model. I now prefer it over React if I don’t require any React-specific features.

  

• Tailwind CSS - CSS is my jam, so I love styling with vanilla CSS. But I always end up using Tailwind CSS because it’s so concise, and it doesn’t block you from writing normal CSS when it’s appropriate.

Back-end Web

• TypeScript - I prefer the JS/TS ecosystem because of the vast serverless hosting options it unlocks. Cloudflare’s free tier itself is more than enough for most of my projects.

• Go - I reach for Go when I need performance-critical API services or for tools that require cross-platform binaries.

• SQL - SQLite is my default choice for a database because it’s just a file. I’ve also used PostgreSQL and MySQL through database providers like PlanetScale and Supabase. I even used Google Sheets as a database, and it was surprisingly a good experience.

• Docker - I usually prefer serverless deployments like Cloudflare and Vercel, but I’ve had my fair share of containerizing apps and deploying them to AWS EC2 and Google Cloud directly.

I’m also into self-hosting, CI/CD, workflow automation, and other DevOps-y things.

Mobile

• Android - I’ve been developing for Android since the Android 5 (Lollipop) days. I’ve made dozens of apps that solved real problems for me and my clients.

  

• React Native - I don’t own a Mac yet, so for now, Expo is my only option for multi-platform development. Having come from native Android development, I initially had reservations, but it’s good enough.

Design

• Figma - I know Figma like the back of my hand because I design and prototype all my UIs, icons, and illustrations in Figma.

  

AI

• LLMs - I’ve been using the OpenAI API since GPT-3.5 dropped — thanks to a chatbot app I was building for a client during that time. Lately, I’m having fun with automating things with n8n and MCP tooling.

I am looking for a full-time remote role in any timezone. If you come across any opportunities, I would appreciate a recommendation.
Here’s my resume.