⌘+S. Notch flickers: detecting, creating, done. Issue #42 lives on GitHub, your //TODO comment hyperlinked back to it. You’re still in VS Code, cursor blinking innocently.
Bar Ticket just shipped — a macOS menu bar app that watches your files like a hawk, snagging every new TODO comment the instant you save. No tabs. No shortcuts to memorize. It’s the friction-killer devs have whispered about for years.
And here’s the thing: we’ve all got graveyards of TODOs in our repos. They pile up, mocking us during code reviews. The creator nailed it:
You write //TODO: comments all day. You file maybe 10% of them as GitHub issues. The rest die in your codebase. You know it. I knew it. So I fixed it.
Spot on. But why does this matter now? Because dev debt isn’t abstract — it’s those untracked “fix laters” that balloon into outages.
How Bar Ticket Actually Parses Your Chaos
File system events. That’s the secret sauce. macOS fires them on save — Bar Ticket listens, scans for //TODO: patterns (case-insensitive, flexible). Grabs the comment text as title, appends context.
Then, git config magic: it sniffs your repo’s remote, pings GitHub API. Two seconds flat. Appends (#42 github.com/yourrepo/…) right to the comment line — bidirectional link, baby.
Editors? VS Code, Xcode, Vim, Cursor, Zed. Whatever. As long as it’s a file on disk. No plugins needed. (Though imagine if it hooked LSP someday — but nah, this stays ambient.)
The notch animation? Chef’s kiss. Visual feedback without popups. macOS 14+ only, leveraging that modern menu bar real estate.
Why Do TODOs Rot? Blame the Switch
Context switching murders momentum. Studies (yeah, those flow state ones) peg it at 15-20 minutes per interruption. Flip to browser, hunt repo, type issue, copy ID, paste back — ragequit.
Bar Ticket? Zero switch. You’re already saving. It rides that habit like a pro.
I’ve seen linters nag about TODOs for decades — JSHint in 2010, eslint-plugin-todo today. They shame, but don’t act. Bar Ticket acts. Historical parallel: remember Post-its in the ’80s? Ephemeral notes became persistent because capture was effortless. This is dev workflows’ Post-it moment — low-friction persistence turns braindumps into tickets.
Why Does Bar Ticket Fit Real Workflows?
Busy solo dev? Crushing it. Logs every “later” without breaking stride.
Team lead? Enforces accountability — no more “I forgot” excuses. Codebase tells the story.
Open source maintainer? Gold. Contributors drop TODOs; they auto-issue, triaged later.
But — skepticism check — it’s Mac-only. Linux/Vim diehards grumble. GitLab? Not yet (GitHub remote only). And what about multi-remote repos? Picks the origin, assumes that’s your jam.
Still, for Apple devs (we’re legion), it’s surgical.
The architecture shift here? Codebase as dynamic issue tracker. TODOs aren’t comments anymore — they’re proto-issues, machine-lifted to the board. Predict this: expect forks for Jira, Linear integrations. Micro-apps like this seed ambient devops, where tools vanish into habits.
Creator’s betting on workflow fit — free download, feedback begged. Smart. No VC fluff, just solves itch.
Will Bar Ticket Kill TODO Hell Forever?
Not quite. Humans hoard. But it crushes the 90% drop-off stat cold.
Edge cases? Nested TODOs, false positives (//TODAY: meeting). Regex tweaks incoming, probably.
Unique insight: this exposes TODOs as anti-pattern signals. If you’re TODO-ing constantly, refactor upstream. Bar Ticket doesn’t fix bad design — it surfaces it, issues piling like tech debt meters.
Teams could dashboard these: “42 open TODO-issues this sprint.” Metrics from markup. Wild.
Download it. Test on a side project. See your TODO graveyard resurrect.
🧬 Related Insights
- Read more: Sourcery vs. mypy: Why AI Refactoring Beats Type Checking Alone for Python Teams
- Read more: What If Your Next Customer Call Was Handled by an AI That Sounds More Human Than Your Best Rep?
Frequently Asked Questions
What is Bar Ticket Mac app?
Bar Ticket is a free macOS menu bar tool that auto-creates GitHub issues from //TODO comments when you save files.
How does Bar Ticket work with GitHub?
It reads your git config for the repo remote, uses GitHub API to create issues, and links back to the code comment.
Does Bar Ticket support all code editors?
Yes, any editor that saves to disk: VS Code, Xcode, Vim, etc. No plugins required.
