Background
I'm a test engineer. My day job involves writing test cases, chasing down bugs, and building the tooling that makes QA faster—scripts, automation, dashboards. Over the past couple of years, AI tools (Claude Code in particular) became a real part of how I work, not just an experiment.
The projects I've used AI tools on range from scraping and analysis scripts, to full websites, to a quantitative trading system with backtesting and live execution. That breadth is why I started AI Nav: I kept running into the same problem of not knowing which open-source tool to use for a given job, and spending too long reading README files that told me nothing useful about real-world behavior.
Tools I Actually Use
What I Write About
The guides and tool reviews on AI Nav come from real usage patterns. When I write that a tool is hard to set up, it's because I hit that friction. When I recommend one tool over another for a specific use case, it's based on having tried both for that case.
I don't have opinions on every tool in the directory—there are 300+ of them and I haven't used most of them directly. For tools I haven't run myself, the assessments are based on documentation quality, GitHub issue patterns, and community feedback. I try to be clear about that distinction in what I write.
Articles by Nolan
Found an error or want to suggest a tool? Email yuzc017@gmail.com or open an issue on GitHub.