/**

JavaScript is where I started, and understanding it deeply — the event loop, closures, prototype chain — is what makes me effective with everything built on top of it.

TypeScript is my daily driver now, but knowing what happens under the hood matters. How the event loop schedules microtasks, how closures actually capture scope, how module resolution differs between ESM and CJS — that's the knowledge I lean on when debugging gets serious.

I've worked with JavaScript across Node.js servers (Hono on Bun, NestJS), browser environments (DOM APIs, Canvas, Web APIs), and React Native mobile runtimes. For Hurivuri I chose Bun as the runtime and genuinely appreciated the speed difference over Node.js for startup and certain workloads.

Some of the most interesting work I've done at the JavaScript layer lives in BullMQ job processors — payment webhook handlers, courier API callbacks, email delivery queues, and search index synchronization running as background services.

Every TypeScript project I write is still JavaScript under the hood, and knowing that layer well is what separates confident debugging from guesswork.

*/