Boris Cherny created Claude Code. When he shared how he actually uses it day-to-day, the setup was surprisingly simple. I went through every tip, tried most of them, and have opinions about all of them. The original thread is on Boris’s X account. A good companion site is howborisusesclaudecode.com which compiles everything in one place.
Obsidian + Claude Code is everywhere right now. But pointing an AI at a folder of markdown files and hoping for the best doesn’t work. What matters is how you structure the knowledge base. Get that right, and Claude becomes genuinely useful. Get it wrong, and you get confident garbage. There’s been a wave of posts about this combo lately: James Bedford’s full walkthrough, Greg Isenberg’s “personal OS” approach, kepano (Obsidian’s CEO) sharing Claude Skills. They’re all worth reading.
Your development environment should feel like one cohesive tool, not a collection of unrelated windows with clashing colors. I theme everything with the same palette — Catppuccin Mocha
After years of refining my terminal workflow, I’ve landed on a stack I genuinely enjoy using every day: Ghostty as the terminal emulator, tmux with sesh for session management, and Neovim with LazyVim for editing. Everything runs on macOS (Apple Silicon) with a consistent Catppuccin Mocha theme across all tools.
I’ve been gradually replacing classic Unix tools with modern alternatives, mostly written in Rust . After a year of daily use, these aren’t experiments anymore — they’re muscle memory.