I was quite impressed with how MongoDB handled everything. They were quick to respond in an intelligent (read: not hot air) manner, admitted that their product still has some shortcomings that they're working on. I wish more companies were as honest.
Also depends on where you live. For example, in Washington an employer cannot claim ownership of something you built in your own time, assuming that you didn't use any of their resources.
Are you going to be doing some intense marketing in small geographic areas? This is the type of app that depends on high participation in a small area - I have a hard time seeing how it will succeed without focusing on a small area first.
The 60 minutes interview gave an anecdote where employees with options were giving some of their own options out to other founding employees without after they went public. When one of the first employees, and a close friend of jobs asked for some options, another founding employee told Jobs that they should help him out, and offered to give out some options if Jobs would match him. Jobs declined, and never gave out any of his options.
While it's certainly his decision to make, I think it's entirely reasonable for people to say he doesn't deserve the worship he's been receiving.
Isaascson had 40 some-odd interviews with Jobs, and none of it was censored by Jobs apparently, so the biography ought to give a good picture of the real jobs.
From the 60 minutes interview with Issaacson, it seems like a fairly honest appraisal of Jobs.
It seems a bit silly to use a video clip created with a 1k slow mo dolly and another 1k in video editing software. For some reason I just don't see the average user using that equipment....
And even with that....it doesn't really look that amazing?
Keep in mind this post was originally from 2007. jQuery started in mid-2006. When this was originally written, there really weren't many effective abstractions of the DOM.
I myself am a ASP.NET MVC developer by day, and play with Node.JS by night. I agree with you on the difficulty in moving outside the .NET world, but I will say ASP.NET MVC isn't nearly as bad as webforms. Webforms abstracts so much of how the web works away that that it's extremely difficult to wrap your head around anything else. And like you said, because the abstraction is so deep, it's very difficult to make room in your mind for anything BUT webforms. With ASP.NET MVC, I've found very little difference. The majority of the coding for most modern CRUD apps is on the client-side anyway, so the majority if your knowledge is transferable to Node.js. Express and ASP.NET MVC both follow a restful model, and I already had experience working with closures, async calls,from client-side javascript, so I haven't found the conversion to be very difficult at all.
I don't understand this:"The iPad is a credible laptop replacement for many people and with iCloud and another year or two of hardware improvements, that’s going to be true for more and more people. The Kindle Fire is a laptop replacement for almost no one. It’s a peripheral, not a second computer and it’s priced accordingly. " What is it that makes the iPad a possible laptop replacement, but the Fire not? To me, the primary market for people replacing laptops with a tablet are casual users, many of whom care more about content and entertainment than producitivity, in which case it would seem the Fire would be equal to, if not beating, the iPad.
So is this a competitor to something like spreedlycore? I'm trying to find a recurring billing provider which can handle multiple merchant accounts, and the only thing close was spreedlycore, which handles the processing but none of the recurring functionality. Nobody seems to provide a recurring billing solution which supports multiple merchant accounts.
Man - I would kill for this. We use fogbugz / kiln right now, and integration into these boards for cases / users / pushes would be the icing on the visibility cake.
Stackoverflow is written in .NET. It certainly has a more "corporate" focus than node or something - but that's not to say there aren't people building cool applications with it.
Google docs might have not gone down for everyone, but when we used it, twice we had instances where entire documents got nuked. Eventually two week old backups were restored, which was essentially useless for the type of documents they both were.
Agreed - although I will say I've lost count how many times I've had to explain to a junior that "push would create remote heads" just means you need to fetch and then push...
Maybe I'm just an idiot, but it took me much longer than it should have to get SSH support setup for Github on my Windows box. I had no such issues with Hg.
Having used Mercurial and Git, I have to say I vastly prefer the interface of Mercurial. It still has its quirks, but overall I find it much easier to use, especially on Windows. Git was very clearly built as a Unix solution first, with Windows support hacked on later.
He mentions how broken the typical interview process is, something I hear repeated frequently. I'm curious what you guys think the "ideal" interview process would look like?