203 karma · joined September 10, 2009
But as I said, it's not too big of a deal, if they would only post ahead of time how long puzzles would be active, so one could complete them before this tightly-timed period.
As a side note, I think there is also a subtle common UI pattern to abuse the hover feature on websites which is common in flash. It makes touch-based browsing more difficult and I wish web developers would avoid it. It isn't fair to blame flash for it though, javascript can do it too.
I sort of imagine that these puzzles have an outlier effect: it removes the top and bottom users from a selection pool. Maybe that's okay, personally I was a bit disappointed at the missed opportunity.
One way they could improve this is by giving the puzzles expiration dates, removing the fear of completing one far ahead of the interview process, and having it expire. You'll still miss out on those who haven't heard of ITA until the near-graduation career fairs, but it will at least improve the situation.
Computer science
Internet
Pornography
Bam!
Regardless, the assumption that pornography would be in every book assumes that you don't cluster the data to topics with strong clique behavior and normalize the data to remove overly-linked (aka obvious) topics.
Sorry if I'm misunderstanding your reply due to its brevity, but again, error correction is the primary concern of these barcodes, and given that they are good error correctors, you can put what data you want within them, be it an underlying visual programming language or text.
If by "yet" you mean your proposal is to expand on these visual languages by making a programming language + error correction system, you're not adding any value that didn't exist before, it is the same thing as what already exists.
And besides, it's better to just give the user a URI and then they can download the application from a more robust location.
Using something like piet doesn't maximize reliability (error correction) and thus isn't good for that domain.
You should change the description from "reusable todo lists WTF?" to "Sharable workflows for your everyday life", that would be a succinct description that markets it better.
You could argue that checklists are helpful: http://www.huffingtonpost.com/lloyd-i-sederer-md/is-your-doc... and that you help enable the creation and sharing of the knowledge required for processes.
You could then enable people to tag their checklists with uses "budget planning checklists", "software design checklist" etc.
But even still, there's not a lot of meat on your "app", it's basically a ReST cookbook application right now.
I point it out because it is useful to always be mindful of their absurdity.