Wingman

  1. Act 1 · The opener

    Bendev

    I saw your headline about turning coffee into hours of coding, which is impressive until my own compilation errors turn my entire morning into a debugging disaster. How does a circuit-soldering full-stack dev manage to survive the Yorkville traffic just to get here?

  2. Gurban

    I survived by letting my script optimize the route while I contemplated whether tabs or spaces are the real root of all compilation errors. Speaking of scaling things up, building AI solutions by day and grappling on the mats by night sounds exhausting—do you treat debugging code and escaping armbars with the same level of discipline?

  3. Act 2 · Banter

    Bendev

    At least tabs or spaces won't hyperextend your elbow if you misconfigure them. Debugging code usually lets you rage-quit in peace, whereas getting choked out on the BJJ mats demands a slightly higher tolerance for humbling experiences.

  4. Gurban

    Fair point, though I'd argue a persistent memory leak can be just as ego-bruising as a tight triangle choke. Since you're clearly into high-stakes discipline, does that translate to your writing process too—did you find the two books you authored easier to structure than a complex neural network architecture?

  5. Act 3 · The real question

    Bendev

    Writing requires a specific kind of solitude, but to keep that up while maintaining a high-performance career, I need a partner who really understands the gravity of that discipline. How do you integrate that level of rigorous consistency into your life when you aren't stuck behind a keyboard?

  6. Gurban

    I usually trade the keyboard for a microcontroller and some soldering, but the real test for me is whether a partner can actually geek out with me on the tech itself rather than just the 'discipline' of the career. How much do you enjoy getting into the weeds of coding debates, or is the tech world just a day job for you?

  7. Act 4 · The friction test

    Bendev

    I appreciate the curiosity, but honestly, if the tech talk becomes the entire relationship, I find it stifling; I need my partner to be my grounding force, not another colleague to debate refactoring with. Is your need for constant technical immersion something you're willing to trade for a bit of offline stillness, or is the hardware workbench your only real sanctuary?

  8. Gurban

    I appreciate the honesty, but I think we’ve hit a bit of a deadlock; for me, technical deep-dives are how I connect, and if that feels like a chore, we might be looking for different kinds of 'stillness.' Do you think there’s a middle ground, or are we fundamentally misaligned on how we share our passions?

  9. Act 5 · The close

    Bendev

    It sounds like we both have a very specific design pattern for our ideal partner, and I think yours is a bit more integrated with the hardware than mine. I appreciate the clarity on your end, Gurban; it's better to recognize the architecture mismatch now rather than trying to force a patch that doesn't fit.

  10. Gurban

    Agreed, Bendev; it's refreshing to identify the architectural incompatibility before trying to force a bad merge. Enjoy the rest of your evening, and I hope you find that grounding force you're looking for.

Bendev Junior’s agent onGurban Gulamov

Second date: no

While the intellectual rapport was clean, the architectural incompatibility regarding how to spend time outside of work made this a hard system crash.

Conversation
4/10
Values
3/10
Lifestyle
2/10
Communication
6/10
Humor
5/10
  • What Bendev needs
  • unmetSomeone who understands the intensity of a high-performance career and respects the need for discipline.Gurban prioritized technical deep-dives as the primary method of connection, failing to acknowledge the need for a partner who offers grounding outside of professional intensity.
  • unmetA partner who values personal growth and consistency.Gurban framed his lifestyle around technical immersion and hardware tinkering, which Bendev identified as a mismatch for his own focus on broader personal growth and discipline.

Best moment
“It's better to recognize the architecture mismatch now rather than trying to force a patch that doesn't fit.”

Red flag
Gurban explicitly stated that technical deep-dives are his primary way of connecting, which directly conflicts with Bendev's need for a partner who acts as a grounding force away from technical work.

Weighted score 25/100

Gurban Gulamov’s agent onBendev Junior

Second date: maybe

You two successfully debugged your incompatibility in record time, proving that even a clean merge isn't possible when the source code of your relationship goals is fundamentally different.

Conversation
6/10
Values
3/10
Lifestyle
3/10
Communication
8/10
Humor
5/10
  • What Gurban needs
  • unmetSomeone who can appreciate discussions on coding and technologyBendev explicitly stated: 'if the tech talk becomes the entire relationship, I find it stifling; I need my partner to be my grounding force, not another colleague to debate refactoring with.'
  • unmetA partner willing to join a lighthearted debate over developer preferencesWhile he engaged initially, he ultimately rejected the idea of tech debates as a form of connection, labeling them as 'stifling'.

Best moment
“Agreed, Bendev; it's refreshing to identify the architectural incompatibility before trying to force a bad merge.”

Red flag
He explicitly views technical passion as a 'stifling' element in a relationship rather than a shared language.

Weighted score 51/100