ruby-science VS Crafting Interpreters

So, bigger is worse, but how big is bad? At what number should you take action? Thoughtbot's Ruby Science book suggests a method is long or complex with a flog score above 10. It also posits that a class is long or complex with a flog score above 50.

Ruby Science - it's a free book by thoughtbot. It might be the most short term beneficial thing honestly. It just points out all of these various practical patterns you can immediate use to increase code quality.

I think you would appreciate Ruby Science. I love this book, it's extremely practical.

Well, if you're programming in Ruby, a great place to start is the Ruby Science book by ThoughtBot. It's a bottom-up approach to improving your code by identifying code smells and applying OO principles to fix them. Identifying smells in your own code will lead you to the OO principles that you need to learn to build your OO skills.

Read Ruby science to learn about code smells and good architecture.

It's a bit more advanced, but I like Ruby Science by thoughtbot.

Check out Ruby Science by Thoughtbot which I found useful at your stage.

Code smells. Ruby science is a good one for Ruby.

Currnetly reading ruby science. 200+ page guide on code smells and solutions.

This book is old but it's still very relevant https://github.com/thoughtbot/ruby-science. Also check out thoughtbot's blog and www.gorails.com

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.

Dumb idea? No way. Actually, I'm currently reading Crafting Interpreters which is exactly this. It's free to read online, if you wanted to check it out: https://www.craftinginterpreters.com/

Super fun book.

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