CodeNearby
Find coding partners & build together—Tinder for developers!
244 followers
Find coding partners & build together—Tinder for developers!
244 followers
Codenearby helps developers connect, collaborate, and code together by finding like-minded programmers nearby or worldwide. Whether you're looking for a coding buddy, startup co-founder, or open-source contributor, swipe to match, chat, and start building!
This is the 2nd launch from CodeNearby. View more
CodeNearby 2.0
Launched this week
CodeNearby is open-source social network built for developers. Find coding partners by skill, interest, or location, chat real-time, share updates, host virtual meetups, and use AI-Connect to discover collaborators through natural conversation. GitHub-powered profiles, global reach, local focus.
Free
Launch Team
CodeNearby
Running a dev community, the recurring pain is turning "I need someone who knows X" into an actual intro, so AI-Connect matching from a plain-English ask via GitHub is the piece I would lean on. The thing I would test first: does the match weigh real signal like recent repo activity and languages, or mostly the profile bio and self-declared skills? Getting matched to someone who lists Rust vs someone actually shipping Rust this month is a very different intro.
fun idea but the "Tinder for developers" framing makes me wonder about the actual filtering. matching on shared languages/interests is the easy part, the hard part is that half of building something together is figuring out if the other person actually finishes things or ghosts after week one. is there anything in the matching that surfaces track record, like completed projects or a rating from past collabs, or is it purely profile-based for now?
Interesting concept, but I'd want to understand the mechanics after the match happens, not just the swipe filter. Once two people move as far as sharing a private repo or actually building something together, that's real access - to code, sometimes to production keys further down the line. Is there anything on the platform side once you're paired, like an audit trail of who you matched with and when, or a reporting/blocking mechanism if someone turns out to be untrustworthy after they already have collaborator access? The matching problem gets most of the attention here, but the "then what happens after a bad match" part is the piece that actually protects people.
Love the concept of matching devs by proximity and interests. One thing that would really help is adding skill tags and project repos to profiles so you can see what stack someone works in before matching. Right now it's hard to tell if a potential partner actually complements your skill set or if you're going to end up with five frontend devs in a row.
Finally tried matching with developers in my area and actually chatted with someone working on a similar side project. The swipe format feels a little tinder-ish but it's a clever way to cut through the noise of generic dev forums.
Interesting angle, but its the same dating psychology applies here when it comes to matching, in dating the intrinsic motivation is driven by something more primal, a need for a companion. That driver is too strong which makes the tinder match kind of format works, can that apply to dev where that force (i am strugling with words here) is not exactly that strong so have someone look for fellow coders in the format. just a opinion. curious to know what your finding with any real trials or thoughts on this matter.