1,068 karma · joined January 27, 2010
Just like you could go back and implement for yourself the skeleton code they handed you, you could also go out and implement everything in the lectures without any assignments at all. It's just that, like you said, the assignments provide a useful starting point. And I'm only saying they could be even more useful by requiring you to implement more of the complete pipeline.
The fact that an incredibly self-motivated person could learn everything there is to know about machine learning with the course as a starting point doesn't mean that it's bad to make the course more useful for a somewhat lazier or less interested person.
From the article: 33% said they would use Bing more often after taking the Challenge
Two very different statements IMO - how many of those 33% are ever actually going to think about it again rather than just reverting to their old habits?
I agree with this. The programming assignments I've done so far in the Machine Learning class are usually 5-7 matlab functions, many of which are about 2 lines of code (the longer ones might be ~10 lines of code). If you've ever done matlab/octave programming the assignments will take about 20-30 minutes and be completely unenlightening as you're literally just translating mathematical notation into matlab (which is, by design, already a lot like mathematical notation anyway). They provide entirely way too much skeleton code to learn anything from if you're not actively trying to learn. If I weren't already mostly familiar with most of the material presented in the class, I imagine I would never retain knowledge of how the machine learning "pipeline" worked or have any high-level understanding of the algorithms, because the assignments just require you to implement the mathematical pieces of each step, without ever asking you to, for example, actually call any optimization routines, or put the pipeline together.
The problem, I think, is that it would just be too difficult to do automatic grading in a way that is reasonably possible to pass if they don't turn most of the work into skeleton code. Since the automatic grading needs nearly exactly matching results, one minor implementation difference in a perfectly good implementation of the algorithm itself (e.g., picking a single parameter incorrectly, picking the optimization termination conditions incorrectly, choosing a different train/dev split, etc.) would make the entire solution completely wrong.
(Too bad it'll probably be a while before robot cars can legally operate without a human in the driver's seat and paying attention, though)
(I'm assuming your point was that Spotify probably pays at least as much per listener as the radio.)
Less abstractly, I think the author's point about the standardized "UI" for cars is a good one - society is better off, not worse off, as a result of companies copying each other in the auto industry. If you can drive one car you can drive them all (well...except for the automatic/manual thing). You don't need to spend three days relearning how to drive every time you rent a car. In the same way, society benefits a LOT from familiar UI design across different software companies - e.g., anyone who has ever used any mainstream desktop OS in the past 15 years or so can pretty quickly figure out the basics of any other mainstream desktop OS - they all have programs partitioned into "windows", have a "desktop" with "icons", etc. These UI elements all seem trivially obvious to us precisely because of copying, but there are certainly alternatives to all of them.
Am I being dumb or are you saying Facebook pays for their employees' groceries if they choose to work from home instead of working at the office and eating at the free cafe(s) there? I'm impressed if so (even though it probably wouldn't really add up to that much money for a company that can afford to pay $1B for Instagram).
(Of course being in the same room doesn't hurt in that respect either, but partitions have other advantages as well, e.g., aesthetics and noise.)
I'm confused, can anyone offer any insight as to how a neuropsychologist would be genuinely surprised by this case? I would have expected that a rather large percentage of a general neuropsychologist's (or at least one that specializes in children) patients would be people who "function at the bottom 1 percent".
Edits: Wow, I need to learn to make sure I reread sentences in full when I go back and reword something.
[1] http://www1.icsi.berkeley.edu/~farrell/birdlets/iccv11-camer...
... is it just me or would this be an incredible perk? If a roll of quarters and an envelope with $250 worth of $1, $5, and $20 bills were delivered to my desk every month I'd save a lot of time going to the ATM or the laundromat for tips/laundry/cash-only restaurants/etc. I think I'd willingly give up a lot more of my salary than it's actually worth for the convenience of perks like that. Free laundry (like, full wash and fold and dry cleaning)? Shit, for that I'd probably take a $95K job over a $100K job (all other things being equal) even though it's really worth ~$1000 at most (comparing against the cost of laundry services, not machines, of course). Does Facebook still have that?
I suppose there is one possible negative consequence to users who opt not to use app-specific passwords: their existence alone removes some of the incentive for client applications to implement 2-factor themselves (which I don't know if Google even has an API for). And sure, it would be nice to have features like access control on a per password basis (e.g., so I could allow Pidgin to access only gchat, but no other part of my account). But the implication that the mere existence of application-specific passwords somehow makes Google's 2 factor auth useless is just wrong.
They are strictly better than using a single password for everything though, in that they are unique and strong (due to being automatically generated and 16 characters long), and easily revocable.
Though, I do think it would often mitigate the damage from this type of security breach that it seems like we've seen so much of from big name tech companies lately. I'd guess that a majority of accounts created on the internet are pretty unimportant to the account creator, and with how often passwords are reused indiscriminately, the worst effect of these password leaks is often not the unauthorized access to all those accounts on the hacked site but rather the usernames and passwords themselves - which are very often reused for bank, email, etc. accounts. With my proposal, anyone who opted not to have a password wouldn't be vulnerable to that.
I have a Gmail tab opened just about 100% of the time I'm on the computer, so this would be very convenient for me as an alternative to having to remember passwords for sites that I visit once a month or less (and end up having to get a "password reset" link via email every time I log in anyway), and then I'd only have to keep my Gmail account secure (which I do via 2 factor).
But in that sense an executable file isn't any different from a non-executable file, is it? The default app for the file could do equally dangerous things with a non-executable.
Personally I thought that part was hilarious. I'm not sure whether it was true or not (due to how naive it made the author seem) but I definitely enjoyed the article more because of it.