783 karma · joined April 12, 2008
Previously: PhD in CS at MIT. Worked at ACN, MSFT, MOT, etc.
Find me at https://twitter.com/VineetSinha
E-mail me at: vineet dot sinha at gmail.com
Build Apps in Android, they are also Java based. Try coding challenges, www.hackermeter.com was just launched and they seem cool. Play with new frameworks - things like Play Framework are interesting. And try taking online courses (like the Scala Udacity course).
It will take you some time to dig yourself out of your situation, but you should be able to do it.
Yes, they did try open standards. However, the reason it failed was not (IMO) because open standards were a bad idea.
The Open Standard initiatives failed at Google because they did not really know how to do UX. They have only recently started to figure it out.
(I would argue that Google+ is significantly better than OpenSocial ever was, and Google needs to improve it even further)
Definitely impressed that they had the discipline to shut it down in 4 months.
My bet/hope is that with more resources from Yahoo, David will pick and influence more parts of Yahoo than just Tumblr.
App.net's value proposition is just not clear. I can't think of a reason to sign up for other that the face that it will be great someday.
Sounds great - once they build a successful marketplace. But until then, the value proposition is not currently compelling. As a user - ad-free is not in itself compelling enough (yes, ad-free with a user base similar to twitter or facebooks is compelling), and as a developer their user base is again too small to matter.
They likely need to figure out which group is more important. If it is users, they likely need to focus on a killer app, or a killer community (perhaps by focusing the group they are targeting). If developers are more important, and they don't have a user base that is large enough to be compelling, perhaps they need to pith a different pricing model to developers (something to the effect of free to build apps and $1/user with these 100 social features).
(I haven't used them)
The other question is, who is going to be paying on the site - event organizers or those getting gigs? (Both is fine, but it is not clear from the site).
As someone who might organize one or two big events a year, I feel like if I pay, I would like to pay per event for help. (I guess I could consider paying throughout the year, but I find it hard to understand a value proposition that would matter in between my events).
Assuming that Google had done these, there should be no reason that Python would not be fast or robust enough.
A great site is listing many hackathons is: http://www.hackathon.io/
But yes, this refactoring is going to cost and there is unfortunately not many people for whom it is a worthwhile expense. If Automattic is able to think about 10 years in the future, it might make sense for them to start investing in such a clean up.
This kinda limits you to Google Docs style apps, as opposed to other crazy ideas I might have. I would also like to have an option to pay so that I can keep our users data private.
Edit: Added clarification.
I think Google's better move would have been cut a few features and 'Plus-ify' Reader - kinda like they have been doing with their other products. They would have evolved an important user base, shown commitment to the RSS standard, and kept a number of important apps using their api's.
Aren't they after all supposed to be championing the open web?
I don't think this is intentional, but it now hard to argue againsT people saying that they intentionally waited till they killed the RSS readers market and then shut down their product.
I will definitely play with it.
(Great idea. I also don't like the tagline.)
I am looking forward to the competition (and innovation) in this space.
For interesting articles during work time I always save them for later. This is usually using Pocket (getPocket.com) but there are other tools. Later I read them when I am in the mood to read the interesting articles. This way, I try to limit wasted time.
For when I want to add a comment, I actually plan to only do it 2-3 times a day, and at most in 15 minute slots each time. This again puts an upper limit on my time on non-work tasks.
Once you do the above, you realize how much time you were wasting on non-essential things. And from there, you can take on other fun projects.
My instinct is that you are getting a decent amount of ad revenue, and that you might be able to get more - but it will likely require a whole bunch of experimentation to figure that part out.
I would instead focus on the other opportunities: driving more users, and generating other forms of revenue.
You likely will be able to 2-4x your users by experimenting with SEO and Social traffic sources. Also, 2M page views means you likely have a lot of users that you can try to get them to interact with the site more - that interaction will likely result in them coming back and getting more users (via) facebook.
With regards to revenue your simplest bet could be with thinking about different affiliate programs - you might want to approach relevant companies even though they might not have an explicit program.
If you have a specific niche of users, then you can likely drive up ad revenues more, but even if not you can try segmenting your users giving them a little more reason to stay and finally targeting them differently for higher ad rates.
The above is a high bar to hit - even if it is free. And if you charge, you have a bigger challenge.
If you are building a framework for the Java community, I think that your answer is to make a large part (that is significantly better than Hibernate) open source. Once you do that, and see the community forming around it, then you should think about monetizing it. Likely by selling support, services, premium connectors, monitoring tools.
While I would be willing to believe that you guys have an amazing product, I am still extremely skeptical in believing that you will be able to build a business around it. So think MVP without investing too much into it. And right now, MVP sounds like: make it open source.
You might want to see how the Vaadin guys make money.
I find it useful to think of three four questions as a good checklist when reviewing code. Naming often helps in only one of the above.
Using it quickly makes me want a couple of features:
- not needing drag n drop for something (like creating a new task or group - be default putting them in the previous group or top level)
- being able to add tasks that are at the intersection of two groups. I imagine this would look something like a venn-diagram.
Finally, I am reluctant to support a startup unless I know how you are planning to survive. Is it going to be advertisement? not yet release feature? large teams? Once you do this, I will be more comfortable telling others.
Edit: I did my math wrong previously. It is 1500 hours/month.