BlogViral

Show HN: Bird, a CLI for Tired Brains https://ift.tt/FS4HZVB April 18, 2026 at 12:13AM

Show HN: PanicLock – Close your MacBook lid disable TouchID –> password unlock https://ift.tt/LZFdG8k April 17, 2026 at 11:38PM

Show HN: Stage – Putting humans back in control of code review Hey HN! We're Charles and Dean, and we're building Stage: a code review tool that guides you through reading a PR step by step, instead of piecing together a giant diff. Here's a demo video: https://ift.tt/anDedrW . You can play around with some example PRs here: https://ift.tt/OHvftMp . Teams are moving faster than ever with AI these days, but more and more engineers are merging changes that they don't really understand. The bottleneck isn't writing code anymore, it's reviewing it. We're two engineers who got frustrated with GitHub's UI for code review. As coding agents took off, we saw our PR backlog pile up faster than we could handle. Not only that, the PRs themselves were getting larger and harder to understand, and we found ourselves spending most of our time trying to build a mental model of what a PR was actually doing. We built Stage to make reviewing a PR feel more like reading chap...

Show HN: Arrow. Point your phone, walk where it says, find out where https://kouh.me/arrow April 16, 2026 at 11:36PM

Show HN: I built a music theory course with games and spaced repetition I’ve spent a year building a theory learning path that starts from scratch and goes all the way up to topics like Secondary Dominants and Borrowed Chords. It uses a combination of games, interactive lessons and spaced repetition to help you understand and remember concepts. Not just learn something new and forget it in a few days. I’m trying to figure out: 1. Is the progression logical? 2. What am I missing that you’d like to see in there? 3. Where does it get confusing and could use more clarification? https://ift.tt/X0dpWjt April 16, 2026 at 10:29PM

Show HN: CodeBurn – Analyze Claude Code token usage by task Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens. Tools like ccusage give a cost breakdown per model and per day, but I wanted to understand usage at the task level. CodeBurn reads the JSONL session transcripts that Claude Code stores locally (~/.claude/projects/) and classifies each turn into 13 categories based on tool usage patterns (no LLM calls involved). One surprising result: about 56% of my spend was on conversation turns with no tool usage. Actual coding (edits/writes) was only ~21%. The interface is an interactive terminal UI built with Ink (React for terminals), with gradient bar charts, responsive panels, and keyboard navigation. There’s also a SwiftBar menu bar integration for macOS. Happy to hear feedback or ideas. https://ift.tt/x2bXt6I April 14, 2026 at 05:57AM