A practical guide to using the PARA framework (Projects, Areas, Resources, Archive) to create consistency across all your tools and platforms. The focus is on organizational structure over tool features, showing how the same four folders work in email, notes, and file systems to eliminate the constant question of where you put something.
A practical approach to getting thoughts out of your head and into systems you're forced to look at. Emphasizes treating yourself like your own customer with SLAs, capturing immediately, and actually processing what you capture. The goal: peace of mind and confidence nothing falls through the cracks.
How I automated PR reviews with Claude Code using a simple markdown file. Enforces team standards, catches obvious issues, keeps humans in the loop.
Em dash and spaced en dash, RIP. 1800-2020s
This is why I structure stored procedures with temp tables instead of variables. It's not about performance. It's not about best practices. It's about getting out of the office on time.
I asked ChatGPT about a video game with 23 years of fan documentation. It got basic facts wrong. Then I asked two AI models to audit my own LinkedIn profile—and they both confidently told me my job title was wrong. The problem isn't AI. It's how we're using it.
I went from building dashboards to leading teams. From Tableau Server administration to architecting data platforms. From asking "what chart should this be?" to asking "what problem are you trying to solve?"