Message a match who codes side projects without seeming clueless
How to reply when someone mentions building apps or side projects. Show interest without pretending to understand their work.
Someone who spends time coding side projects is signaling that they care about building things, learning constantly, and have a life outside dating. They're likely detail-oriented, goal-driven, and expect you to actually listen instead of just reacting.
Your reply needs to do two things at once: acknowledge what they said specifically, not generic stuff about passion, and open a door for them to actually talk to you about it. They don't need you to code. They need you to ask questions that show you get why it matters to them.
Most people either ignore the coding part entirely or they overcorrect and pretend to understand React when they don't. Both kill the conversation. Find the angle that's actually interesting to you, then ask about that.
Get replies that sound like you
Screenshot the conversation in WingAI. It reads the vibe and gives you natural replies for this exact situation.
Try for freeWhy side projects signal something different than just being busy
Someone building on the side isn't trying to impress you with their resume. They're doing it because they like solving problems or learning something new. That's the actual signal. It means they spend free time on work they chose, not work they were assigned. They probably get frustrated when things don't work, spend way too long on small details, and get excited about obscure wins nobody else notices.
When they mention it to you, they're deciding whether you're someone who gets that. Or someone who'll make fun of it later. Or someone who won't even remember they said it.
Find the human reason behind the code project
The technical stuff is real but it's not your entry point. Your job is to find the actual problem they're solving or the thing they wanted to understand. Someone building a fitness app probably got frustrated with existing apps. Someone building a scheduling tool probably has a workflow that doesn't exist yet. Someone tinkering with game development probably loved a game and wanted to know how it works.
Ask about that reason, not the code. You're not pretending to code. You're asking why this problem matters to them. That's something you can actually talk about.
Send early, then give them real space to respond
Reply within a few hours while the conversation is fresh. They're more likely to respond if they're still thinking about the project or just took a break from working on it. Don't send a super long message asking five questions. One solid question is better. If they don't respond in 48 hours, they're either busy with the project itself, which is fine, or not interested. Don't double message or try to be funny to get their attention back.
If they do reply, match their energy. If they go deep into details, ask a follow-up. If they keep it short, respect that and move toward meeting up instead of continuing the technical conversation over text.
Why these replies fail
“oh that's so cool! i love how you're so driven”
This is empty praise that could apply to anyone. It shows you didn't actually process what they said.
“wait so is that like machine learning? or just python?”
You're pretending to understand tech enough to ask specifics, which will feel forced and get exposed immediately.
“lol sounds like a lot of boring coding hours haha. what do you do for fun?”
Dismissing their project signals you don't respect what they care about and you're not actually interested.
Common mistakes
- Ignoring the coding part and pivoting to something safer, which signals disinterest in what matters to them
- Flattering vaguely ('that's so cool') without showing you actually processed what they said
- Pretending to understand the technical side when you don't, which they'll immediately spot
- Asking 'what does it do' without any follow-up, making it feel like an interview
- Using motivational language ('living your dreams') instead of talking to them like an adult
Questions people ask
- What if I have no idea what they're building?
- That's fine. Don't fake it. Ask why they started building it or what problem it solves. That's a question you can actually ask. You're learning about their thinking, not the code.
- Should I pretend to know about coding if I don't?
- No. It will sound awkward and they'll know immediately. Ask about the motivation or the outcome instead. Focus on what you can actually engage with.
- Is it weird to ask how long they've been working on it?
- Not weird at all. That's a good entry point. It shows you're paying attention and lets them talk about why they stuck with it. Just follow up with something about what keeps them going.
- What if they give a short answer and seem uninterested in talking about it?
- Drop it. They mentioned it but maybe they don't want to talk about it over text. Move the conversation somewhere else and bring it up naturally later, or let it go.
What people say after using WingAI
“I overthink every text. Having three options and picking the one that sounds like me cut that spiral short.”
Sam R.
“I was skeptical at first. Then I tried it on a dry chat and the replies actually sounded like me, not a chatbot.”
Mazoonx
“Used it for a couple hours and set up a date the same night. Not even kidding.”
Nikola2214
Get replies that sound like you
Screenshot the conversation in WingAI. It reads the vibe and gives you natural replies for this exact situation.
Try for free