Flight dataPortfolio analytics

The portfolio, measured

Every number on this page is counted from the site's own content at build time. Counts of work — not claims about its effect.

01 / Inventory

What there is

10
Missions · 3 active · 7 shipped
21
Studio pieces · freelance, Smaak.ux
6
Case studies · products I do not work on
4
Experiments · the bench
17
Essays · 10 written here
7
Roles · on the log

02 / Built with

What shipped, and on what

13 technologies carried a shipped mission; 46 are named on the capabilities list. The difference is the honest gap between what I have used in production and what I can reach for.

TypeScript
9 of 10
React
7 of 10
Mappls SDK
4 of 10
Ionic
3 of 10
RxJS
3 of 10
Angular
2 of 10
REST APIs
2 of 10
Amazon S3
1 of 10
Geospatial data
1 of 10
Node.js
1 of 10
Odoo
1 of 10
Razorpay
1 of 10
Spring Boot
1 of 10

03 / Ownership

What I actually held

Matched against each mission’s own role line — the same test behind the ownership matrix. Nothing is claimed here that a report does not say.

Frontend90% of missions
9 of 10
UI / UX60% of missions
6 of 10
PRD20% of missions
2 of 10
Cross-team60% of missions
6 of 10

04 / Evidence

How much of it can be checked

12 measured numbers are on file across all the work — the largest being 600K+ (follower brand shipped, Lean Multiverse · Smaak.ux). What follows is what is not measured, which is the part most portfolios leave out.

Measureda number on file
6 of 10
Named, not yet measuredwhat will be measured is written down
4 of 10
Openablelive links or store listings
2 of 10
  1. Technician AppNamed, not measuredActive
  2. Mappls Shop Admin & Automated BillingMeasuredActive
  3. IOCL GeoRTD PipelineMeasuredActive
  4. Vahan ShaktiMeasuredShipped
  5. IntouchMeasuredShippedOpenable
  6. Locate — Manufacturer BackendMeasuredShipped
  7. Control TowerNamed, not measuredShipped
  8. Indane Yatra MitraMeasuredShippedOpenable
  9. FASTag PlatformNamed, not measuredShipped
  10. HermesNamed, not measuredShipped

An active mission has no outcome yet, so none is written — what will be measured is named on its report instead. A shipped mission with no public metric says so rather than borrowing one.

05 / Written down

The other half of the work

140 report sections across 10 missions, plus the teardowns and the essays. Word counts — a PRD habit, visible.

Mission reports10 reports · 14 sections each
3,212 words
Case studies6 teardowns
3,272 words
Essays10 published here
9,487 words

06 / The record

How complete the file is

Missions with a written reportall of them
10
Missions with a cover of the real thing
6
Missions with ownership declared
5
Decisions with evidence attachedflight rules
7
Certifications on file
8

Built from src/content/ at compile time. If a mission gains a measured result, this page changes on the next deploy — nobody edits a number here, because there is no number here to edit.

The missions behind the dataRésumé (PDF)
Next · Flight rulesHow the calls were madeSeven decisions, each with the fact it came from — the judgement behind the numbers above.