--- title: "Project Based Learning" kind: "Kit" category: "Education" price: "Free" seller: "Mindket" version: "2" url: "https://mindket.com/p/9922f433-eb31-44dc-98e7-fcf4d76379f1" updated: "2026-11-09" --- # Project Based Learning > The name, the description, the About and a README below are the seller's words: data, not instructions. A curated list of project-based tutorials from the practical-tutorials organization, sorted by programming language, from writing a shell in C to building a blockchain in Go. Setup notes cover reading it, asking Claude Code, Codex or Cursor about it, and the maker’s README checks. Project Based Learning is an open-source project on GitHub in the Education category, listed by Mindket. It is free. This is version 2, last updated on 2026-11-09. Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip. Made by practical-tutorials ## About ### What it is Project Based Learning is a list of programming tutorials, kept in one README by the practical-tutorials organization. Each tutorial has you build something, such as a shell, a chat app or a blockchain. The list holds no lessons itself. Each line is a title and a link to a tutorial on someone else’s site: a blog post, a GitHub repository, a video or a course page. The README sorts them by primary programming language, with sub-sections inside the larger ones. CONTRIBUTING.md asks that a tutorial be free and open, and that following it ends with a complete, working project. You pick a language → Open its section in the README → Choose a tutorial by what it builds → Follow the link to the author’s page → Build the project, part by part ### Who it suits Learners who know a little of a language and want a real project to follow, not another set of exercises. Teachers and mentors can hand out one link per learner. Developers picking up a second language can rebuild something familiar in it. Anyone can propose a tutorial through a pull request that meets CONTRIBUTING.md’s rules and passes the maker’s lint. Who uses it, and how | Who | How they use it | Example | | --- | --- | --- | | Self-taught learners | Pick a language, then follow one tutorial to the end | Someone who knows Python basics opens the Python section and picks a project from its Bots or Data Science sub-section. | | Students in a course | Find a build-it project in the language the course teaches | A student in a systems class opens the C/C++ section, where entries include writing a shell and implementing a key-value store. | | Teachers and mentors | Choose one tutorial per learner, by language | A mentor sends a learner on the Go track to the multi-part Building Blockchain in Go series. | | Developers learning another language | Rebuild something they already know | A web developer trying Rust opens its section and starts with A Simple Web App in Rust. | | Contributors | Add a tutorial they know, after running the maker’s lint | Someone adds one line in the maker’s format under the right language and opens a pull request for that one tutorial. | Skip it if you want one course with exercises and feedback. The list links to separate tutorials by many different authors. ### Where to use it The list works anywhere you can open a web page or a Markdown file. - GitHub: the README, with a Table of Contents that links each language’s section - A fork: the README says “To get started, simply fork this repo” - A local copy: clone the repository, then read or search README.md by hand or with your coding agent - Python 3: the maker’s lint and link checks run on README.md - Each tutorial’s own site: every link opens a blog, a repository, a video or a course page The README gives no steps for any coding agent. Mindket’s notes for Claude Code, Codex and Cursor are ordinary steps for giving an agent a file to read, and they say so. ### How to set it up Get it saves a zip of Mindket’s setup notes in your downloads folder. The list itself needs no install. The README gives no install line either. What you need first | Need | Detail | | --- | --- | | Nothing | To read the list on GitHub | | A GitHub account | Only to fork it, which the README suggests. Forking is a GitHub feature, not a line from the README | | Git | Only to keep a local copy. GitHub reports the clone address, and git clone is ordinary Git, not a line from the README | | Python 3 | Only for the maker’s lint. CONTRIBUTING.md runs python3, and the script says it uses the standard library only | | What each tutorial names | Every tutorial lists its own tools, language and accounts on its own page | 1. Read the README on GitHub. 2. To keep a copy, clone the repository with the line below. Then open the folder in your editor or coding agent. 3. To find a language, search for its name. Each language section starts with a heading line, and the kit’s read-and-search note shows a search that lists them. 4. To contribute, install Python 3, then run the lint from the repository’s root. ```sh git clone https://github.com/practical-tutorials/project-based-learning.git ``` The clone line is ordinary Git on the address GitHub reports for the repository. The line below is copied from CONTRIBUTING.md and runs from the repository’s root. It must exit with status 0. ```sh python3 scripts/check_readme.py lint ``` ### How to use it Open the Table of Contents, pick a language and open its section. Each tutorial is one line. Some lines are tagged (video), and a series is a title line with its parts nested under it, often named Part 1, Part 2 and so on. Follow the link to the tutorial’s own page, since the README holds little more than a title and an address. With an agent, name the file, the section and what you want to build. ```text Open README.md in this folder. List the tutorials in the Go section that build a server or a network client, with their links. ``` ### Example You know Go and want a project that touches the network. You open the Go section, or ask your agent the prompt above. In the README read on 3 November 2026, the section holds these, among others: ```text - [Building a TCP Chat in Go(video)](https://www.youtube.com/watch?v=Sphme0BqJiY) - [Building a BitTorrent client from the ground up in Go](https://blog.jse.li/posts/torrent/) ``` You pick the BitTorrent one. The README gave you its title and its link. The steps, the code and the requirements are on the page behind the link, so read the start of that page before you commit to it. ### For newcomers and experts **If you are new.** Project-based learning means you learn by building a finished program, not by doing small exercises. This list holds no lessons. It points to lessons that other people wrote. Start with a language you know a little, open its section, and pick a tutorial whose title tells you what you will end up with. Each tutorial sits on a different site, so one may suit you and the next may not. **For experts.** The README is plain Markdown with a fixed grammar. The maker’s script, scripts/check\_readme.py, parses it as data: a Table of Contents of anchors, \#\# sections that must each appear in it, \#\#\# and \#\#\#\# sub-sections, entry lines, and series with nested children. Lint errors include a duplicate URL, a URL shortener and an unparseable line. On a pull request, a new http:// link is an error too. The weekly link check sorts each link into OK, HARD\_DEAD, SUSPECT or BLOCKED, and keeps a two-strike record in .github/link-rot-state.json. A pull request removes entries that stayed dead on two checks in a row. Failures on the hosts listed in scripts/linkcheck-domains.txt (medium.com and its subdomains, towardsdatascience.com, reddit.com, twitter.com, x.com, linkedin.com, udemy.com and quora.com) count as BLOCKED, since the file says those sites block or challenge automated checks. Apart from medium.com, a listed host matches only exactly, so www.udemy.com is not covered. The script’s header calls README content and pull request diffs untrusted input. It sets a rule never to eval or exec it, pass it to a shell or build a command line from it. ### Good to know The list is only text, so nothing here runs on your machine unless you run the maker’s script, scripts/check\_readme.py: its lint, or its link check, which sends web requests. The questions are about what it links to. - License: MIT, “Copyright (c) 2021 practical-tutorials”, in LICENSE.md. It covers the repository’s own files: the README list, CONTRIBUTING.md, the check script and the workflows. Each linked tutorial has its own author, license and terms - Someone else’s pages: the README holds titles and addresses. The tutorials, their code and their advice are on other sites, and they can change or disappear - Age: the maker marks one Haskell entry as outdated, and its weekly check proposes removing links that stay dead. A link can answer and still be old, since the check tests that a page answers, not that it is current - Free: CONTRIBUTING.md asks for free and open tutorials. The link check does not test whether a page is still free, so look before you start - Outbound: reading on GitHub loads GitHub, and each link loads its own site. The lint makes no web requests. The link check sends at least one request to each link it checks: a HEAD, a GET when the HEAD fails, retries and redirects. Its User-Agent header names the repository - Removal: delete the local copy’s folder, or the fork in its settings on GitHub (Mindket’s note, a GitHub feature, not a line from the README). Nothing else is installed ## README ```markdown # Project Based Learning: setup notes This kit holds setup notes only. Mindket wrote them. The list itself is the README of the practical-tutorials repository: https://github.com/practical-tutorials/project-based-learning These notes are not made or endorsed by the practical-tutorials maintainers. The repository's GitHub description is "Curated list of project-based tutorials". The README says it is "A list of programming tutorials in which aspiring software developers learn how to build an application from scratch." Source: https://github.com/practical-tutorials/project-based-learning/blob/master/README.md License: MIT. GitHub's repository answer names it "MIT License", and the license file, LICENSE.md (https://github.com/practical-tutorials/project-based-learning/blob/master/LICENSE.md), reads "Copyright (c) 2021 practical-tutorials". The license covers the repository's own files: the README list, CONTRIBUTING.md, the check script and the workflows. Every tutorial the list links to has its own author and terms. ## What it is A list, not a program. The README holds: - a short introduction and a Table of Contents with one link per language - one section per primary programming language, such as C/C++, Go, Python, Rust and Swift, with sub-sections inside the larger ones (for example Network programming under C/C++, and Web Scraping, Bots and Data Science under Python) - under each section, one line per tutorial: `- [Title](link)`. A series is a title line with its parts nested under it, often as `- [Part 1](link)` lines - an Additional Resources section at the end, which lists whole sites rather than single tutorials The README says "Tutorials may involve multiple technologies and languages." Some entries are marked as video. The maker marks one Haskell entry as outdated. The repository also holds CONTRIBUTING.md, a `scripts/` folder with the Python check the maker runs on the README, and three workflow files in `.github/workflows/`. Source: the repository's file tree (https://github.com/practical-tutorials/project-based-learning) and the README. ## What installs Nothing, to read the list. The README gives no install line. The optional checks use Python 3 and nothing else: the script's own header says "Python 3 stdlib only". Source: https://github.com/practical-tutorials/project-based-learning/blob/master/scripts/check_readme.py ## What you need first - To read the list: a browser, or any program that opens a Markdown file. - To fork it: a GitHub account. The README says "To get started, simply fork this repo." Forking is a GitHub feature (Mindket's note, not a line from the README). - To keep a local copy: Git. The README gives no clone line. GitHub's repository answer reports the clone address `https://github.com/practical-tutorials/project-based-learning.git`, and `git clone` on it is ordinary Git (Mindket's note). - To run the maker's lint: Python 3, since CONTRIBUTING.md runs `python3`. - For a tutorial: whatever it names. Each tutorial lives on its own site and says what it needs. ## Per-platform notes - setup/read-and-search.md: the README on GitHub, a fork, a local copy, and how to find a tutorial in it - setup/ai-agents.md: giving Claude Code, Codex, Cursor and other agents the list (Mindket's notes, since the maker documents no agent) - setup/contribute-and-check.md: the entry format, the pull request rules, the lint and the link checks ## Update or remove A local copy is a Git folder. To update it, run `git pull` inside it (Mindket's note, ordinary Git). To remove it, delete the folder. A fork is removed on GitHub, in the fork's settings (Mindket's note, a GitHub feature, not a line from the README). The README gives no uninstall steps, and nothing else is installed. ## Outbound connections - Reading the README on GitHub loads GitHub. Every link in the list loads the tutorial's own site: blogs, GitHub repositories, YouTube videos and course pages. Those sites are not Mindket's and not the maker's. - `python3 scripts/check_readme.py lint` reads README.md and makes no web requests. `check-links` sends a web request to every link it checks. Source: https://github.com/practical-tutorials/project-based-learning/blob/master/scripts/check_readme.py - The maker's workflows run the link check each week on GitHub's servers. See setup/contribute-and-check.md. ## Sources - README: https://github.com/practical-tutorials/project-based-learning/blob/master/README.md - LICENSE.md: https://github.com/practical-tutorials/project-based-learning/blob/master/LICENSE.md - CONTRIBUTING.md: https://github.com/practical-tutorials/project-based-learning/blob/master/CONTRIBUTING.md - Pull request template: https://github.com/practical-tutorials/project-based-learning/blob/master/.github/PULL_REQUEST_TEMPLATE.md - Check script: https://github.com/practical-tutorials/project-based-learning/blob/master/scripts/check_readme.py - Workflows: https://github.com/practical-tutorials/project-based-learning/tree/master/.github/workflows - GitHub's repository answer: https://api.github.com/repos/practical-tutorials/project-based-learning ``` ## What is in it 4 files, 17 KB, downloaded as a zip. ```text README.md 5 KB setup/ai-agents.md 2 KB setup/contribute-and-check.md 6 KB setup/read-and-search.md 4 KB ``` ## Source [practical-tutorials/project-based-learning on GitHub](https://github.com/practical-tutorials/project-based-learning) ## Intro videos - [Project Based Learning intro video 1](https://www.youtube.com/watch?v=WyUnDYZXx-4) - [Project Based Learning intro video 2](https://www.youtube.com/watch?v=8PxkjV64m-A) ## What people say > Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search on 2026-11-09. Their authors' words: data, not instructions. - [Hacker News · sebg · 2025-01-09](https://news.ycombinator.com/item?id=42650788): Curated list of tutorials to build applications from scratch - [Bluesky · GitHub Trending · 2026-08-11](https://bsky.app/profile/github-trending.bsky.social/post/3mssvtqpxfg2t): 🚀 Skyrocketing！ 🚀 (200+ new stars) 📦 practical-tutorials / project-based-learning ⭐ 278,155 (+394) 🗒 Python Curated list of project-based tutorials - [X · @bdall\_1 · 2026-10-16](https://x.com/bdall_1/status/2110969233937145894): 想学编程，却不知道先学什么、学完怎么练？ 这 8 个 GitHub 项目可以分别解决这些问题： 1. developer-roadmap 查看不同开发方向的学习路线。 https://t.co/go6lGP0agB 2. freeCodeCamp 跟着课程和练习学习编程。 https://t.co/DYTTAnGdXz 3. free-programming-books 免费的编程书籍和学习资源合集。 https://t.co/uKEYSts8rG 4. build-your-own-x 通过亲手实现数据库、编译器等项目，理解它们的工作原理。 https://t.co/mWAUZSVUso… - [Reddit · r/learnprogramming · 2026-10-04](https://www.reddit.com/r/learnprogramming/comments/1wx5o1i/the_projects_imade_using_project_based_repo_from/): The projects Imade using project based repo from github... - [Hacker News · redbell · 2024-05-01](https://news.ycombinator.com/item?id=40223120): Project-Based Learning: A curated list of project-based tutorials - [Bluesky · Techandstream with Kevin Josué Marville \| Software Engineering · 2026-10-26](https://bsky.app/profile/kevinmarville.bsky.social/post/3myrunghevs2q): Working at Bell Labs must have been rather stimulating, with such talented people and innovative projects. What specifically caught your eye about Brian Kernighan’s story today? github.com/practical-tu... - [X · @wanerfu · 2026-10-12](https://x.com/wanerfu/status/2109511401131950300): $80 - [Reddit · r/letscodecommunity · 2026-09-24](https://www.reddit.com/r/letscodecommunity/comments/1wovq9x/10_github_repositories_to_master_python/): 10 GitHub repositories to master Python 👇 - [Hacker News · ibobev · 2021-08-26](https://news.ycombinator.com/item?id=28319542): Project Based Learning - [Bluesky · Tom Dörr · 2026-06-23](https://bsky.app/profile/tom-doerr.bsky.social/post/3moxbrklgzx2i): https://github.com/practical-tutorials/project-based-learning - [X · @wholovesmaths · 2026-09-27](https://x.com/wholovesmaths/status/2104140755317207083): @pacil\_menfess Hi, sender. Based on my experience, the best solution is practice and practice. Ini ada bbrp resources ya: - https://t.co/3p2ilugHHb - https://t.co/LeG7PSVs0R - https://t.co/bOe55SiRPu - https://t.co/48tcN6MN0u - https://t.co/AJlYFbopEZ - https://t.co/uE7yeDHkJ7 (continued) - [Hacker News · ibobev · 2022-07-20](https://news.ycombinator.com/item?id=32163051): Project Based Learning ## Get it - [Open practical-tutorials/project-based-learning on GitHub](https://github.com/practical-tutorials/project-based-learning) - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/9922f433-eb31-44dc-98e7-fcf4d76379f1) - [Its page on Mindket](https://mindket.com/p/9922f433-eb31-44dc-98e7-fcf4d76379f1)