Oculus

Where'd you get the wrong idea that it was a Startup?

AngualrJS was a side project of Misko, who was working at Google on the DoubleClick team, until he bet he could rewrite DoubleClick in 1 or 2 (can't remember) weeks using his framework and cut down on the LOC/code complexity. He eventually did and they decided to go full time on the framework. They discussed this at the start of their Google IO presetation.

At first in my mind it's 'Oh, another javascript particle effect' and then I try the demo and it becomes 'holy shit, this is amazing'

Amazing job!

Really awesome read, thanks for the link!

I agree. Just like LanceH said, it's bad form to get caught, but in all honesty, this is the NSA's job. To gather forgien intelligence.

That was very fair response. Kudos for being able to attack the points, not the person.

This could be part of Google's Project Loon. Instead of building a data center in Africa why not ship one over.

Wow this had me laughing quite a bit, I love this community <3

This a million times. To continue the analogy: Only with experience will the driver know approximately how long the drive should take. Read about the traffic all you want, but until you drive there multiple times, try not to give a set arrival time (or prepare to arrive late).

In case the site isn't loading for you (wasn't for me):

http://webcache.googleusercontent.com/search?q=cache:www.mat...

I think the distinction Bluedevil is trying to make is you're going into this SaaS app with no intention of it being hugely profitable or successful. You're scratching an itch and if other people decide to pay you to help scratch their itch as well, then that's just a sweet bonus.

In contrast, a business would be going in with the intention of the service/app being successful (profitable or popular). Maybe hobby isn't the best way to describe it, but I agree your way of looking at things is closer to a hobby then a business.

I think we're getting pretty close to figure it out in the world of node with npm.

I'd be surprised if Google is doing this for anything, but the patents.

Lets disregard the age of the article for one moment. I think that the author is making a good point, developers oversimplify applications and when they begin to work it turns out that it's a hundred times more complicated then initially thought. Very valid.

Great Article, HATE the title. I think it gives the wrong impression. The title should be:

How we tripled our revenue by understanding our users better

Yes by adding a button you tripled your revenue, but what you really did was understand your customers/users better and identified that you could have them spend more by offering a certain deal (which you then implemented by adding a button).

It (title) gives people the impression that they should be A/B testing button locations/colors/<insert (99.99% of the time) random property/> when what they should really be doing is learning more about their users and how to provide the most value for them which in the end gives you more revenue or profits or candy :)

How isn't Apple afraid that Samsung could steal their chip designs? Do they pick Samsung because they simply have no other option?

This has been a long time coming after Box poached one of the top guys on the Google Docs team.

So much new found respect for Russell Brand, that was hilarious.

That's a very biased argument.

Just as people searching for a washer on Google are more likely to click on a washer ad, people looking at the #Astronomer stream are more likely to buy a telescope.

That's not the perfect comparison, but Twitter definitely classifies it's users into ad related categories.

Finally a web framework I can use. All the Java web frameworks I tried to use are way too enterprise-y.

Kind of reminds me of the Windows tablet being way before the iPad, yet the iPad blowing it out of the water. Microsoft had all these great ideas, but failed to execute. It really reinforces the 'ideas without good execution are worthless' motto.

I noticed the 'do things that don't scale' actions like delivering a trophy with cookies to the 10k user or writing personalized emails to every new customer.

Riot should be a case study on how to handle leaks. Immediately releasing all that they know and forcing password resets. Good on them!

What I don't understand is what's the purpose of doing this? From what it seems, Hacker Scouts are merely trying to do good. Why go out and fight that? I'm curious to hear BSA's side of the story and see if they're being shitty people or if there are real reasons to them doing this.

As I mentioned in the reply above, the engineer's response could've been many times better, but you have to agree the bug submitter gave them practically nothing to work with.

I definitely agree with you on this. The response from the engineer could've been better. Some sort of canned response would have worked.

IMHO, the whole ToS business was a way to give him a slap on the wrist for embarrassing them.

My guess is the latter.

I think he prefers it the exact same way. It's just not natural for him (and most people) to say nothing when someone asks him what he's working on. Even if it's just some small hacked together game he's still going to be honest. Most developers love showing off what they're working on no matter what it is because there's usually no downside. Due to his popularity, people go out and start telling everyone that Notch is working on this new super awesome game even though Notch is just fooling around with an idea.

That sales rep. more than deserved it though I'm surprised Groupon's training didn't even prepare him for the hang ups. Shows poorly on both of them.

The problem here is that if FB took every single bug report that they got 100% seriously, they'd never get to the real bug reports, but would just constantly be sifting through the spam. You have to make educated guesses on whether or not a report is just useless spam. This report, the way it read, shoots off a lot of spam flags. I understand why he got dismissed so easily and frankly it is his fault. Nobody has enough staff to hold hands with every single bug submitter regardless of what they send.

Bookmarked. Definitely could've used this post when I was just starting with PostgreSQL!