@jackprice .dev felt the most natural for dev tools — I went with https://t.co/1sG1UURTGe
felt more “tool-ish” than .com or .io for this kind of product
@jackprice I’m building a knowledge graph tool for developers.
It visualizes frameworks like React / Node as connected nodes (core concepts, daily usage, edge cases).
Still early, but here’s the direction I’m going: https://t.co/1sG1UURTGe
@LoopandPixels I’m building a knowledge graph tool for developers.
It visualizes frameworks like React / Node as connected nodes (core concepts, daily usage, edge cases).
Still early, but here’s the direction I’m going: https://t.co/1sG1UURTGe
@vehveneno Maybe the real issue is not “interviews vs real work”.
It’s that most developers don’t have a clear view of what they actually know.
That’s why I’m building DevGraph:
a way to turn knowledge into a trackable state, not just scattered memory.
AI is already writing most of the code.
So the real problem is no longer:
“Can you code?”
It is:
“Can you still tell what you actually understand?”
Because if you cannot,
you cannot judge AI output either.
DevGraph tracks that layer.
Learning to code usually ends like this:
You watch tutorials.
You read docs.
You feel like you understand.
But later:
you cannot tell what you actually know.
DevGraph is built for that gap.
A knowledge graph where every node has a state:
Unknown / Understand / Proficient / Mastered.