The twitterverse has been alive with discussion about the generic FizzBuzz test and it’s effectiveness as a filter in the hiring process. There has been mixed reaction from both sides – some find it an effective way to weed out candidates, while others find it an uninteresting or even insulting approach to hiring. There’s even reports of candidates leaving the interview after being asked to complete FizzBuzz!
So I was at Prairie Dev Con last week, giving a few talks. David Wesst was right before my Win 8 with HTML/JS talk and totally nailed his HTML5 talk. It was entertaining, had flashy demos, and really got the point across. After that he came to me and we started talking about “live coding” in presentations.
I’ll be presenting at Prairie Dev Con 2013 in Winnipeg tomorrow, and since there’s so many good talks this year I want to give people a bit more information on my two talks to help those decide if they’d like to attend (or not).
New idea of the week! How about a Visual Studio add-in that lets you listen to online playlists that consist of your favorite songs as well as songs that other developers are currently listening to?
For me, one of the most important aspects of the agile movement has been self-management. Moving from a “here, work on this” management model to a “let’s work as a team” has made huge strides in productivity for development groups around the world. One of the key tenants of this has been ownership.
There’s a common misconception from a management/executive standpoint that throwing more staff at a project or problem may increase the progress or throughput. Of course, most developers and other knowledge workers know this is definitely not the case, but it’s pretty hard to describe why – it just doesn’t work that way. I’m going to take a stab at explaining it in terms that everyone can relate to.
Just finished reading The Programmers Before Us Were Better, where the author proposes that because of a lower barrier to entry into software development is corrupting the industry as a whole. I left that article with a feeling of “yes, but…” – I’m going to attempt to clarify my thoughts on this post.
Analytics are great. They help measure and compare information. Sometimes that information is important, sometimes it’s superfluous, but the important thing is you’re capturing it. The thing that gets me is the part afterwards – what do you do with those numbers, with those comparisons, with all that data after you’ve captured it?
I read an article last week, Don’t worry that your job is pointless, that tries to assure developers that although we’re not out saving babies or changing the world, that’s okay. We’ll get plenty of other opportunities to change people’s lives outside of our career – focus on those. Based on a few personal ancedotes I find myself disagreeing with this viewpoint – as developers, we make a lot of difference in the world whether we know it or not.