· Sergiy Oliynyk · Productivity  · 3 min read

The Problems with Time Trackers

Using time trackers in software development doesn’t guarantee better performance. In fact, it may even make it worse.

Using time trackers in software development doesn’t guarantee better performance. In fact, it may even make it worse.

Introduction

Some companies monitor developers using time-tracking software that records keystrokes, mouse movements, and periodically captures screenshots to ensure continuous work on a project. However, this creates a misleading impression because a time tracker can only confirm that a developer is pressing keys, moving the mouse, and keeping work-related applications open.

I’m not going to discuss cheating - when developers use software or hardware tools to simulate activity. Instead, I want to highlight other problems with time tracking.

NOTE

By “time trackers,” I mean any software used to monitor the time an employee spends at a computer for the purpose of calculating work remuneration.

Software Development Is More Than Just Coding

System Design

One of the most time-consuming activities in software development isn’t typing code but figuring out how to implement a feature or fix a bug in the most efficient way. While we often do this while looking at the screen - examining code snippets, requirements, or bug descriptions - it’s sometimes more effective to step away from the computer. Thinking through problems with pen and paper, during a walk, over coffee, or even while lying on the couch can lead to better solutions. Every developer has their own preferred approach. But how do you track these activities? Can I install a time tracker in my brain?

When working on a complex task, I continue thinking about it even after shutting down my work laptop. Many times, I’ve had breakthrough ideas while taking a shower or walking down the street. If a company only compensates me for the time I spend in front of a monitor pressing keys, there’s no incentive to think about work outside those tracked hours.

Meetings

Most developers dislike meetings because they consume a lot of time with minimal impact. But if you’re paid for the time spent in meetings (because the tracker records it), it becomes beneficial to extend discussions as much as possible.

Don’t get me wrong - every team has important topics to discuss daily, and meetings are a necessary part of software development. However, once all questions have been addressed, most participants prefer to wrap up quickly and get back to work. But why would you prioritize tasks if you’re getting paid just for being in a meeting?

Coding Efficiency

Most developers don’t enjoy spending excessive time typing code. That’s why we learn keyboard shortcuts, use code snippets, and appreciate tools like GitHub Copilot. But if what truly matters is the time spent typing, why bother optimizing? Why learn shortcuts when I can use a mouse? Why rely on AI to generate code if I can manually type every letter and get the same result although spending more time?

Constant Disturbance

Working with time tracker you need to remember to pause it when you stop working and resume it when you are back. It creates anxiety and decrease ability to think about work tasks.

Using a time tracker means you must remember to pause it when you stop working and resume it when you return. This creates unnecessary anxiety and reduces your ability to focus on work.

Conclusion

I’ve provided examples of how time-tracking software shifts focus from the real goal - delivering high-quality software in a reasonable timeframe - to simply logging hours. This approach diminishes motivation and stifles creativity.

As a result, time tracking has undesirable consequences for both employers and employees.

Back to Blog

Related Posts

View All Posts »