Does it use the docs in the repository or only the code?
Show HN: I built an AI that turns GitHub codebases into easy tutorials
51–60 of 181 posts
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#52This is really cool and very practical. definitely will try it out for some projects soon.
Can see some finetuning after generation being required, but assuming you know your own codebase that's not an issue anyway.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#53Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#54Earlier quoted context omitted.
Nobody said AI isn’t useful. The hype is that AI isn’t a tool but the developer.
Nobody? https://news.ycombinator.com/item?id=41542497
Doesn’t claim it isn’t useful just it’s not as useful as they thought.
For instance to me AI is useful because I don’t have to write boilerplate code but that’s rarely the case. For other things it still useful to write code but I am not faster because the time I save writing the code I need to fix the prompt, audit and fix the code.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#55Earlier quoted context omitted.
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
From flow.py 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…
This has given me decent success:
"Write simple, rigorous statements, starting from first principles, and making sure to take things to their logical conclusion. Write in straightforward prose, no bullet points and summaries. Avoid truisms and overly high-level statements. (Optionally) Assume that the reader {now put your original prompt whatever you had e.g 5 yo}"
Sometimes I write a few more lines with the same meaning as above, and sometimes less, they all work more or less OK. Randomly I get better results sometimes with small tweaks but nothing to make a pattern out of -- a useless endeavour anyway since these models change in minute ways every release, and in neural nets the blast radius of a small change is huge.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#56Interesting..would you like to share some technical details? it did not seem you have used RAG here?
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#57That's a game changer for a new Open source contributor's onboarding. Put in postgres or redis codebase, get a good understanding and get going to contribute.
Isn't that overly optimistic? The postgres source code is really complex, and reading a dummy tutorial isn't going to make you a database engine ninja. If a simple tutorial can, imagine what a book on the topic could do.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#58Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#59Did you measure how much it cost to run it against your examples? Trying to gauge how much it would cost to run this against my repos.
Re: Show HN: I built an AI that turns GitHub codebases into easy tutorials
#60You didn't "build an AI". It's more like you wrote a prompt.
I wonder why all examples are from projects with great docs already so it doesn't even need to read the actual code.