- This topic is empty.
-
AuthorPosts
-
May 13, 2014 at 6:46 pm #170110
nixnerd
ParticipantSo, I’m still coding an app that I originally had the concept for like 2 years ago. However… I’d maybe like a co-founder or two. Probably just one though because I think one more person would make all the difference.
Primarily, I’d be looking for someone who is more of a databasing expert. But… I don’t even really know where to look. Should I just go to meetups? What’s the standard protocol for this. It’s been a few years since I was in college so it’s not like I can just find some classmate.
I just want to find someone good. I don’t want someone just for the sake of having a helper. For that, I’ll just finish it myself, even if it takes another year.
May 13, 2014 at 9:20 pm #170122__
Participantweb app? mobile? desktop?
I like databases. : p
May 13, 2014 at 9:36 pm #170123nixnerd
ParticipantWeb. Python.
May 13, 2014 at 10:00 pm #170124__
Participanthmmm… an excuse to learn python more better… what DB? could I ask you about the app itself?
To answer your actual question, I don’t really know. Meetups could be good. I’ve met some cool people at meetups, but I’ve never actually been looking for someone. I suspect anyplace isn’t “that great” if finding someone is the main reason you’re going there. It’s probably more like dating than a want ad or job interview.
May 13, 2014 at 10:24 pm #170125nixnerd
ParticipantProbably MySQL, maybe NoSQL. Depends on what would scale better with my data design… and that I’m afraid is beyond my expertise.
The points of data are quite simple. There are two classes of users. Class A has a username, a password, and belongs to several categories (obviously they have user settings unique to them). Class B has a username, a password, a physical address, possibly a physical location and credit card information (obviously they have user settings unique to them).
That’s pretty much it. Then, information is sent between users of Class A and users of Class B. Obviously there will need to be a login system and a secure layer for financial transactions. But beyond that it’s a pretty simple web app.
The problem is… choosing co-founders is probably the single most important step in any startup. It’s not the product or technology to create the product. It’s the team you assemble. Back in my sales days… I was on teams that were phenomenal and our product was shit. But we sold a ton of it because of how great the team was. There was knowledge and support and enthusiasm. Those things are more important than which database to use. But how do you find those people with the technical know how that are a good fit?
I suppose it is a bit like dating. I’m asking an impossible question akin to “How do I find the perfect wife?”
May 13, 2014 at 10:27 pm #170126nixnerd
Participant*Sidenote: I understand it’s ridiculous at this stage to even entertain the idea of using NoSQL. Be that as it may, I do see the realistic possibility for tons of people to use this. Like, way beyond the threshold needed to go non-relational. But again… something I don’t know very much about.
May 14, 2014 at 12:27 am #170140__
ParticipantI’m asking an impossible question akin to “How do I find the perfect wife?”
Well, at least the internet has an answer for that one.
The problem is… choosing co-founders is probably the single most important step in any startup
Absolutely. You’re kinda stuck with them. And betting the farm.
I understand it’s ridiculous at this stage to even entertain the idea of using NoSQL. Be that as it may, I do see the realistic possibility for tons of people to use this.
I have not seen the “NoSQL” light. The main selling points everyone hits me with are “you don’t have to use SQL!” and “you don’t have to define any schemas!” …both of which strike me as weaknesses, not strengths. It seems like a bad trade, aimed at people who are frustrated because they don’t understand how to use a RDBMS in the first place. The potential for a disorganized mess seems too high, and I hear conflicting things about how well they can scale.
Undoubtedly, they’ll work out for some applications. But for apps* that have well-defined objects, that interact in particular ways, I think a relational DB will always be the correct solution.
* like yours, it seems. but maybe I’m wrong.
May 14, 2014 at 12:35 am #170141__
ParticipantThe points of data are quite simple …
You’ve caught my interest, btw. I want to know what this actually does! :)
May 14, 2014 at 5:23 am #170171nixnerd
ParticipantI’ll email with a few more thoughts.
May 14, 2014 at 11:31 am #170199__
ParticipantCool, got it. I like it.
-
AuthorPosts
- The forum ‘Other’ is closed to new topics and replies.