Skip to main content

2 posts tagged with "development"

View All Tags

The right way to email a git repository

· 2 min read
Brian Graham
Consultant

You're tasked with reviewing the code challenge of another candidate. You download the project.zip file, extract it, and it doesn't run. You can't tell what part of the code is auto-generating scaffolding, or what part is the complex part. You can't really get an idea of if the code would work, or was even written by the candidate. You don't even know if they did the entire project in one big commit or not. As long as there's nothing horribly wrong, you'll pass them.

Most companies have some kind of code challenge in their interview process. While you may like or dislike this practice for different reasons, one thing that can easily remove a bunch of headaches here is to stop asking for zip-files of that project.

What Slows Development Teams

· 6 min read
Brian Graham
Consultant
Historical Context

This article was originally published as a guest post for GitPrime in 2017, during the height of the Agile movement and the rise of DevOps practices. At the time, many teams were struggling with the transition from waterfall to iterative development, and developer productivity tools were primarily focused on basic metrics like commit frequency and lines of code.

Since then, the industry has evolved significantly with the emergence of DORA metrics, platform engineering, and more sophisticated approaches to measuring developer experience. However, the core challenges identified here around communication gaps between managers and developers, context switching, and misaligned incentives remain relevant today.

GitPrime Background

GitPrime was a developer analytics platform that provided insights into software development teams' productivity and processes. The company was later acquired by Pluralsight and integrated into their Flow product offering before being discontinued. This article represents thinking from the earlier era of developer productivity tooling, when the focus was primarily on code-based metrics rather than today's more holistic developer experience approaches.

Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law. – Douglas Hofstadter

Developers and managers both want scope and delivery time to align, but despite working toward a common goal, they rarely do. The gap is often so large that deadlines are missed, products become irrelevant, and teams face burnout.

Three major schools of thought explain why Hofstadter's Law persists in software development.