Yes. Programming is not Bottlenecked by Typing Text. If yours is, you're not doing Programming. You're just Typing Text. It's not about remembering What Text to Type. It's about Understanding the Problem you are Solving.

Contrary to what everyone says, it’s more important than ever to be deeply technical…

I’m experimenting with a new kind of IDE, designed especially for people with ADHD. github.com/v-noc/IDE Instead of treating code as text files and folders, it converts code into graphs and lets you work visually. You can isolate a single function and focus on it without being

I’m experimenting with a new kind of IDE, designed especially for people with ADHD. github.com/v-noc/IDE Instead of treating code as text files and folders, it converts code into graphs and lets you work visually. You can isolate a single function and focus on it without being

I’m experimenting with a new kind of IDE, designed especially for people with ADHD. github.com/v-noc/IDE The idea is inspired by how hardware is maintained. If one component fails, you don’t analyze the entire machine. You isolate the component, test it, fix it, and put it

The default dashboard for programmers should be the IDE. With the right UX, all relevant information should live next to the code itself—not scattered across log dumps and disconnected dashboards. Why dump thousands of logs that are hard to search and harder to understand?

One of the biggest advantages of a graph‑based IDE is that files and folders are no longer isolated or fragile. They can be connected, tracked, and enriched with documentation and metadata that stay with them over time. There’s no need to put documentation in separate folders

semantic-aware version control + graph-based coding environment. Instead of tracking just files, it understands what actually changed functions, classes, conversation with agents(coming soon), and others.

semantic-aware version control + graph-based coding environment. Instead of tracking just files, it understands what actually changed functions, classes, conversation with agents(coming soon), and others.

semantic-aware version control + graph-based coding environment. Instead of tracking just files, it understands what actually changed functions, classes, conversation with agents(coming soon), and others.

I spent the whole day trying to add JavaScript and TypeScript support to github.com/v-noc/IDE. so I can explore Claude Code and test it also,

I put Claude Code into my graph-based IDE and hosted it here: vnoc.vercel.app/project/claude… You can browse the code + docs without jumping through files, focus on one function at a time, and share links to specific nodes like this: vnoc.vercel.app/project/claude… agent coming soon!

I put Claude Code into my graph-based IDE and hosted it here: vnoc.vercel.app/project/claude… can browse the code + docs without jumping through files, focus on one function at a time, and share links to specific nodes like this: vnoc.vercel.app/project/claude… agent coming soon!

I put Claude Code into my graph-based IDE and hosted it here: vnoc.vercel.app/project/claude… You can browse the code + docs without jumping through files, focus on one function at a time, and share links to specific nodes like this: vnoc.vercel.app/project/claude… agent coming soon!

I put Claude Code into my graph-based IDE and hosted it here: vnoc.vercel.app/project/claude… You can browse the code + docs without jumping through files, focus on one function at a time, and share links to specific nodes like this: vnoc.vercel.app/project/claude… agent coming soon!

Hey guys, I am experimenting on a new kinds of coding environment for humans and llms, it uses graph db, insted of files , and alone documents logs and task to be connect to the code , it's opensource vnoc.vercel.app/project/claude…, and can focus in single node vnoc.vercel.app/project/claude…

One benefit of a graph-based IDE is flexibility. You can reduce cognitive load by grouping related things together and controlling how much you see at once. On a huge codebase like Claude Code, that makes it much easier to know where to start and avoid getting lost.

I hosted the ClaudeCode codebase on V-NOC as a demo: vnoc.vercel.app/project/claude… Been exploring a different UX for navigating large codebases. I added grouping so related things can collapse into higher-level structures, which helps reduce cognitive load and control how much