Aryan Jasala

About

Hi, I’m Aryan Jasala. Senior Software Engineer at rtCamp, working remotely out of Delhi.

It is a role that spans engineering, tech lead and engineering management. In practice: the pull request, the review of it, and the postmortem when it was the wrong one.

What I work on

Enterprise WordPress, mostly the parts where a number has to move.

  • Platform migrations. Architected a move off a legacy Django application onto WordPress VIP: data model, MemberPress and Stripe multi-currency billing, launch, and the post-live plan
  • Front-end architecture. Built rtCamp’s reusable front-end foundation as FE lead. Monorepo, component-based rendering, Tailwind and Webpack. It became the org standard
  • Internationalisation. Designed a platform-wide WPML conversion: content pipeline, automated translation workflows, and a custom block parser
  • LMS engineering. Owned a go-live, including the completion and reminder email systems, plus tooling to recover course progress that had gone missing
  • Performance. Core Web Vitals work on high-traffic sites: CSS bundling, font and ad-script tuning, deferred rendering, and a CDN system serving theme assets and images off a dedicated subdomain
  • Developer tooling. A PHPStan CI pipeline and a GitHub to Slack sync action, both adopted across projects

Automattic Certified Advanced Professional WordPress Developer.

The less glamorous half is sprint planning, technical discovery and audits, review gatekeeping, and onboarding new developer batches.

Why this site is quiet

Most of what I ship lives in private and client repos. So does most of the interesting part. 🙃

What lands here is the part I can write about: something broke, here is the root cause, here is the PR. If you got here by pasting an error message into a search box, you are exactly who I am writing for.

What is here

Two things, and they do not overlap much.

The WordPress writing is the reference kind: plugin fundamentals, custom blocks, rewrite rules and transients, internationalisation, PHPUnit from scratch, a local dev setup, and how VIP Go is laid out.

The homelab writing is the other kind, where something broke and the post is the postmortem. The hardware, a two node cluster and its quorum problem, GPU passthrough, VLANs, and split horizon DNS.

Elsewhere