Connect
Every route in, and what each one is actually good for. Email gets read; the rest vary.
- github
GitHub
@VictorBlainSource, commits, and the work in progress.
- substack
Substack
systemsbyvihaanSystems by Vihaan — the build log, written as it happens.
- linkedin
LinkedIn
in/vihaan-vaghelaBackground and history, in the format that expects it.
- devto
DEV
@victorblainLong-form engineering write-ups, posted where engineers read.
- x
X
@Vihaan_VaghelaShort-form thinking, mostly about systems.
- email
Email
vihaanvaghela@gmail.comThe most reliable route. Read daily.
The newsletter
The one channel that does not depend on an algorithm deciding you should see it. Choose what you want; unsubscribe in one click, any time, from the footer of any email.
the conduit
A message sent here is stored before it is mailed, which is the only reason it can hand you a reference afterwards — the number refers to a record, not to an email that may or may not have arrived. Say what you are trying to do rather than what you would like built; the first is the more useful message and usually the shorter one.
Email still works if you prefer it — vihaanvaghela@gmail.com. It reaches the same person and keeps no reference.