jeads

There is something of a resemblance, certainly. Nothing like a little healthy competition.

Apparently great minds think alike.

http://datalba.com/

https://news.ycombinator.com/item?id=11484635

Google is very unfocused. I've heard very a capable serial entrepreneur say "Google competes with everyone.” I understand his consternation. But I certainly don’t feel like Google has solved this problem for me when I’m fumbling around in Android Gallery.

I am very familiar with that process myself. :)

While a cached intermediate for offline use is a very real possibility, providing top quality service without use of our server system would not be feasible with the current device market. Server-side we can use hardware that is optimized for this kind of processing, without being constrained by device or browser limitations. Without that the service quality would degrade sufficiently to tarnish our product’s image and turn people away.

One example of this is the one you provided: the quantity of training required for accurate answers. If we need to keep this metric tight, relying on random ARM processors and sandboxed single-threaded javascript is not the way.

Datalba’s CEO is in the process of collecting early test users, and has been receiving large quantities of test media for use with the prototype from several of them.

Yes, there are many opportunities in the enterprise market for this. The immediate interest is in bringing a quality service to the world that many people will benefit from. The needs of enterprise customers are largely a subset of that goal, and the parts that aren’t can be handled in a given contract or agreement.

We have been working with and building on the latest in deep learning research, and have become quite proficient with designing and building these technologies.

While we will undoubtably be exploring payed options, I fully expect that to make this product a real success that there needs to be as few barriers to access as possible for the user. Degrading accuracy based on a paywall, the most seemingly economical choice, would alienate the majority of users before they have a chance become highly engaged.

Additional value-adds such as auxiliary services could be monetized, but so far we have managed to collect a number of expressions from consumers that this leads to a very ‘pushy’ presentation. While more market data is needed, it is clear this is territory that should be tread lightly.

The remaining option that is most clear is to monetize in ways that don’t directly make demands of our customers. It would be possible to produce very sophisticated market data from the information our service will collect, something that our partners are likely to find very valuable.

Customers who are not using our cloud storage service for storing content and who are concerned about security and privacy may have the option to have only metadata stored on our system. Once the images and other content have been processed the needed metadata has been largely collected, and can index remote storage. The media does need to be stored somewhere accessible to be searchable.

A browser extension is planned, but only as one of several clients including a phone app and a website.

Your diving headlong into an incredibly sticky issue. This is one of the core fears the public has been chewing on a long time... that the sharing of medical information would become so streamlined that nearly minimal effort would be required to profile an individual.

Great job! Weaving through the math, diagrams and code like this is a great setup.

You might consider adding a little more force and excitement into the writing, to keep people engaged. Maybe a joke. You'll catch a wider audience that way.

"There are a number of things to note about a... " <- This paragraph needs to be rewritten for clarity. The text is disjointed and redundant. The diagram above it should probably be made with a larger, clearer font and rearranged a little.

Make some showy data visualizations with R or MatPlotLib. Publish them somewhere with a link you can share. Even better if you can handle a little webdev, make something like one of these and really knock their socks off: http://d3js.org/. Have a resume website or fleshed out LinkedIn account that you can share.

Sign up on Kaggle (https://www.kaggle.com/) and start participating in contests. Use this to refine your technique. If you do well in the contests, it will be noticed. Be awesome, tactfully, but publicly. Join their data science jobs mailing list and aggressively pursue leads. Make friends and participate in the community and forums.

You should also be attending events like ODSC (http://odsc.com/). Talk to data science people in your area, make connections.

Get very, very friendly with the features in NumPy. Keep your skills sharp and continue to build them.

You should get paid for what you do. Take charge of your fate.

Github.com is a great place for this. When you use an open source project from here, go ahead and contribute any issues you find, or comment on them if others have had them. Read a little of the code every once in a while and when you see something you can improve, make it happen.

But if you want to do a lot quickly, you need to find a project in active development. If possible, get in contact with the developers and find out how they are coordinating and planning. Are they using email? Slack? irc? Hangouts? Meetings? Join in if you can!

Once you've decided to get involved, read the code and really understand it. Make sure you are meeting the standards and conventions the others are using, and that your additions are compatible with the rest of the system.

If your not familiar with git, you need to be: http://think-like-a-git.net

If you get a good idea, make something simple and open source it. Put it up on Github and maintain it, to show that you are capable and interested in contributing. This might help you with teams that are a little skittish.

And if for some reason you can't find a good project to join, then get a friend or two together and make one. You want to make something that is useful to people, and actually gets people interested.

Some items to you might want to pay attention to when getting your project off the ground are mentioned in the ChangeLog article they are discussing here: https://news.ycombinator.com/item?id=2162078