Most portfolios show the build. Almost none show the debugging.
Cognizant — product detail pages for a customer-facing e-commerce application
Pepperfry framework — Cucumber over a Page Object Model, data-driven from Excel
PredictCare — three models chosen from fifteen-plus evaluated, 95%+ accuracy
IdeaTrack — eight-plus entities supporting a multi-stage approval workflow
A portfolio site is usually a highlight reel: four screenshots, a gradient, a contact form. It shows the finished surface of the work and none of the working. Which is fine, until the person reading it wants to know whether you can actually do the thing, and there is nothing on the page to answer that with.
This site is built the other way round. It is a folder — a desk rather than a gallery wall. Roles, frameworks, products and coursework are filed as cases, each with the paper document on top and the loose notes and links scattered around it. You open a folder, pull out a file, and read the working.
The format suits my work because a lot of it is invisible by design. Half of engineering is quality: the framework that catches a regression before a customer does, the defect traced through logs to a root cause rather than patched at the symptom, the suite wired into a pipeline so it runs whether or not anyone remembers to. None of that photographs well. All of it is the job.
The through-line across three companies is the same instinct in different clothes. At Cognizant it is a Page Object Model framework and 100+ end-to-end cases behind a storefront. At CRIS it was role-based navigation and a modular architecture so the next screen was not a bespoke problem. At QSS it was internal tooling and documentation that cut the team’s workload. Build the thing that stops the problem recurring, not the thing that fixes it once.
The products here follow the same logic. A Java reference that curates 195+ methods because the official docs are complete and therefore slow. A map that persists your notes because a map you cannot return to is a viewer. A card manager you drag because files are objects, not rows. Each one is small, each one is deployed, each one answers a problem I actually had.
The design of this site is a tribute to Mosby’s Files by Tubik Studio — an archive of American Modernist architecture built around the same folder metaphor. The structure is theirs, rebuilt because it solves a real problem: it lets a body of work be browsed the way it was accumulated, in layers, rather than flattened into a grid. Everything inside the folders is mine.
The folder’s open. Start anywhere.