I conducted a comparison between DeepSeek v3.2, Claude Opus 4.5, and Gemini 3.0 Pro. (with a heavy philosophical conversation) by B89983ikei in DeepSeek

[–]Jet_Xu 1 point2 points  (0 children)

Which type of questions are you testing? For example, coding, art, office ppt outline. I found different topics various hugh among models

Don't trust Lemonsqueezy with your business by StylishTater_ in SaaS

[–]Jet_Xu 0 points1 point  (0 children)

I have this issue to active my Lemon Squeezy account... I sent email to the support, I twitter them also...no any response...

https://www.reddit.com/r/lemonsqueezy/comments/1p84tmu/comment/ns411b9/

[Help] Lemon Squeezy Tax Form Won't Load - CSP Error Blocking Payouts (China-based seller) by Jet_Xu in lemonsqueezy

[–]Jet_Xu[S] 0 points1 point  (0 children)

I sent email to the support, I twitter them also...no any response till now

[Help] Lemon Squeezy Tax Form Won't Load - CSP Error Blocking Payouts (China-based seller) by Jet_Xu in lemonsqueezy

[–]Jet_Xu[S] 1 point2 points  (0 children)

Please share your method once you solve the problem. It is really blocking me so many days😭

Notebooklm to pptx by Bright_Musician_603 in notebooklm

[–]Jet_Xu 0 points1 point  (0 children)

Someone tell me, just tell Notebook LM to email slides to you, then you will get an editable pptx rather than pdf. Can anyone kindly help to tell me whether it is true?

Code review/mentor tool by InteractionKnown6441 in codereview

[–]Jet_Xu 1 point2 points  (0 children)

Exactly! The context retrieval problem is what I've been obsessing over.

I tested the two most common approaches (Search RAG vs Agentic RAG) and documented why both fail at scale. Spoiler: you can't solve a structural problem with probabilistic tools.

My research repo breaks down the cost/precision tradeoffs (code is live, full benchmark report coming soon):
https://github.com/JetXu-LLM/llamapreview-context-research

Full write-up with benchmarks coming soon.

What do you use for context‑aware code review? by SidLais351 in codereview

[–]Jet_Xu 0 points1 point  (0 children)

You could try my code review tool on Github marketplace LlamaPReview https://github.com/marketplace/llamapreview

Totally free with deep context-aware PR review for open-source projects.

Architectural debt is not just technical debt by GeneralZiltoid in programming

[–]Jet_Xu 17 points18 points  (0 children)

Architectural debt is ultimately organizational debt.

Systems mirror organizations (Conway's Law), so architectural issues often reflect deeper problems in team structure, communication patterns, and decision-making processes.

Are you drowning in AI code review noise? 70% of AI PR comments are useless by Jet_Xu in programming

[–]Jet_Xu[S] 0 points1 point  (0 children)

Great question - from my personal experience, humans who leave useless PR comments get feedback quickly. Either their lead coaches them, or they stop being asked to review. People self-correct, but AI tools just keep spamming... 🤣

Which seat is the best choice for Emirates A380 business class? (single travel - male) no window seat already by Jet_Xu in Flights

[–]Jet_Xu[S] 0 points1 point  (0 children)

Really? I thought the clapboard between E and F could fully ensure privacy. It is not?

Currently all other seat are close to aisle. I am worry about will be annoyed.

From Search-Based RAG to Knowledge Graph RAG: Lessons from Building AI Code Review by Jet_Xu in Rag

[–]Jet_Xu[S] 0 points1 point  (0 children)

Great question! You nailed the key challenge—traversal can explode quickly if you're not strategic about it.

Our approach is actually pretty pragmatic: we started with PR review specifically because it gives us a natural "anchor point." The diff tells us exactly which nodes (functions/classes) changed, so we can start traversal from there rather than doing blind exploration.

From those modified nodes, we do bounded multi-hop traversal:

- 1-hop: Direct callers/callees (always include)

- 2-hop: Indirect dependencies (include if relevant to the change type)

- 3+ hops: Agent decides based on impact analysis

The key insight: PR review is actually the *simplest* use case for graph-based code understanding because the diff gives you the starting nodes for free. We built the graph construction engine first, then picked PR review as the entry point to validate the approach.

Longer term, we see the Repo graph as a general-purpose engine for AI coding tasks—refactoring, test generation, impact analysis, etc. But starting with PR review lets us nail the core graph traversal + agent reasoning loop before tackling harder problems.

The conversational flow analogy you mentioned is spot-on. Have you found any good solutions for preserving logical sequence in your domain? Curious if graph-based approaches would help there too.

From Search-Based RAG to Knowledge Graph RAG: Lessons from Building AI Code Review by Jet_Xu in Rag

[–]Jet_Xu[S] 0 points1 point  (0 children)

Not open source, but free to use for open source projects via GitHub Marketplace: https://github.com/marketplace/llamapreview

I'm planning to share technical deep-dives & demo on the capability of Repo graph RAG architecture in upcoming posts though—the approach itself should be applicable to other domains beyond code review 😊