#Measuring Engineering Effort, Not Code Volume

In the complex world of software engineering, understanding genuine effort is often clouded by outdated metrics and subjective feelings. The developer who appears perpetually "busy" might be delivering less value than the one quietly shipping clean, efficient code. Tempo, ScreenJournal's engineering analytics (launching soon), is designed to move beyond vanity metrics and derive context and true effort from Git activity, so managers can support and coach their teams on the value they deliver rather than the volume of code they produce.

#The End of the Lines of Code (LOC) Fallacy

For decades, Lines of Code (LOC) has been the default, yet deeply flawed, proxy for developer productivity. The philosophy behind Tempo rejects this metric for several critical reasons, because measuring by volume actively encourages the wrong behaviour:

• It Punishes Quality Work: LOC fails to capture one of the highest-value engineering activities: refactoring. A great developer often removes hundreds of lines of complex, legacy code to replace it with a dozen lines of clean, simple logic. LOC metrics would register this crucial simplification as "negative productivity."
• It Rewards Bloat and Inefficiency: When measured by LOC, developers are incentivised to write verbose, padded implementations, inflate their code volume with unnecessary comments, or avoid using efficient libraries and frameworks. This results in technical debt and increased maintenance costs, which is the opposite of high performance.
• It Ignores Complexity: A single-line change to a core security function might require days of research, testing, and architecture review, delivering immense value. A one-hundred-line change to boilerplate UI code might take an hour. LOC treats these two tasks as being 100-to-1 in value, which is demonstrably false.

#Estimating True Effort with AI

Tempo is designed to replace the flawed quantitative approach of LOC with a smart analysis powered by frontier AI models. The aim is not to count activity but to read and understand it.

Because Tempo is Claude Code and engineering analytics, it reads the local repository and Claude-specific files to analyse relevant development artifacts and produce a contextual Effort Score:

1. Code Context Analysis: The model processes the content of commits, PR descriptions, and issue summaries. It is designed to recognise when a small code change resolves a complex, critical bug versus when a large code change is simply a routine feature addition.
2. Complexity Recognition: By analysing the structure and content of the codebase where the changes are made, the model can estimate the cognitive complexity of the task, so a developer who solves a thorny problem with minimal code is credited for the value delivered rather than penalised for a low line count.

The point of this score is to make effort visible and discussable, not to rank people against one another. Scores are contestable, and engineers see the same picture their managers do, so the conversation stays about the work.

#Surfacing Real Effort and Engagement Patterns

Tempo is also designed to give managers a fairer view of engagement over time, drawn from consistent Git activity (commits, reviews, comments). The goal is to open supportive conversations, not to catch individuals out.

• Sustainable Pace: By reading the frequency and timing of meaningful contribution signals, Tempo can surface where someone's engagement looks unusually low, which is often an early signal of burnout, blockers, or unclear priorities rather than a lack of effort.
• Patterns Over Snapshots: Tempo is designed to distinguish normal fluctuations (an occasional sick day, a week spent in design reviews) from longer-running patterns worth a conversation. This gives managers objective context to check in, remove blockers, and coach, rather than guesswork to police.

Used well, this is a coaching tool. It helps a manager notice when a strong engineer has quietly taken on the hardest problem in the sprint, and when someone capable seems stuck and could use support.

#How ScreenJournal Fits In

Tempo is the engineering-specific angle, and it is launching soon. In the meantime, ScreenJournal already helps teams see what actually happened in a day: it reads on-screen work as short-lived video, writes a timeline of what each person actually did, then deletes the raw screen data. When you need a summary, ScreenJournal can draft a standup on request through Ask AI chat or MCP, so the write-up reflects the real work instead of a hurried recollection.

To see how Tempo brings this together for engineering teams, take a look at what we are building for engineering teams.

#What are you waiting for?

Head to screenjournal.ai to see how ScreenJournal surfaces real work, and to be first in line when Tempo launches.