Photo by Branko Stancevic on Unsplash

The first time I was involved in a technical interview I was asked to present and grade a coding question: “What does this script do?” The candidate was then handed a print out of a (relatively) simple VBScript that changed the computer name of a Windows PC.

Only one candidate answered correctly. Every other candidate failed the question with an “I don’t know.”

On first glance, this seems a reasonable question. Part of the job they were interviewing for often required working with scripts to deploy computers and software. I told them that we weren’t looking for a specific answer, just a general idea of “What does this do?” The candidate failing to even make a guess seems like an interview fail. They couldn’t think on their feet. They couldn’t think creatively.

But was it really a failure of the interviewee?

Read More >

The goal of this post is to present a relatively simple agile-like development process to get started with.

The main audience is new Project/Product managers or developers trying to wrangle a chaotic development cycle.

A good primer on the reasons why you need a process can be found here: Negotiating a Process.

Good? Let’s get started then.

Read More >

No one likes a new process. It’s work to memorize, it’s work to do, and it removes your own autonomy from a situation, keeping you from just doing whatever you want to do.

But working without a process leads to chaos. Missed deadlines. Solutions that don’t actually solve the problem. Angry customers. Angry managers. Angry developers.

Read More >