"We may provide information to service providers to help us bring you the services we offer. Specifically, we may use third parties to facilitate our business, such as to send email solicitations. In connection with these offerings and business operations, our service providers may have access to your personal information for use in connection with these business activities."
Email solicitations from third parties ? .. makes me real reluctant to sign up.
Yeah second this .. loose the registration to vote. I'd love to vote on some of this but just won't do it if I have to register.
I observed that search doesn't work on option's. So although "which cola drink do you prefer? " has pepsi as an option .. searching for pepsi yields nothing. The reason it's important to have this is often I'm looking for what people feel about some product (pepsi/iphone/ubuntu) etc I don't want to guess what the question is.
Also I don't know what your monetization strategy is .. but I would hate to see something influence the choice of votes. like this http://www.betabooth.com/poll/What-Non-cola-Sugary-Drink-Is-...
If you want to have adverts make it non related to the questions asked.
I often do not live up to it, but this is important:
The good news about Jesus can transform your life. Jesus died for our sins and rose again from the dead. If you become his follower, you will have salvation (moksha).
For a startup looking to attract co-founders I'm don't think this is very judicious. I'm not saying don't be religious just leave out any mention of it on company sites, that's what personal blogs are for.
I know the NASA thing was meant to merely underscore a point but I've seen this comparison so many times that it bugs me and I wish folks would stop using it. The average NASA sw engineer develops a ridiculously low number of lines of code a year (I think I read something like less than 100 ines). A 6000 line patch has 2500 page spec.
The dynamics are vastly different than in any commerical software.
A nice article on the process is here http://www.fastcompany.com/online/06/writestuff.html . Makes a good read.
Great deals(once you get all their coupons and upgrade your own memory) on developement strength machines and it's good to support initiatives that provide alternatives to MS.
I've been using GTD for the past year and its worked out very very well.
It's strange that I've always used this philosophy of "what is the next smallest increment of code that can be written?" for development but never applied this in other areas
In startups its all the more important that you don't let little things slip.
jsjenkins168 wrote:
Theres actually research out there that proves this is true
hmmm.. I found research in this area very lacking. The only scientific study seemed to be from sleep researcher Claudio Stampi and his essentially said "If you absolutely can't keep regular sleeping schedules (like in long sailing races) then polyphasic sleep is a better alternative".
If you have pointers to papers I'd appreciate links sent to the email-id in my profile. I might try this again someday.
I've done the polyphasic sleep thing for ~3 months last year. You can forget about coding for the first 10-12 days or so while you acclimatize (or at least I found it very very hard). And if you don't initiate yourself exactly right you'll find you've wasted a whole month just getting dog tired.
While you do suddenly seem to get a lot of time it makes any kind of socializing hard since you have to sleep every 3-4 hours. Even after a couple of months if I missed one sleep session I would hit a massive wall and all coding would come to a stop.
Lack of time can sometimes be a good thing. It forces you into creative solutions. The funny thing is, although I produced more lines of code during the polyphasic experiment
I think the quality suffered (not much but when I look over those pieces it always seems I could have structured it better). I don't know what to attribute that to since I didn't feel any different while coding in or out of the polyphasic state after the ramp up period.
Oh and to add .. perhaps this is the wrong crowd for market research.
I usually go down to the local starbucks (I've even sat outside a large grocery store) to ask my market research questions. It's funny the perspective you gather from non tech folks.
Are your interests in social bookmarking (a la delicious/clipmarks..) or social annotation (diigo/fleck/stickis/trailfire ...) ?
The scene is pretty crowded and traction will be very difficult unless you have significant differentiator.
Based on my prior experience getting friends/family to use a social bookmarking service , most folks don't use any because organizing bookmarks never gets elevated to problem from a mere inconvenience.
They have to shown thats it's really really easy before they become converts. Your trick is going to be how to reach this audience.
I'm a web novice too so take my advice as such ..
My requirements are similar to yours, backend ANN's and frontend graph visualization.
I'd go with whatever you currently feel most comfortable with. Getting the first version out there in the fastest way possible will give you a chance to judge feasibility and traction.
The minor differences between current popular languages and frameworks will the least of the problems in getting the app up and running (and honestly inspite of all the wars they don't matter all that much)
When I started programming I would go with the simplest solution I could because I was ignorant of any other way . Now I go with the simplest solution I can because I know the other ways
If I hadn't gone the other ways I would never have learnt to appreciate the simple solutions. I just wish it was a faster proces ;-)
For eg my preference would have been "pay pal" , "amazon fps" and finally "credit card".