953 karma · joined December 27, 2008
- Bugs in the system are dangerous; for instance, if I did my quiz in an hour but it got submitted as two, my job opportunity could be lost
- People will get around your anti-cheating methods
- People will practice or memorize solutions to your quiz (while there's no problem with practicing, this allows people who are good at solving your quiz but bad at programming in general to get through)
- Code comparison may not be useful, especially since a lot of tasks will lend themselves to being expressed in just a few ways which most code will use
- Defining a useful metric for "how good your code is" is tricky, possibly impossible
It'd be especially good if your quizzes asked for things that needed to be implemented anyways. It'd be a nice, cheap way to build up an open-source code repository.
Honestly, I'd probably do the quizzes just for fun. Now that I think about it, something similar already exists which I do play for fun: http://projecteuler.net/
Altogether, it sounds like a good idea if you can get the details right.
As for the photos: like I said before, they don't look underage to me. I've additionally checked this with a few people in other age ranges of both genders, just to be sure I wasn't crazy, and the consensus was that they all looked like adults.
P.S. The "If you don't agree with me, you're <insert x here>" approach is a bit silly. I do like to consider myself pretty open-minded, though :)
One small usability tip: you could pretty easily combine the login and registration forms. Just put an extra "register" button, do a username check, then add a second password box and the name fields. Also, it'd be a little nicer (though I see what you're doing with the in-one-line thing) if you stacked the password confirmation box under the other; I usually visually compare the lengths before hitting "enter".
Also, I noticed that the look and feel is in many ways similar to Flickr, especially the colors. I don't know if that's a positive or a negative; on the one hand, it will immediately associate your site with photography for anyone who's used Flickr before, while on the other hand it may make it harder to establish a unique brand.
I haven't explored the inside of the site much, but from what I can tell, you've done a pretty good job. Keep up the good work, and good luck.
The use case? Inline comments, feedback boxes, contact info, control panels, really anything you want to have immediately available but out of the way most of the time. Is this the best way to implement those? Not always, of course, but probably enough to warrant its existence.
The link you provided doesn't count. First of all, it's on a humor site, and the article definitely seems to belong there. But more importantly, it provides no evidence that the models are underage, the photos it shows don't appear to be me to be of underage girls, the photos aren't quite pornographic anyways (though admittedly fairly close), and it doesn't even provide any evidence that AA attempted to represent them as underage.
I'm completely willing to hear that AA is making child porn--I have no affiliation with them or anything like that--but you haven't provided any evidence and therefore you shouldn't make the claim.
This bit isn't E-prime.
This isn't to say you couldn't put together programs manually still, of course--it'll always be fun. But you could get rid of most of the tedious bits. Also, Lisp (or something Lisp-y) seems like the most likely candidate for putting code together this way.
I'll give him his clever phrase, despite being technically false. What we create with our knowledge of computer science (our programming) is not the same thing as computer science itself.
This is an interesting way to think about programming, though. Compare it, for instance, to metalworking. The craft itself, clearly, is distinct from the science of metallurgy, but at the same time they have evolved alongside each other. I wonder if programming and computer science will go through a similar progression. As metalworkers just were learning to manipulate metal, we bit-twiddled and hand-assembled; as metalworkers evolved their tools and meticulously forged their creations, we created compilers but still hand-coded our programs. The next big step in metalworking was the automation of their craft via factories; is this way code will go as well? Will we simply guide computers as they produce their own code? And what advances in computer science would be necessary for this to happen?
Edit: Please forgive me if my history of metalworking is slightly incorrect, I just realized I mostly pulled it out of my ass.
Of course, people could just back up, but some stuff is just hard to do that with, especially on the web.
Is it just me, or did they mislabel the section "Enterprise is Back"?
Strange, considering that the events feature is one of the most useful on Facebook, and because he has obviously used it (albeit inefficiently) since he's noticed events this way. Really, Facebook events are great for parties and things when you can't get everyone together at once to plan/discuss/whatever, (or when you're antisocial like me and you don't want to). A lot less phone calls and such to mess with, and a built-in discussion board and RSVP system to boot.
This is a really, really good point. I can't think of very many people who I'd expect to be able to answer. I can't, not really--I can tell you what I'm studying, but I don't think studying quite counts, at least not with something else accompanying it.