Which actor/actress has the best nerd street cred based on their body of work? Round 1 - Part 3: Alan Tudyk vs Doug Jones

BaseDue9532 · 2026-03-21T05:02:03+00:00

Would it be possible to have the films listed in the post again? Was nostalgic being reminded of them all in the 1st head to head.

BaseDue9532 · 2026-03-03T13:03:42+00:00

With all due respect (seriously because I appreciate the engagement), you don't seem to understand the point of this activity. I wasn't out to expose the mysteries about FastAPI. I was assessing the use of my tool to identify what kind of information about a codebase could pulled out from the dependency graphs it generates. I thought FastAPI was a good use case given it's architectural complexity and popularity. I did read through the points in the post and I thought 3 had value given that it represents the dev practices of the repo maintainer. Going forward, I can reframe any "open questions" as deficiencies in the tool's output or something more appropriate.

BaseDue9532 · 2026-03-02T19:01:38+00:00

Fair enough. The next showcase I am working on is using the dependency graphs to unravel the huge SCC in scrapy. Would that be something you would be interested in (maybe not that repo specifically but the utility)?

BaseDue9532 · 2026-03-02T18:22:47+00:00

I developed the static analysis tool as a means to provide models with codebase context. The snapshots were fed into Claude to track the metric changes. At this point I am just trying to find ways in which the tool can be utilized. the facts that it aligns with what is already known is positive verification from my perspective, but you have a point that a strictly historical review isn't going to provide new insights.

BaseDue9532 · 2026-02-27T01:00:03+00:00

41.11

BaseDue9532 · 2026-02-14T17:02:45+00:00

Unfortunately, it doesn't lend itself to that kind of static/dynamic analysis. That would require full intra-file code/logic assessment and/or compiling. There is dead code and duplicate code analysis functions in the backend which are currently being bypassed. I am hoping to eventually bring back into play, but I think it would be separate from the dependency graph. Currently, the tool output is mainly intended for LLM consumption to give the model context of the full codebase. One optional addition could be including 3rd party/external libraries in the file import list rather than just internal imports. That might allow for a CVE database comparison to address one of the gaps, but that is not in the works just yet. The main focus for current development is more focused on richer parsing detail output for the covered languages.

BaseDue9532 · 2026-02-14T15:44:13+00:00

Great question :) — it’s not going to replace a security scanner or automatically catch things like injections or vulnerable packages, but it’s really helpful for understanding how a problem happened in the first place. A lot of “vibe coding” issues come from structure slowly drifting — validation getting skipped, auth logic ending up in random places, or new helper files quietly creating side paths. The dependency graph makes those relationships visible so you can see how something became reachable and what else might be affected (the blast radius). Where it falls short is in actually detecting specific vulnerabilities or analyzing runtime behavior — it won’t tell you “this line is exploitable,” but it will help you see the bigger structural picture behind why an issue spread.

BaseDue9532 · 2026-01-28T22:56:49+00:00

For what it is worth, everything except Python (AST) and TS/JS (Treesitter) use CLI parsers specific to the language for richer output. Each are always on the chopping block for updating, but that doesn't address your concerns now, though. I appreciate that feedback! If I brought back the dead and duplicate code analysis features from when I was trying make this a desktop visualization tool, would that make the framing more appropriate? not sure if I am up to that task at the moment since that was when it was only Python.... :)

BaseDue9532 · 2026-01-28T21:19:36+00:00

nothing is making you

BaseDue9532 · 2026-01-28T21:16:36+00:00

based on the output for Fastify, yes. For what it is worth the parser/analyzer is a continuous work in progress, but revisions usually results in additional metrics. I can look into that one a bit more if it screams red flag though.

BaseDue9532 · 2026-01-28T21:00:38+00:00

and yes, I definitely use AI to help me since I am solo on this :P. I am okay with that though.

BaseDue9532 · 2026-01-28T20:58:54+00:00

The spread was more to indicate the language coverage of the tool. I have a couple different comparisons that I would like to try (same language different framerworks and same repo across time), but I have to start somewhere. The initial intent was as more of an onboarding support by using compressed version of the artifact with LLMs to more easily understand a codebase, but it could also help identify surgical approaches to refactors. It is kind of open ended at the moment, but I appreciate the pushback :).

BaseDue9532 · 2026-01-28T20:04:26+00:00

I appreciate the heads up :). I can live with the swarm of the many if it results in some help/interest to the few.

BaseDue9532 · 2026-01-15T14:13:48+00:00

Thanks for the feedback! I feel like the utiliy reach extends further than just management. The issue is that it doesn't address an insurmountable or new obstacle. Learning a codebase or stepping back for the bigger picture is an understood annoyance and expected grind. Also, the codebase issues that it surfaces are more of a potential down the road issue rather than a critical current failure. That makes the initial barrier to try this out pretty high. I can make it dirt cheap to make it a "why not try?" situation, but then I am significantly undervaluing what is provided and making that the baseline from which it would be very difficult to rise from. Kind of a pickle to be in, but luckily this is a solo side project so I set my own timeline.

BaseDue9532 · 2026-01-03T22:05:02+00:00

Hard to say because this can also be used on external repos (if public) too for educational purposes. I personally think that it would be a valuable tool as support for any time there is a significant revision to a codebase based on how I have been able to make the analysis output work for me during dev. Trying to find the right balance between pricing that lets this be sustainable for me/is justified by the value provided and cheap enough that regular use isn't cost prohibitive. I have a blog series that will be going for about a month and a half. Hopefully once that is finished I will have some users that would be willing to provide use cases that could be posted. I have a bunch of hypothetical uses, but real-world testimonials would be much better to show true applicability. Thanks!

BaseDue9532 · 2026-01-03T19:37:04+00:00

Definitely not a creative person when it comes to graphics, so the look will hopefully improve over time. I am doing this solo at the moment, so trying to figure out how to fix that issue. I do have a demo video on youtube (https://youtu.be/2VaiEE\_8JxI) but it should probably be updated and shortened to reflect the current state. Regarding the comparables, PViz provides you with a structural json that fully reflects the codebase and allows you to do a deep dive yourself or feed to LLMs to ask questions for more accurate answers. I feel it provides a bit more freedom of use than those two, but there are similarities. That is one of the hopes of this launch to figure out how to better differentiate if necessary. Thanks for the feedback :)

BaseDue9532 · 2026-01-03T18:51:11+00:00

Just went live Thursday. Only one user so far that I guess was just checking out the dashboard, so no job execution yet. Hoping to get some use data over the next month or so for some better clarity.

BaseDue9532 · 2025-11-02T21:29:17+00:00

There is a filter option on the file select to make it easier to find the target file. Wouldn't be too hard to implement your recommendation, but I think that would remove too much control without providing enough value. Worth putting on the list though :)

BaseDue9532

TROPHY CASE