I would find this more interesting if it made tutorials out if the Linux, LLVM, OpenZFS and FreeBSD codebases.
The Linux repository has ~50M tokens, which goes beyond the 1M token limit for Gemini 2.5 Pro. I think there are two paths forward: (1) decompose the repository into smaller parts (e.g., kernel, shell, file system, etc.), or (2) wait for larger-context models with a 50M+ input limit.
Show HN: I built an AI that turns GitHub codebases into easy tutorials
41–50 of 181 posts
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#42Earlier quoted context omitted.
Exactly, kudos to the author because AI didn’t came up with that. But that’s what they sell, that AI could do what the author did with AI. The question is, is it worth to put all that money and energy in AI. MS sacrificed its CO2 goals for email summaries and better autocomplete not to mention all the useless things we do with AI
> But that’s what they sell, that AI could do what the author did with AI. Can you give an example of what you meant here? The author did use AI. What does "AI coming up with that" mean?
In the few years we will see complaints that it’s not AI that built a power station and a datacenter, so it doesn’t count as well.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#43Put in postgres or redis codebase, get a good understanding and get going to contribute.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#44Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#45I built browser use. Dayum, the results for our lib are really impressive, you didn’t touch outputs at all? One problem we have is maintaining the docs with current codebase (code examples break sometimes). Wonder if I could use parts of Pocket to help with that.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#46With the rise of AI understanding software will become relatively easy
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#47Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#48Earlier quoted context omitted.
Exactly, kudos to the author because AI didn’t came up with that. But that’s what they sell, that AI could do what the author did with AI. The question is, is it worth to put all that money and energy in AI. MS sacrificed its CO2 goals for email summaries and better autocomplete not to mention all the useless things we do with AI
> But that’s what they sell, that AI could do what the author did with AI. Can you give an example of what you meant here? The author did use AI. What does "AI coming up with that" mean?
The AI companies sell it like the AI could do it by itself and developers are obsolete but in reality it‘s a tool that still needs developers to make something useful
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#49Earlier quoted context omitted.
> But that’s what they sell, that AI could do what the author did with AI. Can you give an example of what you meant here? The author did use AI. What does "AI coming up with that" mean?
GP commenter complains that it’s not AI that came up with an idea and implemented it, but a human did. In the few years we will see complaints that it’s not AI that built a power station and a datacenter, so it doesn’t count as well.
They push AI into everything like it’s the ultimate solution but it is not instead is has serious limitations.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#50This is actually really cool. I just tried it out using an AI studio API key and was pretty impressed. One issue I noticed was that the output was a little too much "for dummies". Spending paragraphs to explain what an API is through restaurant analogies is a little unnecessary. And then followed up with more paragraphs on what GraphQL is. Every chapter seems to suffer from this. The generated documentation seems mor…
exactly it is. I'd rather impressive but at the same time the audience is always going to be engineers, so perhaps it can be curated to still be technical to a degree? I can't imagine a scenario where I have to explain to the VP my ETL pipeline
Ensure the tone is welcoming and easy for a newcomer to understand{tone_note}.
- Output only the Markdown content for this chapter.
Now, directly provide a super beginner-friendly Markdown output (DON'T need ```markdown``` tags)
So just a change here might do the trick if you’re interested.
But I wonder how Gemini would manage different levels. From my take (mostly edtech and not in English) it’s really hard to tone the answer properly and not just have a black and white (5 year old vs expert talk) answer. Anyone has advice on that?