2015
futureme: initialize objective function
root promptpersonal operating system / build 2026.09
one life.
many branches.
A nerdy little archive of the timelines that happened, the ones that almost happened, and the suspicious recruiter emails that keep trying to fork the repository.
multiverse controls
bad ideas, but with buttons
roulette idle. Pick a button. Disturb the timeline.
2015root prompt committed
2018CMU branch merged
2020Twitter checkout
2026main still compiling
branch topology
an extremely serious visualization of causality
git log --oneline --life
selected commits from the canonical timeline
2016
grad-school attempt #1 → rejection / retry
failed build ≠ abandoned project2018
2019 → 2020
2021
Tesla / Cruise probes ignored
branch declined2023
2024
Microsoft node respawns
rebase detected2025
2026
main: stable, suspiciously quiet
watch branch generatorruntime diagnostics
highly scientific, absolutely not made up
entropy meter
equilibrium68%plot development
Current timeline is stable enough to feel suspicious. Do not confuse peace with a missing feature.
branch generator
NEW_BRANCH_AVAILABLE
recruiter_ping()
recruiter_ping()
WARNING
user reports boredom
user reports boredom
INFO
main remains protected
main remains protected
the Gmail Branching Hypothesis 👽
the emails are real; the interpretation is gloriously unserious
Working theory: my inbox is not documenting the timeline. It is testing branches.
Whenever life approaches equilibrium, Gmail seems to produce a portal: university decision, recruiter ping, offer letter, immigration form, relocation thread, or bureaucratic side quest. The hypothesis therefore proposes that Gmail is a Monte Carlo simulator for career and geography.
- 2015: FutureMe accidentally supplies the system prompt: fly high, dream big, regain control.
- 2016–2018: rejection → retry → CMU. The simulator learns the agent reopens failed paths.
- 2021: Tesla and Cruise probes are declined. The simulator learns Nishad does not always maximize novelty.
- 2023: multiple career and geography branches collide. Difficulty is increased.
- 2024: Microsoft respawns. Apparently some nodes persist in cache.
- 2026: stability rises; boredom is reported; recruiter density becomes suspicious again.
In this model, replying “Thanks, interested. Happy to chat.” is functionally equivalent to git checkout -b possible-new-life.
Reality check: this is a joke built from my own career history, not a claim that Gmail, recruiters, or the universe are secretly controlling anything. The multiverse is currently unverified by peer review and my sister.
alternate timelines
the paths not taken, rendered with irresponsible confidence
msft-2020 / Redmond brancharchived
You keep the original Microsoft offer. The pandemic arrives almost immediately. Your twenties become less “Twitter inside the news” and more “Azure from the edge of it.” By 2026, you might be the six-year Microsoft veteran wondering what would have happened if you had taken that Twitter offer.
twilio-2023 / communications branchghost
You take the Twilio branch and stay there. Different coworkers, different city rhythms, different technical problems, different random Friday nights. Eventually the divergence becomes so large that this version of you feels like a cousin with shared childhood memories.
dublin-2025 / Europe branchunmerged
You move to Dublin. The first weeks are logistics, grey skies, unfamiliar streets and novelty. A year later you have favorite cafés, rent complaints, a new social graph, and absolutely no idea what Bengaluru-Nishad is doing at 5 AM.
india-2018 / unopened branchlost history
You do not go to CMU. The US chapter never starts the same way. No Pittsburgh path, no identical professional network, no same sequence of later forks. The tree does not end — it simply grows in a direction you can no longer reconstruct.
recruiter mode
the part where the joke accidentally becomes a decent portfolio
software engineer
MS in AI/NLP from Carnegie Mellon University. Experience across large-scale consumer systems, cloud infrastructure and edge/platform engineering. Previously at Twitter; currently at Microsoft in Bengaluru.
distributed systemscloudedgeKubernetesC#backendAI / NLPLLMsagents
career graph
Autodesk internship → Symantec → Carnegie Mellon → Twitter → Microsoft India, with several highly plausible alternate branches left behind along the way.
Recruiter disclaimer: yes, this is intentionally nerdy. No, I do not normally describe career decisions as branch collisions. Probably.
terminal
yes, it actually takes commands now
try
conspiracy or ask a normal question · first AI query downloads a small local model · ↑/↓ history · Ctrl+L clears“You only notice the branch point later.”
Some choices feel enormous in the moment. Others look like a random email, a move, a job, a person you keep talking to, or one ordinary Tuesday where you choose differently.