Proof & Attribution
Showing what you shipped and who or what produced it, in a form that survives someone checking. Covers verifying contributions, separating your own authorship from what an agent wrote, and the work that never becomes a commit.
AI vs Human Code Attribution: How to Split Credit Accurately (2026)
AI vs human code attribution is not something you can read off a finished diff. Here is how attribution actually works: track authorship at the moment of writing, separate agent output from human decisions, and keep an audited record instead of guessing after the fact.
How to Turn Your GitHub Activity Into a Developer Resume (2026)
Your GitHub already contains better resume material than anything you could write from memory. How to build a developer resume from GitHub activity: mine your commit history for real bullets, quantify without lying, and link one verifiable destination.
How to Show Your Coding Activity to Recruiters (2026)
Recruiters spend seconds on your profile and cannot tell curated activity from gamed activity. How to show coding activity to recruiters in a way they can actually verify: curated repos, visible recency, and an audited record of what you shipped.
How to Build a Developer Portfolio From Your Git History (2026)
Your git history is a truer portfolio than any curated site, because it is a record of real work rather than a claim about it. How to turn commit history into proof, and where it falls short.
Resume vs Proof-of-Work Profile: What Actually Gets Developers Hired in 2026
Resume vs proof-of-work profile, compared for developers in 2026. What each one is for, why a resume is a claim and a proof-of-work profile is evidence, and when you still need both.
LinkedIn vs GitHub for Developers: Which One Actually Gets You Hired in 2026?
LinkedIn vs GitHub for developers, compared for 2026. Which one recruiters actually read, what each is best for, and why neither one proves you wrote the work.
GitHub Profile vs Portfolio Site: Which Should Developers Build in 2026?
GitHub profile vs portfolio site, compared for developers in 2026. Which one actually proves your skill, what each is best for, and why neither verifies the work on its own.
Best GitHub Wrapped Alternatives for Year-Round Coding Stats (2026)
Looking for a GitHub Wrapped alternative that works all year? Here are the best options in 2026, from free recap generators to audited profiles that track what you and your AI agents actually shipped.
How to Verify GitHub Contributions (and Why the Green Squares Don't)
GitHub's contribution graph shows activity, not proof, and it can be gamed in minutes. Here is how to verify GitHub contributions properly: read the commits, check authorship, and confirm the work behind the squares.
How to Prove Your Code Is Human-Written, Not AI (2026)
You cannot prove code is human written not AI by inspecting the code, because finished output looks identical either way. Here is what actually proves human authorship: provenance, attribution, and an audited record of how the work happened.
How to Prove You Wrote the Code (Not AI) in 2026
AI writes a large share of code now, so 'I built this' settles nothing. Here is how to prove you wrote the code: provenance, an audited trail, and what actually holds up when someone checks.
Strava for Coding: What It Means and Why Developers Want One (2026)
Strava for coding is a profile that records what you actually built over time and proves it, the way Strava logs every run. Here is what the analogy gets right, where it breaks, and why it matters in the AI era.
Changelog
All updatesAugust 26, 2026
The DevClocked Agent
Ask questions about your own data in plain language at /agent. It reads through 15 tools covering summaries, projects, time breakdowns, sessions, commits, clients, invoices, unbilled time, timesheet items, invoicing coverage, and workspace rollups. Eight more tools can propose actions, but nothing runs until you accept its confirm card. Ask it to close out the month and it walks the invoicing recipe one step per turn, from coverage check to invoice draft. Available on Pro.
August 23, 2026
Gemini CLI Agent Tracking
The Mac app now reads Gemini CLI sessions, so those agent turns land beside your Claude Code and Codex work instead of disappearing into plain terminal time. The daemon parses your local session files for the model, input, output and cached tokens, tool calls, and subagent nesting, then attributes each session to the right project. Message content never leaves your machine; only counts and metadata are sent. Requires Mac app v1.4.49 or later. Gemini models are not priced yet, so you will see token counts rather than cost.
August 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.