Towards Battery-Free HD Video Streaming http://batteryfreevideo.cs.washington.edu/
Discussion: https://news.ycombinator.com/item?id=16881946
1,592 karma · joined September 24, 2008
http://epicco.de
Towards Battery-Free HD Video Streaming http://batteryfreevideo.cs.washington.edu/
Discussion: https://news.ycombinator.com/item?id=16881946
IMHO, hiring based on homework is no guarantee that you won't end up with a bad hire anyway. It is just another imperfect data point to base your decision on, but one that comes at the cost of massively reducing your number of candidates.
Requiring homework is a great way to deter the kind of people companies should be most interested in hiring: those who are not actively looking for a new job.
I find this trend especially surprising considering that the U.S. has at-will employment where you can fire anyone anytime (at least that is my understanding, I'm from Germany). Why not get people at a desk quickly and evaluate them on the job?
Since I've signed out of Facebook on my PC and kill the mobile Facebook app while not using it, I tend to get multiple push notifications per day, most of them asking if I know some random person.
My girlfriend, who is on Facebook daily, has never seen any of these notifications.
I regularily used a similar exercise to weed out bad candidates. The task was to build a stack with based on a double linked. Looking up stuff was okay, but straight copy paste was not. I gave them half a day and told them to write the best code they can.
There where many discussions how that exercise is relevant to the junior PHP dev position we were hiring for (spoiler: it's not). But it gives you a good idea what the candidate considers good code (consistent code style, documentation, tests,...)
Edit: this is more or less worst case, i.e. highest tax class and public health insurance.
And I think that the policy to focus on mobile web first is sound for that use case.
I would document the backup process and communicate it to my manager/client with a mail like "hey, I set up backups, they are stored at <server>, docs are in the wiki".
Other potential issues: causing unauthorized costs ("who stored 10TB on S3?") or privacy violations, e.g. when working with healtcare or payment data.
[1] http://blog.backblaze.com/2012/10/09/backblaze_drive_farming...
While a small site might not be targeted directly, you might still get hit by an automatic attack if you use any off the shelf software. It's not fun when Google marks your site as harmful because your OpenX-Ad-Server suddenly serves malicious ads.
I think that proper use of HTTP methods is one of the core ideas of REST, but I understand that one might have to take shortcuts like _method to satisfy real-life needs while calling it RESTful to satisfy the buzz-word hungry PHB.
Let's just agree not to do something like GET /foo?_method=DELETE
Also, never rely on the internet connection at the venue and bring adapters if you have a Mac.
There might be a trademark issue, but I didn't check the Facebook ToS.
[1] http://itunes.apple.com/us/app/twitterrific-for-twitter/id35...
Out of curiosity, did you create this in 72 hours straight, i.e. a long weekend, or stretched out over several evenings?