2,454 karma · joined February 21, 2011
name = "Hans Yadav"
identifier = "hans"
domain = "hansy"
tld = "me"
contact = "#{identifier}@#{domain}.#{tld}"Full disclosure - $500+/month in revenue, but not profit. The majority (95%) goes to the creators I work with.
My target is smaller teams, where collisions (hopefully) happen less frequently. If you're a bigger org, chances are you also have the resources to just buy everyone their own seat/license to the account instead of relying on the employees to share one account.
Instead, codes are fetched by explicitly using the slash command and only users who are granted access to them can see them. So if a new person joins your team and types `/tfa` into the box, they won't see anything because nobody has given them access to any codes.
Does that make sense?
~200 subscribers
~6% accessed their RSS URL within the last week
<1% authenticated with Pocket
1.) Totally opt-in. Unless this cafe holds a monopoly on the coffee market on this college campus, students can choose to participate.
2.) It seems like the students have some control over what data to share. Hopefully it's not a binary all-or-nothing situation, but if there's a chance students can share whatever they want (and receive tiered cafe services in proportion to whatever they share), that seems kinda interesting.
I'm more than happy to grant companies access to me. But I want something in return. In this case, maybe a chai latte?
Most of your time with your side project will be allocated to customer support and marketing. Others on this thread have correctly pointed out that approaching the project in terms of a business is the appropriate mindset to possess. You'll constantly be tweaking and iterating until you hit product-market fit, then you'll have to go out and sell the product.
It took me about a month to build https://www.onhand.co then double that time to reach enough users to sustain the server costs (still not profitable).
Honestly the best advice I have is similar to the advice startups receive, which is first figure out a pain point others are willing to pay to alleviate, then spend time building your side project/business/passive income.
Are you choosing an available day (i.e. one that isn't grayed out)?
Clarification: are notes attached to individual files, or can you also attach notes to file types or even specific file names? For example, any time I click on a .gitignore I see my note for useful git commands.
Without question this is the single best beginner resource for learning Ruby on Rails I have ever come across. I tried CodeAcademy and a few other similar websites, but just couldn't connect the dots. Michael Hartl does an unbelievable job explaining web concepts in a simple, concise manner.
I can't recommend this resource enough.
http://www.meetup.com/find/events/?allMeetups=true&radius=5&...
http://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/Gra...
After the interview, I started beating myself up over the dumb things I said. But after a few hours, I opened up Photoshop, mocked up a better solution and sent it over to the recruiter (who I then asked to forward my solution to my interviewer).
I progressed to the next round.
I honestly don't know if my revised solution helped or not, but I'm sure it didn't hurt.
I'm not surprised at the $200k offer.
HN discussion: https://news.ycombinator.com/item?id=7519827