BLOG / ENGINEERING
Engineering
Technical deep dives into dependency graphs, semantic search, and architecture
The dead-code detector we shipped with Pagerank and git history
Code hotspot detection as ranking, not a linter: Pagerank plus git history sorted quiet files from risky ones, so you can ignore the right 3.
Architectural Decision Records: Capture Why Your Code Is the Way It Is
Every seasoned engineer has experienced the 'archaeology phase' of a project. You’re looking at a specific abstraction—perhaps a custom implementation of a m...
Building a Dependency Graph for Any Codebase (Python, TS, Go, Rust, Java)
Every software engineer has experienced the 'wall of code' phenomenon. You join a new project, clone the repository, and find yourself staring at 100,000 lin...
How We Built repowise: Architecture of a Codebase Intelligence Platform
Most software engineers spend upwards of 70% of their time reading code rather than writing it. Yet, the tools we use to navigate these complex systems have ...
Self-Hosting a Codebase Intelligence Platform with Docker
As engineering teams scale, the primary bottleneck isn't usually writing code—it's understanding it. Between technical debt, architectural drift, and the 'bu...
Semantic Search Over Your Codebase: LanceDB + pgvector in Practice
Every developer has experienced the 'grep fatigue.' You’re navigating a 100k+ LOC codebase, trying to find where a specific business logic—say, the grace per...