project-based-learning VS Crafting Interpreters

Project-based learning — Explore the Project Based Learning repository

💻 5. Project-Based Learning 📍 https://github.com/practical-tutorials/project-based-learning  Why it's awesome:  Learn by building real projects in React, Vue, Go, ML, DevOps, and more. Structured tutorials that go beyond theory. ✅ Best For: Learners who hate theory  🚀 Hackathon-Ready Projects + Resume-Ready Work

1️⃣6️⃣ Project-Based Learning 🔨 📌 https://github.com/practical-tutorials/project-based-learning A collection of hands-on projects to improve your coding skills.

View on GitHub

🔗 Website: https://gittech.site/github/item/42650788... 📂 GitHub Repository: https://github.com/practical-tutorials/project-based-learning 📅 Published On: Thu, 09 Jan 2025 23:27:04 GMT

Link: https://github.com/practical-tutorials/project-based-learning

Nodejs practical tutorials

Project-Based Learning Programming Tutorials

9. Practical-tutorials/project-based-learning - This repository provides links to project-based tutorials for various programming languages, with a focus on Python. It's a great way to gain practical experience and build your developer portfolio. https://github.com/practical-tutorials/project-based-learning

[An optional challenge](https://github.com/munificent/craftinginterpreters/blob/4a84...) gives an implementation of arrays for jlox at least.

Cool! I did not know about that book. Added to [1]. :-)

--

1: https://github.com/munificent/craftinginterpreters/issues/92...

> If you’ve been relying on Markdown and occasionally fighting its quirks, AsciiDoc might be the structured, fully-featured alternative you didn’t know you needed.

No, I'm afraid it's the format I know I don't need. At least not for the kind of things I usually use markdown for.

Readme files, technical documentation, moderately complex websites with templating and rendering engines - markdown works just fine. Sometimes with a custom `|||warning\n...\n|||\n` thrown in to render something in a box with a red border.

I get that there's a market in the space occupied by TeX, Typst (underrated IMHO), and possibly MS Word or Quark Express (for non-techies). Libreoffice is great in theory but, again IMHO, "eh" in practice. That market is generating book-length documents with all the cross-references and other features that needs.

That said, Robert Nystrom of "Crafting Interpreters" managed this just fine with markdown and a few custom scripts: https://journal.stuffwithstuff.com/2020/04/05/crafting-craft... , https://github.com/munificent/craftinginterpreters/tree/mast... . This is how those famous 10x writers/programmers work, I guess.

Asciidoc is Markdown's big brother? I'll carry on playing with the little brother, thank you very much.

Also the whole page is an ad for their own editor tool. $9.99 per month so you don't need to use your own editor and unintuitive tools like (gasp!) the terminal.

Build an Interpreter (Chapter 14 on is written in C)

[3]: https://github.com/munificent/craftinginterpreters

The best resource for any amateur compiler writer is Bob Noystrom's Crafting Interpreters:

https://www.craftinginterpreters.com/

It is well paced, well illustrated, and demonstrates a very simple recursive descent parser, avoiding all the junk typically foisted on students.

I cannot recommend the book highly enough, I use it in my compilers class.

The license is here:

https://github.com/munificent/craftinginterpreters/blob/mast...

Though now that I look at it, I apparently completely forgot to specify how the images should be licensed. Oops.

It's not a big deal and I really appreciate you reading and writing about the book, but I would prefer to not have the images reused without attribution.

Lots of people have done implementations in other languages: https://github.com/munificent/craftinginterpreters/wiki/Lox-...

I did the first half in Clojure (in order to teach myself Clojure), worked just fine. I had to do a bit of translation but it's really not a lot.