611 karma · joined May 13, 2013
I can't fault free new music, but this interface feels like it was poorly bolted on to a retail sales website, which is exactly how the web video service has always felt.
Edit: I just realized that 3 of the albums are in the search results. I turns out the right tab is scrollable, and after 15 items, it switches to showing matching albums, which includes 3 of the 4 Daft Punk albums, and also some Macklemore.
While you could consider this advice on how to game an interview, I would argue it's also excellent advice on how to become a better software engineer.
That's interesting. Including titles of nobility makes things much more interesting. The appropriate thing to write on an envelope for a Duke is "The Duke of PlaceTheyAreDukeOf", and the letter starts "My lord,", but a baron is handled differently. He gets "(The Rt Hon) The Lord PlaceTheyAreBaronOf." And that doesn't even begin to cover all the cases.
For instance, I'll bet ya that allowing people to share their moods on Facebook leads to measurably different and likely less accurate mood graphs.
Hrm. 50% increased firings seems kinda high to blame entirely on frequency of review. Were these guys bad and the managers just didn't realize it under the old system? Or do they always fire one unlucky guy every review cycle and just do the same thing but more frequently now?
Pros:
* Tests are self-updating. Add a new feature: tests come in for free. Change a feature: tests automatically update. Fail to document a change: tests fail.
* Tests are unusually thorough
* Eventually consistent testing. If nobody ever complains, it probably wasn't a bug worth fixing.
Cons:
* Tests cannot be run offline. Feature must be committed and deployed before tests can be run.
* Potentially large quantity of false positives (bad bug reports)
* Potentially large quantity of false negatives (nobody notices particular bug, release considered good)
* Does not work for non-user-visible features
So basically you trade the reliability of your tests for a substantial build/release speedup. Some users experience each bug, but they are the users who are actively using the meta-community and have signed up to experience more bugs. Still, lack of pre-release unit testing must radically increase the importance of VERY careful code reviews.
Not the decision I would have made, but definitely has the sorts of advantages that a small team of engineers drool would drool over.
Well said, sir.
We all agree that math isn't patentable, so let's assume that. As math is not patentable, no mathematical theorem, proof, or function is patentable. All processes that exist entirely in software are representable as a series of mathematical operations. Therefore, software methods are math. As math isn't patentable and software is math, software must also not be patentable.
Milk republic? Potato republic? Egg republic? Atlantic salmon republic?
That said, I don't think there's any evidence that the existence of the patent system prompted its invention, and so I wouldn't call this an argument in favor of patents.
There is some intrinsic value to the softcopy, but mostly convenience and being freed to sell your hardcopy.