1. 3

I have created a medium to guide others through code examples. I have been using collections of these ‘playbacks’ for the CS classes that I teach. Here are some examples:


(These are best viewed on a big screen)

They are good for getting a peek inside the head of a developer who writes some code. My students seem to like them.

I am wondering if people who hire sw devs would see any value from a potential candidate’s ‘code portfolio’ of playbacks?

Here is a test portfolio I put together:


I am looking for feedback. I am mostly wondering if it makes sense for developers to create professional portfolios to show to potential employers.

Here are some questions I have that readers might be able to help me with:

  • Is this any better than looking at a dev’s GitHub repos? Worse?
  • Is there any value in seeing a candidate’s code this way from a hiring perspective?
  • Would it take too much effort for a hiring team to work through a portfolio?

  2. 3

    Your playback bit is cool. I like it. I still prefer looking at GitHub repos instead, though, just because it’s much faster. Watching the code be written isn’t that useful to me because I’m used to personally making lots of false starts before I get somewhere and I expect others to do so too.

    It’s more interesting to me to know what someone thinks good stuff looks like rather than for them to show me the character by character handling of how to get there.

    1. 3

      I’m just (“just”) a software engineer, not a manager, nor an SE who is often asked to interview. That said, if I were to hire, the primary thing I would be interested in is the human-human interaction of a prospect. Written code, while still important, would be secondary. To determine employer-employee fitness as regards both of these aspects, I would do pair programming in a scheduled session (call it an interview, if you want), and then make my hire-or-not judgement based on that.

      Regarding what I mean by human-human interaction, I can give details if desired.

      1. 3

        Much as it pains me to say it (because it is neat!), I simply wouldn’t bother if this came alongside a CV. If everyone submitted these, the time to screen submissions would explode. While there’s no doubt useful information to be gleaned from a playback, I’m not that interested in the step-by-step process of producing code, even with sideband comments annotating it. A repository (or any complete collection of code) gives me relevant information that I can peruse and examine in a fraction of the time, much like a blog post vs. a video tutorial.

        This might be different if I was hiring for junior or intern positions and the general standard was lower, though!