shivang2607

TO be honest, I dont think I will pay for this, though revenue can still come through Ads

That's so cool, building something consistently for 10 years is no small feat. How did AI helped you, or How did AI impacted your day to day work in recent years ?

so wholesome <3

I am building Cloud based context compiler and intelligent codebase visualizer for Developers and AI Agents, for easy PR review, onboarding and easy architectural understanding

https://github.com/devlensio/devlensOSS

Location: India Remote: Yes, anywhere Willing to Relocate: Yes, to Bangalore Technologies: javascript, typescript, Nextjs, Nodejs, Supabase, SQL, AI Agents, Vector Databases Resume: https://drive.google.com/file/d/1n-3chCNz61LyMl1Hju13DrzE8bA... Email: shivangkh26@gmail.com

I am building and Intelligent Codebase System for AI agents and Developers: https://github.com/devlensio/devlensOSS

Currently working on Intelligent Codebase Visualizer for reactjs/Nextjs/js and ts Codebases for easy PR review, easy onboarding and easy PR review.

Github: https://github.com/devlensio/devlensOSS https://devlens.io

I am building an open source codebase vissualizer for devs and AI agents(to provide graphical context to them) with features like impact analysis, blas radius, PR review etc.

It is open source: https://github.com/devlensio/devlensOSS ; https://devlens.io

I think people have started to liek TUI applications since Harnesses have started working through the terminal

I am working on devlens.io , It automatically maps your codebase dependencies and drops precise structural insights directly into your GitHub PRs. No hallucinations, just hard context.

It is an open-source project and I will introduce soon its mcp/cli counterpart so that graphical context and sumaries can be given to LLMs/Agents directly through the mcp integration.

https://github.com/devlensio/devlensOSS https://devlens.io

Maybe, in your experience, but I have tried both claude and codex and the code quality that claude produces is still superior in my experience, maybe its because of the nature of app I am building

In my personal experience, no model comes close to claude when it comes to coding performance. It does not matter what any of the benchmarks says.

Having said that I really hope this model of deepseek, performs significantly on par with the claude saunnet model.

Currently Working on https://devlens.io which is an Open source Intelligent Codebase Visualizer for javascript, Reactjs, nextjs and nodejs for easy onboarding and easy PR review. The open source version is live at https://github.com/devlensio/devlensOSS

You can star the repo if you like the project. I am still working on cloud version which will have lots of features.

Also the main MOAT of Devlens is not the visualizer but the blast radius feature. Which essentially tells you if I change this file/function where it will affect my Codebase which is specially useful for PR review.

Also the main MOAT of Devlens is not the visualizer but the blast radius feature. Which essentially tells you if I change this file/function where it will affect my Codebase which is specially useful for PR review.

Currently Working on https://devlens.io which is an Open source Intelligent Codebase Visualizer for javascript, Reactjs, nextjs and nodejs for easy onboarding and easy PR review.

The open source version is live at https://github.com/devlensio/devlensOSS

You can star the repo if you like the project. I am still working on cloud version which will have lots of features.

While working with larger React / Next.js codebases, I noticed a lot of PR review time goes into understanding the impact of a change rather than the change itself. Things like:

what depends on this? what else could this affect? how far does this propagate?

usually require a lot of manual tracing across files and components.

So I started building Devlens — a tool that visualizes the codebase as a graph and shows the “blast radius” of components/changes to help with PR reviews, onboarding, and understanding unfamiliar parts of a system.

Curious whether teams here would actually find something like this useful in real workflows, or if this mostly gets solved through experience and familiarity with the codebase over time.

Website: https://devlens.io GitHub: https://github.com/devlensio/devlensOSS

While working with larger React / Next.js codebases, I noticed a lot of PR review time goes into understanding the impact of a change rather than the change itself.

Things like:

what depends on this? what else could this affect? how far does this propagate?

usually require a lot of manual tracing across files and components.

So I started building Devlens — a tool that visualizes the codebase as a graph and shows the “blast radius” of components/changes to help with PR reviews, onboarding, and understanding unfamiliar parts of a system.

Curious whether teams here would actually find something like this useful in real workflows, or if this mostly gets solved through experience and familiarity with the codebase over time.

Website: https://devlens.io GitHub: https://github.com/devlensio/devlensOSS

Something which is really technical, and complex enough that not many people can do that. And ofc it should earn be handsome money :)

Been working on a tool called Devlens.

It visualizes React / Next.js codebases as an interactive graph so you can understand how features and components connect without manually tracing files.

Main focus right now is helping with:

PR reviews (understanding blast radius / impact of changes) onboarding to large codebases understanding unfamiliar parts of a system faster

Also experimenting with summaries + security analysis directly on components.

Still early, but it’s been pretty useful for me so far.

https://devlens.io https://github.com/devlensio/devlensOSS

Getting too much dependent on LLMs will eventually rust out my brain. I started notificing using tools like claude code and cursor, is ontroducing blackbox around architecture around my own Codebase. And I literally hated it when someone dont understand their own codebase

I like the Irony with the Names

what do you mean by "still" ? Did people even used it ?

Yes, But with the surging supply you have to come in at least top 20% of the developers to earn Good.

Everyone has noticed this now.

If you are building something which can be vibe-coded easily then it ofc people will create it. You can copyright a product but you can't copyright an Idea.

Selling things online was an idea by Amazon, now everyone sells online.

If you really want people not to copy your idea then make something which cannot be easily vibe-coded or copied easily i.e. which require serious skills.

I will choose Dark Knight

Cool Project. Was Wondering If you can convert this into more sophisticated thing. Like comparing different planets on different celestial Bodies with some interesting facts, and numbers. Really nice project whatsoever.

I am in same boat as well. What I learned from my experience and others' experience after talking to them is that

1. You need to focus on the problems that really do exist and for which people might willing to pay for.

2. Marketing and Distribution skills are more Important than your Engineering skills.

3. Good Things take time, if your product is useful and good as well, then it is just a matter of time and marketing. Eventually it will gain traction, so don't loose hope.

I can relate with Claude getting stuck for minutes for minute tasks as well. I should give Codex a try now then. Thanks

In terms of Code quality and UI too ?

Actually I use LLM mostly for the code quality and not for the architectural/logical or design decisions.

I am using claude solely because it's best in terms of Code quality and UI.

According to you do you think codex has surpassed or at least came on par with the claude in terms of code quality and UI ?

How good is codex in terms of code context ?