1,730 karma · joined June 10, 2010
Don't know why you got the idea I was referring to Microsoft at all.
Edit: To clarify, and before I get another laundry list of achievements, I clearly don't think Google is one either.
This is why we at Google don't (or shouldn't, at least - it's widely discouraged) ask brainteaser questions in interviews.
I disagree on whiteboard coding though. I don't find it that easy, but I think it's reasonable to expect a demonstration of relevant skills before you hire a candidate. Any sensible interviewer won't expect syntax-perfect code on a whiteboard, but it's at least a way of seeing if the candidate can walk the walk rather than just talking for an hour.
> I guess I do not see how you can lose if you take the contract-to-hire approach ..
For the first month, the vast majority of people are relatively unproductive. After the next month, good candidates are generally still going through a significant learning curve. Contracting several candidates for a few months to pick one who seems good enough is expensive for relatively little output - apart from salaries, they need desks and computers etc, and you have to do some interviewing to pick them in the first place. It's not a worthless approach, but I don't see it as a panacea.
Morally, I think most people probably feel that it is cloudy and in such a case often justifiable, but that has little bearing on the legal situation.
The two aren't remotely the same - I find it fairly tedious (but explicit, which is sometimes nice) in C, but reasonably painless in C++ with unique_ptr and similar things.
As has been mentioned in other comments on this article, treating the two as the same language, or versions of it, is a mistake.
They do make it reasonably pleasant to run Windows as a non-admin user though, and not the impossibility that was in XP.
I think having them laid out that might make me more likely to react to them than if they were buried in a whole lot of jargon, which makes a slightly unpleasant case for longer agreements :(
Clause 1: you disclaim any fitness for purpose? Not only is this likely unenforceable in many jurisdictions, it seems distinctly weaselly to sell a product and attempt to claim that in the fine print.
Clause 2: does that mean if it erases my entire hard drive, you're not responsible? Seems a bit not cool; though I can understand wanting to avoid claims if it crashes and data is lost, it seems overly wide-ranging.
Clause 4: I have a perpetual license, until you decide it's over for no reason at all and that's that - in which case I get no consideration or refund?
Clause 5: as csense mentioned, at least parts of this would seem unenforceable too.
I guess maybe it makes it seem worse that it's all laid out starkly without all the jargon to mask them; they're not uncommon clauses to include in such agreements, of course.
IMO it's worth it to avoid that awful old chestnut where you'd run out of internal space with heaps left on the card, but unfortunately MTP isn't quite as convenient :(
Of course, it's kind of irrelevant to Dropbox; they don't have a horse in the platform race, so they're supporting all the major ones and doing very well, but they're not a killer app for any one of them. I don't think that proves that it couldn't ever have been a killer app, but it looks unlikely now that it'll be the case.