Coder Radio Video

We discuss the top stories submitted by the audience this week. From the ultimate bridge burn to Stack Overflow’s developer survey & being ok with a little sociopathy.

Mike had a dream & that dream didn’t work out. Today we discuss how fixed contracts lead to fixed death & with perfect hindsight we debate what we might have done differently.

Plus some great feedback, a little nostalgia & more!

Transitions in life comes in many forms, work, relationships, gadgets. How we deal with the process of transition is key & why we shouldn't be anxious about a transition, even if it’s a difficult one.

Plus a bit about GitHub’s ongoing DDoS, switching from PHP to Ruby & a new contender for the perfect Linux dev rig.

It’s a special open mic edition of Coder Radio. We discuss the complex reasons behind Microsoft’s choice to open source MSBuild, the quest for the perfect Linux laptop continues & why, oh why, oh why HTML5 has a place.

Plus emails & more!

Chris shares what he’s loving about Android from a users perspective & Mike goes into what is driving him crazy from a developer's standpoint.

Plus redefining DevOps, starting a multi-user database & more!

We revisit some of the audience's favorite editors, then discuss the reality of terrible engineers.

Then Chris spends the weekend with a smartwatch & believes he’s discovered their purpose. We examine the audience for smartwatch apps in light of the Apple Watch announcement today.

The guys picture working a 9-5 job. If the security of a 9-5 paycheck is a myth, is it really just not having to worry about all the little things that's so appealing?

Plus how merit based hiring could get out of control & making documentation a bit less evil.

Mike and Chris start the show by sharing some hard learned advice, and discussing the events of the last two weeks.

Then we touch on SuperFish, Ubuntu Touch, and more!

Join us as we hop in our time machine and revisit some past topics on the coder radio program.

Can’t we all just settle down & focus? Mike’s just about had it with javascript framework madness. Plus could Microsoft be uniquely positioned to take advantage of the eventual die off of some frameworks?