My practical, reproducible workflow for finding exposed secrets in GitHub repos using trufflehog, gitleaks, and Neovim — with CSV output for reporting.
Hunting Exposed Secrets in GitHub: My Neovim-Powered Workflow Finding secrets in source code is one of those tasks that sounds simple but has enough edge cases and tooling decisions to consume an enti...
The myth of the one true editor, when Neovim shines vs when JetBrains is the right call, dotfiles culture, and how to build a workflow that uses the best of both.
Editors: Why I Use Both Neovim AND JetBrains (And Why That's Not a Contradiction) Let me get the tribal war out of the way early: I use Neovim. I also use JetBrains IDEs. I have no internal conflict a...
Your hands touch the keyboard thousands of times a day — investing in that skill compounds over a career. Touch typing, vim motions, mechanical keyboards, ergonomics, and the resources that actually helped.
Get Better at the Keyboard: The Investment That Compounds Every Day Here's a rough calculation: if you type for 6 hours a day, 5 days a week, 48 weeks a year, you're at the keyboard for around 1,440 h...
Stop forcing one tool to do everything. Real examples of when using the wrong tool cost hours, and a framework for choosing tools based on the problem rather than tribal loyalty.
Use the Right Tool for the Job: Stop Forcing One Tool to Do Everything I once spent three hours trying to manage a complex project in Obsidian before admitting I needed a proper project management too...
A walk through my personal knowledge management system using Obsidian, Readwise, Reader, Todoist, and Neovim — how information flows from capture to creation.
Your PKM Workflow: How I Actually Manage Knowledge Without Losing My Mind I used to be that person with 47 open browser tabs, a notes app full of half-finished thoughts, and a mental model of "I'll re...