HN user

mwbiz

855 karma

www.w2lessons.com www.twitter.com/mwbiz

Posts54
Comments25
View on HN
www.w2lessons.com 14y ago

Up and Running With Elastic Beanstalk - Part 1

mwbiz
1pts0
finance.yahoo.com 14y ago

3 Ways Facebook Plans to Exploit Users

mwbiz
1pts5
www.theglobeandmail.com 14y ago

Five challenges for Facebook: Zuckerberg could be one

mwbiz
2pts0
www.w2lessons.com 14y ago

Your Users Won't Read

mwbiz
101pts23
www.w2lessons.com 14y ago

Fast Zipping in Amazon S3

mwbiz
2pts0
www.w2lessons.com 14y ago

Be Consistent

mwbiz
1pts0
www.guardian.co.uk 14y ago

RIM rejects Amazon's takeover offer

mwbiz
2pts1
www.fastcompany.com 14y ago

To Create Something Exceptional, Do Sweat The Small Stuff

mwbiz
7pts0
www.businessweek.com 14y ago

Facebook Said to Be Planning $10 Billion IPO

mwbiz
1pts0
www.businessweek.com 14y ago

Microsoft Investing in Yahoo? Microsoft Said to Sign Non-Disclosure Agreement

mwbiz
1pts0
www.w2lessons.com 14y ago

Price Doesn't Always Matter

mwbiz
1pts0
abcnews.go.com 14y ago

Facebook Privacy: Site Confirms It Tracks You After You Leave

mwbiz
1pts0
www.businessweek.com 14y ago

Buffett Says Berkshire Has Bought About $10.7 Billion in IBM

mwbiz
111pts82
www.w2lessons.com 14y ago

Engineers and the Curse of Usability

mwbiz
1pts0
www.w2lessons.com 14y ago

CoffeeScript Means Giving Up on JavaScript

mwbiz
82pts65
www.w2lessons.com 14y ago

AdWords Is Not A Marketing Strategy

mwbiz
2pts0
www.w2lessons.com 14y ago

A Review of the Lean Startup Book

mwbiz
17pts9
www.w2lessons.com 14y ago

What We've Learned From Steve Jobs

mwbiz
1pts0
blogs.hbr.org 14y ago

Netflix's Bold Disruptive Innovation

mwbiz
5pts0
www.w2lessons.com 14y ago

2 Years of Programming in 4 months

mwbiz
2pts0
www.w2lessons.com 14y ago

What We Learned From Steve Jobs

mwbiz
2pts0
www.w2lessons.com 14y ago

These Twitter Numbers Don't Stack Up

mwbiz
2pts0
blogs.wsj.com 14y ago

HTML5 Poses Threat to Flash and the App Store

mwbiz
20pts11
www.w2lessons.com 14y ago

The Bright Side for AirBnB

mwbiz
1pts0
www.w2lessons.com 15y ago

The Joy of Event Centric JavaScript

mwbiz
1pts0
www.w2lessons.com 15y ago

It's Not A Redesign If You Don't Cut Features

mwbiz
21pts10
www.pcmag.com 15y ago

Why Facebook is Losing US Users

mwbiz
48pts38
www.w2lessons.com 15y ago

Apple’s Commoditization of Cloud Storage, Should Dropbox Worry?

mwbiz
3pts0
dojotoolkit.org 15y ago

Creating Your Own Dojo Widgets

mwbiz
1pts0
dearjunior.blogspot.com 15y ago

Scala Thread Actors - Waiting for Godot

mwbiz
1pts0

I have a CS degree and an MBA and overall I feel that the CS degree provides more value. The MBA is helpful for some positions but only combined with my CS background. An MBA or business degree on it's own is not that helpful because the only set of skills you have is business, and nothing really tangible.

If you're writing in JavaScript it's a nice candidate for self memoizing functions. Obviously this is only helpful if you're making numerous requests to the method, a single request still produces a series of recursive calls.

Totally agree. I would also add that the long-term effect of doing more could have been really detrimental here. If they let users share tons of folders this would have made it much more difficult to work with a variety of platforms and devices. If you don't have to put in a feature, don't!

Joel Spolsky: Lunch 15 years ago

Absolutely agree with you. I'm not sure why this post got 200+ points. Enforced Association is perfect description and it's something that every company must be aware of. I try to get our team together once a month to go out for lunch but that's where it stops. Everyone likes each other and they spend time together at lunch when they want to, not when they're forced to.

For me lunch is a time to stop thinking about work and get out of the office.

If people don't like sitting together at lunch, all you do is force them to think about creative things to say rather than letting them rest their mind and come back to work more productive after lunch.

It's another one of those time where I don't agree with Joel.

We had a similar experience with failure every 3 months or so. We had a small portion of our services on Amazon and it was the main reason we moved it back to our own Servers. I really don't know how they can continue to offer a service with a failure rate as high as EBS. Amazon should be ashamed of themselves for having such a glaring gap in their otherwise strong collection of products.

It is an anti-pattern but it's one that every framework takes advantage of. jQuery and Dojo use it heavily and it can be dangerous if you plan on incorporating it in strict mode. I will note strict mode in the article, thanks for pointing it out.

Also, to teach all this stuff I'd have to write a whole book, this is why I've suggested two good ones that will do just that.

Is that Rob Mauceri speaking in the Video? I saw him at a round table at the Web 2.0 Expo last month and Douglas Crockford and Alex Russell tore him a new ass about Ecma Script 5 strict mode. Looks like he got out of the building alive and actually listened. Cool

[dead] 15 years ago

You can always setup a new account and start from zero. It's kinda like going bankrupt, that's the American way.

The calculations are quite tricky given the granularity of data the author is working with. I agree that a marginal cost calulation is a bit more useful as the cost of development staff is not really relevant here as this is an R&D cost. The exception being those employees that work on technologies to sustain the growth of pages and searches and the IT staff to maintain the infrastructure. Without management accounting data the figures will be rough estimates at best.

gibsonf1 I agree that a functional approach is equally powerful as an OO approach. I focused on an OO aproach as this is what I have the most experience with and this is what Dojo is geared towards.

The intent of the post is to entice server side programmers to learn JS and to take a rigoruous approach to writing JS code. Whether it is functional or OO is irrelevant as long as you write great code, so your point is certainly worth mentioning.

Thanks for the feedback

The fact is that you are testing for viability with an MVP. It is not a product but rather an experiment. You are falling into the trap that most people fall into in thinking it is a product when it isn't. The goal is to validate if there is a demand for your solution, not to create "the product". If you create a whole product then you've defeated the purpose of the lean startup. Look at About.me, they had nothing more than a landing page and got thousands of Beta registrations. The fact is that this approach does work. If the value proposition of the product is attractive to your visitor and solves a large problem of theirs. By creating this basic demonstration to test your assumption you are in fact checking if you would be wasting yours and everyone elses time by building it, that is the underlying premise behind the lean startup.

Also, the post does actually suggest a static prototype as one of the options.