Tech lines suit people who will recognize the reference without a tutorial: developers, sysadmins, the colleague with strong opinions about tabs. On anyone else they sound like a support ticket.
Short ones travel best. A line that fits in a chat message or a commit comment will get read; anything that needs a diagram is better saved for a second date.
Hackathons, meetups, conference after-parties, the office chat and dating apps full of people who list their stack in their bio. Tech lines work best where the shared interest is obvious, so nobody wonders why you are talking about RAM.
Treat them as an icebreaker rather than a pitch. A good one earns a groan and a reply in kind, and if the other person answers with a better pun, you have already found something to talk about. Skip anything about getting into someone's accounts: even as a joke, it reads badly in a message.

