Guides
Practical guides to tracking coding time: from git history, from the terminal, and from whichever editor you actually work in. Each one covers what the method measures, where it breaks down, and what to do about the gap.
How to Get the Most Out of DevClocked (Complete Guide)
The full mental model behind DevClocked: coding time vs session hours vs dev time, what each tracker actually records, sessions and work blocks and agent streams, reports, issue links, and invoicing. Written for a first week on the product.
Engineering Work That Never Becomes a Commit (2026)
Code review, thinking, agent supervision, config work, and dead-end spikes are engineering work that never becomes a commit. A taxonomy of the six types, where each one does leave a trace, and how to measure the part git cannot see.
How to Track AI Token Spend by Project (2026)
To track AI token spend by project you need per-session records carrying the model, the token counts split by pricing tier, and the repo the session ran in. Here are five ways to get that, where each one breaks, and real numbers from a 13,674 dollar month.
What Is Agentic Engineering Intelligence? (2026 Definition)
Agentic engineering intelligence is the measurement of software work done by humans and AI agents together: session time across IDEs, terminals, and coding agents, tied to commits, PRs, and token cost. Definition, the five dimensions it measures, and how it differs from developer analytics and editor time trackers.
How to Show Coding Activity on Your Resume (2026 Guide)
How to show coding activity on your resume without padding it: turn commits into quantified bullets, link one verifiable destination, and skip the screenshots recruiters ignore.
The Best Way to Track Freelance Developer Hours in 2026 (Passive, Provable, Billable)
The best way to track freelance developer hours is passive tracking built on your git history plus a telemetry layer, not manual timers. Here is the exact setup, step by step.
How to Track Time Spent on a Coding Project (2026 Guide)
How to track time spent on a coding project accurately: scope the project first, pull a free baseline from the repo's git history, then add passive telemetry that attributes sessions (including AI-agent work) to the right project.
How Many Hours Do Developers Actually Code? (The Real Numbers)
Studies put real hands-on coding time between 52 minutes and 6 hours a day, not 8. Here is what RescueTime, Amazon, and 2026 survey data actually found, and why the range is so wide.
How to Track How Much Time You Spend Coding (2026 Guide)
A step-by-step way to track how much time you actually spend coding, why manual guesses run short, and which layer (plugin, git, telemetry) gets you a number you can trust.
The Engineering Manager Productivity Dashboard: What to Track (and What to Cut) in 2026
What actually belongs on an engineering manager's productivity dashboard in 2026: DORA for delivery, churn for quality, leverage for effort, and why commit counts and lines of code should be deleted, not displayed. A builder's guide to the dashboard, not a vendor's.
DORA Metrics Explained: The 4 (Now 5) Delivery Metrics That Still Matter in 2026
DORA metrics explained: what deployment frequency, lead time for changes, change failure rate, time to restore service, and reliability actually measure, why they survived the AI-generated code era when volume metrics did not, and how a solo developer or small team can track them without buying an enterprise platform.
Engineering Productivity Metrics That Actually Work in 2026
Engineering productivity metrics in 2026: track delivery (DORA), quality (churn and change failure rate), and leverage (output per unit of real effort) instead of commits, lines, or hours. Which metrics survived the AI era, which to retire, and a small stack that works for individuals and small teams.
Changelog
All updatesAugust 13, 2026
Export Reports as PDF
Every report — Overview, Commits, and Issues — now has an Export PDF button that produces a clean, print-optimized document honouring your active filters and date range, ready to attach to an invoice or share with a client. Exports are generated locally in your browser; no data leaves your machine.
August 13, 2026
Figma Design Tracking
The Mac app now tracks time in the Figma desktop app as real design hours — automatically, with nothing to configure. Turn on optional file-name tracking to attribute design time to individual Figma files and auto-map it to projects by naming files "Project — File". Off by default, reading window titles of design apps only, behind an explicit macOS Accessibility grant you approve yourself.
July 5, 2026
Issue Attribution — Linear & Jira
Connect Linear or Jira to sync your issues and automatically tie them to the sessions and commits that shipped them. DevClocked matches issue keys from branches, commit messages, and pull requests, so delivered work links back to what it was for — read-only, with no writeback to your tracker.
June 25, 2026
Slack Integration
Install the DevClocked Slack app to bring reports into your workspace. Admins pick channels and posting rules, and each member links their own account with /devclocked connect for private personal reports and shared team digests.