Repo Tutor Turns Public GitHub Codebases Into Guided Learning Paths

·1 views

A developer has built Repo Tutor, an open-source learning companion that helps people explore public GitHub repositories through structured lessons and quizzes. The tool analyses supported source files to identify languages, dependencies, entry points, imports, and a suggested reading order, rather than relying mainly on AI-generated summaries. Learners can answer server-scored quizzes, inspect source code, and have their progress saved locally in SQLite, with English and Hinglish options in parts of the interface. An experimental Ollama-based AI explanation layer is also included, but the developer found small local models could produce incorrect explanations and citations, so its output is not treated as fully reliable. The project does not execute repository code and has been tested on a live public repository, though broader compatibility is still being validated.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

AI Tools Ease Audit Firms' Voucher Matching, Reconciliation and Year-End Closing

Audit teams often lose much of busy season to routine tasks such as matching vouchers to ledger entries, reconciling balances, and preparing closing schedules. The author, a Lahore-based engineer, describes building AI tools for these jobs and argues they must follow strict design rules. Extracted invoice fields are checked against validation rules before reaching the ledger, and most items are cleared through exact and fuzzy matching, with the model used only for leftover cases. Every suggestion is logged with a reviewer, timestamp and source document to create an audit trail, and closing steps are tracked as tasks with automatic checks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Build a Keyboard-Driven Test Grader in Plain JavaScript

A DEV Community tutorial walks through building a test grader in a single HTML file with no dependencies. Users set the question count once, then record wrong answers with a button or keyboard key while the percentage and letter grade update instantly. The core grading logic lives in a pure function that clamps wrong-answer counts, compares scores using integer cross-multiplication to avoid floating-point errors, and sorts custom grade scales. The page also renders a table of every possible score as a quick chart. The guide additionally covers how to avoid common keyboard shortcut bugs, such as blocking single-letter hotkeys when modifier keys are held or when the user is typing in an input field.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Court Staffer Recounts Three AI Conference Talks and Her Discomfort With Public Speaking

A court professional describes how a 2025 decision to build with AI led to speaking invitations at three court conferences in Albuquerque, Los Angeles, and Riverside. She says she was the only attendee from her court at the first event, and the pressure grew with each talk, especially at the Los Angeles Superior Court, the country's largest trial court. The most recent talk, delivered at a Southern Region Finance Officers Meeting, was preceded by two months of preparation, and she rehearsed by listening to an audio version of her notes. Despite positive audience reaction, she says she felt relief rather than accomplishment once it ended.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Choosing Centralized Logging for Next.js and Node.js Startup Apps by Signal Value

The article argues that startups should pick a centralized logging service based on how many useful decisions it supports per ingested byte, rather than on the lowest advertised price. For a Node.js customer-support agent, it recommends one structured event per model call, one summary per agent run, and logging of every error. It advises starting with a managed log service behind a thin application-owned transport interface, selecting an EU deployment, and benchmarking with real traffic. Correlation is handled through trace and span identifiers following the W3C Trace Context standard, and personal ticket text is kept out of routine logs to align with GDPR data minimization. The author proposes testing candidate services by replaying an identical 1,000-event fixture and checking how much configuration is needed to answer the same operational questions.

0 comments Read more at DEV Community