I finally moved to fedora linux after using windows for 10 years. Switched because I was facing RAM management issues in my zenbook 16GB ram variant and I am genuinely impressed hw well fedora handles the RAM. Lovin it !
repost as earlier was removed by mod
I have asus zenbook p14 oled ux3405 modelz 16GB ram variant. For some reason 16GB is not enough and I observed it's not efficient either, so I am switching to linux.
I asked Hermes to scan my device and locate all the important files and folders that I need to backup like ssh files and env files etc. I used dsv4f as a model and I am shocked at how well it worked. Not only does it give me the files I asked, it also traced configurations and hidden files which I forgot. Not only that for all the packages and applications that I have installed it gave me the corresponding list of commands to run to install their linux version. An sh file too which when I will execute all the applications and packages like npm,bun other global packages will get installed.
I told my concern why I was shifting and it told me the packages I need to install in Linux like zram for my purpose.
I'm now discussing with hermes on strategy to how to make a switch efficiently and it's properly guiding me on what distro is best for this hardware, how to do partitioning and make a switch.
I personally use Hermes only for non coding tasks, even when I need to do something related to coding using Hermes I ask it to use claude code.
I believe Hermes for coding is not a good choice and opencode or claude code performs better in terms of coding plus Hermes will use lots of tokens as well.
But does anyone have observed differently ? Do you find Hermes better in coding than opencode or claude code? Does anyone use Hermes for coding ? If yes , what is your setup ? How do you manage the workflow ?
I was doing A/B testing my MCP/skills with claude and it suggested me to add an edge for Nextjs application which will connect frontend nodes to the nextjs backend api route they call.
This actually made the blast radius/impact radius feature much more complete and useful.
Interesting how I am taking feedback for skills from its actual user i.e. Claude XD
It's an Open source project by the way. https://github.com/devlensio/devlensOSS
So I have been building an open source project DevelensOSS for around 5 months. And currently I got an idea why not to give AI agents the ability to access graphical context of codebase with already embedded functional and technical summaries. This can save lots of tokens I believe.
So far I have created the MCP with many tools useful for exploring the codebase/architecture/detecting impact etc, finding node and subgraphs etc. I also build skills but I think I need to do more work on skills, mostly on teaching AI how and when to use different tools of MCP and how to figure out important things from it.
I am using claude code for A/B testing, and improving skills based on that. Once it's ready I think I will try it with non - frontier models and compare the outputs.
Will post updates here. :))
So Hear me out. Not only on almost all benchmarks is mimo v2.5 is better than dsv4f flash, but also the pricing. Most people only look at input and output cost of the model, what they ignore most of the time is the cache rate. And to my surprise mimo2.5 is 10 times cheaper than dsv4f in terms of cache tokens. And second thing is ds4f uses a lot, and I mean a LOT of tokens in reasoning, therefore checking the cached tokens price is much more reasonable.
Hey everyone,
Hitting 50+ waitlist signups in 60 days for a highly niche cloud developer tool is a massive milestone for me, especially since a basic open source version is already out there.
In the world of enterprise SaaS, 50 might sound small. But for a highly specialized, framework-specific developer tool, it means everything. It proves that the pain point is real, the solution is needed, and the idea is officially validated.
Seeing developers choose to line up for the cloud AI features when they could just use the free local tool confirms that "Architectural Intelligence" is the future. I am absolutely fired up to build faster and ship this thing.
If you are curious what the tool is: It’s called Devlens. It’s a codebase visualizer built specifically for the JavaScript, React, and Next.js ecosystem. It uses AST parsing (no AI guesswork) to turn your repo into an exact, queryable mathematical map.
Here are the core pain points it solves:
I’d love to get this community's feedback on it!
Check it out or join the beta here: https://devlens.io/
Hey everyone,
Hitting 50+ waitlist signups in 60 days for a highly niche cloud developer tool is a massive milestone for me, especially since a basic open source version is already out there.
In the world of enterprise SaaS, 50 might sound small. But for a highly specialized, framework-specific developer tool, it means everything. It proves that the pain point is real, the solution is needed, and the idea is officially validated.
Seeing developers choose to line up for the cloud AI features when they could just use the free local tool confirms that "Architectural Intelligence" is the future. I am absolutely fired up to build faster and ship this thing.
If you are curious what the tool is: It’s called Devlens. It’s a codebase visualizer built specifically for the JavaScript, React, and Next.js ecosystem. It uses AST parsing (no AI guesswork) to turn your repo into an exact, queryable mathematical map.
Here are the core pain points it solves:
I’d love to get this community's feedback on it!
Check it out or join the beta here: https://devlens.io/
Hey everyone,
Hitting 50+ waitlist signups in 60 days for a highly niche cloud developer tool is a massive milestone for me, especially since a basic open source version is already out there.
In the world of enterprise SaaS, 50 might sound small. But for a highly specialized, framework-specific developer tool, it means everything. It proves that the pain point is real, the solution is needed, and the idea is officially validated.
Seeing developers choose to line up for the cloud AI features when they could just use the free local tool confirms that "Architectural Intelligence" is the future. I am absolutely fired up to build faster and ship this thing.
If you are curious what the tool is: It’s called Devlens. It’s a codebase visualizer built specifically for the JavaScript, React, and Next.js ecosystem. It uses AST parsing (no AI guesswork) to turn your repo into an exact, queryable mathematical map.
Here are the core pain points it solves:
I’d love to get this community's feedback on it!
Check it out or join the beta here: https://devlens.io/
Hey everyone,
Hitting 50+ waitlist signups in 60 days for a highly niche cloud developer tool is a massive milestone for me, especially since a basic open source version is already out there.
In the world of enterprise SaaS, 50 might sound small. But for a highly specialized, framework-specific developer tool, it means everything. It proves that the pain point is real, the solution is needed, and the idea is officially validated.
Seeing developers choose to line up for the cloud AI features when they could just use the free local tool confirms that "Architectural Intelligence" is the future. I am absolutely fired up to build faster and ship this thing.
If you are curious what the tool is: It’s called Devlens. It’s a codebase visualizer built specifically for the JavaScript, React, and Next.js ecosystem. It uses AST parsing (no AI guesswork) to turn your repo into an exact, queryable mathematical map.
Here are the core pain points it solves:
I’d love to get this community's feedback on it!
Check it out or join the beta here: https://devlens.io/
Github: https://github.com/devlensio/devlensOSS
Its really a big milestone for me. 50+ users have joined cloud waitlist for a niche developer tool for specific language and framework within 60 days that's also when I have an basic open source version already available.
I know 50 is not a large number but for a niche open source dev tool, it means the idea and problems both are validated and it really has scope. So now I am fired up to complete it even faster :))
​
Its really a big milestone for me. 50+ users have joined cloud waitlist for a niche developer tool(https://devlens.io/) for specific language and framework within 60 days that's also when I have an basic open source version (https://github.com/devlensio/devlensOSS) already available.
I know 50 is not a large number but for a niche open source dev tool, it means the idea and problems both are validated and it really has scope. So now I am fired up to complete it even faster :))
Its really a big milestone for me. 50+ users have joined cloud waitlist for a niche developer tool for specific language and framework within 60 days that's also when I have an basic open source version already available.
I know 50 is not a large number but for a niche open source dev tool, it means the idea and problems both are validated and it really has scope. So now I am fired up to complete it even faster :))
Its really a big milestone for me. 50+ users have joined cloud waitlist for a niche developer tool for specific language and framework within 60 days that's also when I have an basic open source version already available.
I know 50 is not a large number but for a niche open source dev tool, it means the idea and problems both are validated and it really has scope. So now I am fired up to complete it even faster :))
Its really a big milestone for me. 50+ users have joined cloud waitlist for a niche developer tool for specific language and framework within 60 days that's also when I have an basic open source version already available.
I know 50 is not a large number but for a niche open source dev tool, it means the idea and problems both are validated and it really has scope. So now I am fired up to complete it even faster :))
Its really a big milestone for me. 50+ users have joined cloud waitlist for a niche developer tool for specific language and framework within 60 days that's also when I have an basic open source version already available.
I know 50 is not a large number but for a niche open source dev tool, it means the idea and problems both are validated and it really has scope. So now I am fired up to complete it even faster :))
Hey everyone,
I’ve been working on something called Devlens — a tool to visualize React / Next.js codebases as an interactive graph.
Built this mainly because PR reviews and onboarding were getting annoying…
had to jump across a bunch of files just to understand how things connect and what might break.
With this, you can open a route or component and:
see dependencies both ways
understand how a feature is structured
check the blast radius before changing something
Also added summaries + basic security analysis so you get context quickly.
There’s a short demo video below that explains it better.
Still early — would love some honest feedback.
Hey everyone,
I’ve been working on something called Devlens — a tool to visualize React / Next.js codebases as an interactive graph.
Built this mainly because PR reviews and onboarding were getting annoying…
had to jump across a bunch of files just to understand how things connect and what might break.
With this, you can open a route or component and:
see dependencies both ways
understand how a feature is structured
check the blast radius before changing something
Also added summaries + basic security analysis so you get context quickly.
There’s a short demo below that explains it better.
Still early, though the open source version is out I am still working on the cloud version which will have many more features. would love some honest feedback.
I kept running into this problem while working on larger codebases:
I’d make a small change in one file… and somehow break something completely unrelated.
It’s surprisingly hard to answer:
“what else does this piece of code affect?”
So I built an open source tool called Devlens.
It analyzes a codebase and builds a dependency graph, so when you select a file, it shows all the other parts that might be impacted (kind of like a “blast radius” for code changes).
Right now it:
\- works for javascript, Reactjs, nodejs, nextjs
\- can generate summaries for each node efficiently explaining what a node does and how
\- Security analysis of your codebase
\- maps dependencies between functions and different types components
\- highlights impacted areas when you select something
\- helps navigate unfamiliar codebases a bit faster
Would love to know:
\- does this feel like a real problem to you?
\- how do you usually figure out impact before making changes?
Project:
https://github.com/devlensio/devlensOSS
Website:
Demo: