Get in touch
Contact
Subject-line routing for fastest response. Chicago-based, US Central time.
Direct email
shujaatali@ieee.orgSubject-line routing (8-hour reply target)
[PRESS]Journalist quotes, interview requests, expert commentary
[SPEAKING]Keynote, panel, and workshop invitations
[EDITORIAL]Associate Editor / TPC / Guest Editor invitations
[STANDARDS]IETF LAKE, ISA99, or other standards-body collaboration
[RESEARCH]Research collaboration, paper feedback, methodological questions
Other channels
- LinkedIn, linkedin.com/in/s-ali-badami for warm intros and DM
- ORCID, 0009-0003-5262-021X for academic verification
- GitHub, @Ali-Badami for code questions and PRs
- Google Scholar, profile
Mailing address
Available on request for physical correspondence. Email [MAIL] with reason and the address will be provided.
See also
- /ask/, an open-question intake (no subject-line ceremony, prefix
[ASK]) - /newsletter/, the Quantum-IoT Dispatch quarterly
- /press/media-kit/, bios, quote cards, BibTeX in one zip
- /speaking/, keynote topics, fees, availability
- /faq/, 30 Q and A on the work, the process, and the standards
- Name and spelling, canonical form of the name with all variants
What I respond to fastest
- Subject lines that start with one of the routing tags above
- Specific, scoped questions ("Can you comment on X by Friday?")
- Editorial / TPC invitations with conference link and timeline
- Research questions tied to a paper of mine, referenced by title or DOI
What I'm slow on
- Generic sales pitches and consulting solicitations
- Unrelated AI-strategy / generative-AI generic asks
- Cold-email "let me 15-min your time" without a specific question
- Surveys without compensation or research-purpose disclosure
Security disclosures
For coordinated disclosure of security issues affecting this site or the published research code, see /.well-known/security.txt. Use subject [SECURITY] for fastest routing.