I’m Jared Rickert, a software engineer focused on knowledge management systems and systems design. I build tools that help humans and AI agents organize, connect, and retrieve knowledge — and I design the scalable architectures that make it all work.
What I Work On
- Knowledge Systems: Building tapper and the KEG (Knowledge Exchange Graph) ecosystem — structured knowledge graphs that serve as memory for both humans and AI agents
- Systems Design: Designing scalable, maintainable architectures using patterns like type-erasure dispatch, capability-based APIs, and layered systems
- Full Stack Engineering: Go, TypeScript, React, PHP, Docker — building web applications and the infrastructure behind them
- AI Integration: MCP servers, CLI agent skills, and cross-session memory systems that give AI agents persistent, queryable knowledge
Featured Work
Check out my projects to see knowledge graph tools and developer infrastructure I’ve built, or read my blog for posts on systems design patterns and knowledge architecture.
Let’s Connect
Ready to work together? Get in touch.
Latest Blog Posts
Type-Erasure Dispatch Pattern in Go
Use type-erasure dispatch to run one orchestration workflow across many concrete types in Go without hard-coded type switches.
What Is a KEG? How I Built My Own Knowledge Graph
The story behind Knowledge Exchange Graphs — how frustration with lost notes, clunky apps, and linear filing systems led me to build a graph-based knowledge system that now doubles as memory for AI agents.
Welcome to My Blog
An introduction to my portfolio, sharing thoughts on software development, Go programming, and building things on the web.
The Vendor Pattern with Composer: When and Why to Commit Dependencies
Explore the vendor pattern in Composer—committing dependencies to your repository instead of fetching them dynamically. Learn the tradeoffs and when this approach makes sense.