▲Reach out
let's.talk
Most messages get read. A good portion get an actual reply. Two short notes on what tends to land well, and a couple that tend not to.
Channels
- LinkedIn /in/khan-maria- DMs are open. A sentence of context goes a long way.
- GitHub @missusk Issues and PRs reach me faster than email.
- Email [email protected] Subject lines that explain themselves get answered first.
What lands well
- Technical questions on the topics I write about: Rails, Kubernetes, dynamic config, distributed coordination.
- Collaboration on platform / infra work, especially the messy migration-shaped kind.
- Specific design questions where you can name the failure mode you are worried about. Those are the fun threads.
- Pointers to a paper, an RFC, or a Postgres detail I've gotten wrong. Genuinely my favorite kind of email.
- Recruiters with a real role in mind that you actually think fits. Happy to chat. Lead with the role and the team, not the boilerplate.
What tends not to
- "Quick chats" without a question attached. I usually need a thread of context to be useful.
- Asks to amplify a launch or a campaign on LinkedIn. That is not really my lane.
- LeetCode-shaped questions or DSA homework. I write about systems, not interview prep.
- "Saw your profile and wanted to connect" with no follow-on. Happy to connect, but I will not reply to template openers.
Replies come on a slow weekly cadence rather than instant. If something is time-sensitive, mark it that way and it will jump the queue.