Where the design community meets.
Developer Joined almost 8 years ago
To someone hiring for any programming role, failing FizzBuzz in any programming language you claim to know is instant rejection territory.
I disagree. If I'm interviewing someone and they've demonstrated a bunch of good skills, have a good attitude, and demonstrate the ability to think on their feet, failing Fizzbuzz when they're put on the spot during an interview isn't an instant-fail in my mind.
Not knowing how the % operator works (or hell, even exists) isn't the end of the road. I may not hire that person as a lead, but if it's a junior position and the candidate seems like a person who has a lot of enthusiasm and possible capacity for learning, I'd still consider them. I'd rather hire that person at the appropriate level, than someone who's not going to fit personality-wise.
The reason I scoffed at the original article was because the author seemed to relish in the fact that he/she had a lot of experience getting things done, but when faced with a problem he/she was unable to solve, he/she got overly defensive instead of trying to actually solve the problem.
The point of things like Fizzbuzz or other programming tests aren't just to demonstrate that the candidate can necessarily complete the task, but to test how the developer approaches a problem and comes up with a solution to the problem.
The author of the original piece did a terrible job of trying to work with the interviewer to come up with a solution, instead choosing to flame out in spectacular fashion.
That to me is the damning thing about the article -- the author's shitty attitude demonstrated in even writing the piece that he/she was remotely in the right in regards to the whole topic. The author was wrong, and went shouting from the rooftops to let everyone know how poorly he/she handled the situation.
I scanned a QR code once in my life.
I went to Gamestop and actually had a good experience chatting with the guy working there, and on the receipt was a QR code for leaving feedback, so I thought I'd throw the guy a bone while my wife was in Old Navy.
I found some dumb QR app on the iOS App Store, installed it and found it to be pretty awful. Ad banners everywhere, etc.
Got the code to scan, and it directed me to a web page. Hilariously enough, the receipt had a QR code, and below that a 20-digit number that represented my transaction, but the awful part was that the 20-digit number wasn't encoded in the QR code -- that just took me to the front page of the site and it was up to me to punch in the 20 digit code.
I uninstalled the QR app and called it a day. lol
All the free QR apps I've ever found in the App Store make it obvious that scanning QR codes is less important to the developers than serving up ads. ;)
What's the point of this article? It's like someone writing a humblebrag for Basecamp.
This is a trick article. The only requirement for designing user-friendly carousels is not to use a carousel. ;)
I debated between the 11" and 13" when I bought my Air. I ultimately decided on the 13". I thought about it, and the 11" was a little too close to netbook size for my liking. I haven't regretted it yet - it's a great laptop.
Got a 6. I have an ElevationDock and an iHome clock radio I'd have to heave-ho if I got the Plus. The 6 just barely fits in both. ;)
Don't miss the buttons at the top left -- it does a CSS Zen Garden-style reskinning of the thing on the fly. When I cooked it up seven years ago, I loved the idea of CZG and knew I wasn't talented enough to make a theme of my own that would make the site, but loved the idea of having a playground to try out ideas, so I figured I'd make it happen on my resume as an interesting discussion piece during interviews.
Long story short, it worked. Since then, I've more than doubled my salary navigating the choppy waters of my career.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.