Hi, I'm Aravind.
Nice to meet you.
on tools
Vibe coding gets a bad reputation because people confuse the tool with the skill. The skill isn't typing — it's knowing what to build, catching what's wrong, and steering toward something that holds.
on systems
The best engineers think in systems, not components. Components are just the output. What they're designing is how things depend on each other — what breaks when this changes, who else is affected.
on ownership
Expanding beyond code into how a product moves is mostly about absorbing ambiguity so the people around you don't have to. Less glamorous than it sounds. More interesting than most things I've built.
— 01
A platform operating in a high-stakes regulated domain — the kind where a wrong word in a document carries real consequences. Owned the entire frontend: architecture, component systems, workflows. Over time, the work expanded beyond the interface — into understanding how the product moves, what it should prioritise, and why.
"The hardest thing wasn't building the UI. It was learning a domain where precision isn't a preference — it's the product."
— 02
Multiple projects across an enterprise insurance platform — quote flows, coverage calculations, letter generation, pricing integrations. Primarily frontend ownership across a domain that demanded consistency over cleverness. The kind of work where shipping quietly and reliably is the whole job.
"Boring and correct outlasts clever and fragile. Every time."
— 03
A personal publication platform, built from scratch. Anyone can read — only I write. The longer vision is a home for everything I build under one brand. For now, it's where I think out loud.
"Every product needs a home. This is mine."
visit webarv.com ↗— 04
A portfolio template platform — built, shipped, then deliberately stepped back from when the ground shifted. AI changed what people actually needed. Knowing when to stop is the same skill as knowing when to start. Still thinking about where this goes next.
"A product decision is still a decision. Stopping for the right reasons is part of the work."
visit portloom.com ↗Five years across frontend architecture, complex domain work, and increasingly — the space between engineering and product. The thread running through all of it: I think about the system before I think about the implementation. What breaks when this changes? What does this look like in six months?
Recently, with how the industry has shifted, I work primarily with AI assistance. When the work required backend delivery in a stack I hadn't touched before, that's how I shipped it anyway. The output is still mine. The judgment is still mine. The responsibility is still mine.
if any of this resonates —
hello@arvnd.in