---
title: "Software engineering"
description: "Application engineering across product sites, client sites, and small tools, with the stack taken from the projects rather than from a wishlist."
canonical: "https://www.ayushrai.site/software-engineering/"
last-updated: "2026-10-16"
---

# Software engineering

Source: https://www.ayushrai.site/software-engineering/
Markdown: https://www.ayushrai.site/software-engineering.md

Application engineering across product sites, client sites, and small tools, with the stack taken from the projects rather than from a wishlist.

Evidence level: Grounded in work I can point to.

## Scope

Software engineering on this site means the application work I can open: interfaces, content models, APIs that read public data, and the occasional extension. It includes how a product is staged so a prototype is not described as infrastructure.

It does not include a distributed-systems portfolio. MedVoice specifies PostgreSQL, a Redis-shaped cache beside it, and idempotent invoice posting. The API still defaults to an in-memory catalog. That is a plan plus a constraint, not a case study in consensus, queues, or multi-region failover. I am not publishing a distributed-systems URL for it.

## Stacks I have actually used

This site is Vite, React, and TypeScript, prerendered to HTML. Flagship products and several MVPs use Next.js. Overlay Text Box is a Chrome extension. Client sites for Iha by Himani and Praful H. are marketing and portfolio sites with public repositories.

MedVoice's recorded architecture is a Next.js admin, a NestJS modular monolith, and an Android worker app that is still a scaffold. I cite that as the product's own stage explanation, not as a completed enterprise rollout.

## How I try to keep the software honest

Stage labels live in one module so a page cannot quietly upgrade itself. Public pages and Markdown twins read the same content records. Withheld award claims are omitted from machine-readable output as well as from the HTML.

For client work, the outcome I will write down is the one in the case study. Iha by Himani is a responsive studio site. An older '300% inquiries' line was unverified and is not used.

## Testing and failure

This repository uses Vitest and Playwright. The interesting failures are content failures: a soft 404 that returns the homepage, a function that does not return a response the host accepts, a canonical URL that disagrees with the redirect. Those are the defects the SEO audit records, and they are ordinary software defects.

## Evidence

- [The Open Framework](/work/the-open-framework): Front-end prototype. Not national infrastructure.
- [Overlay Text Box](/work/overlay-text-box): Chrome extension. Open source.
- [Iha by Himani](/work/iha-by-himani): Client marketing site, 2023.
- [Shiksha-Mitra](/work/shiksha-mitra): Learning platform MVP.
- [This site's repository](https://github.com/ayushrai-hub/ayush-work): The content layer and the prerender pipeline.

## Related

- [Software services](/software-services)
- [Open source](/open-source)
- [Products](/products)
- [LLM systems](/ai-engineering/llm-systems)


## Further reading

- [React docs](https://react.dev/): The UI library this site and several products use.

## Gaps

- No distributed-systems page. Idempotency in MedVoice is not a distributed-systems practice narrative.
- No published performance budget, load test, or multi-region design.
- Backend depth varies by project. I do not collapse Next.js sites and a NestJS monolith into one seniority claim.

Contact: /contact

_Unverified award metrics are omitted. Wording matches the public site._