top | item 31836073

(no title)

chapliboy | 3 years ago

The author says it took about 6 months to thoroughly go through the book and examples.

This is really useful in setting expectations.

discuss

order

thundergolfer|3 years ago

I got through all chapters in around 1.5 months, spending 50-60 hours[1]. I'd do solid 4-5 hour blocks on Saturdays and Sundays when I was most into it.

I'm following teachyourselfcs.com[2], so I'm hoping to solidify the concepts the book intro'd by reimplementing the bytecode interpeter in Rust (rlox) and following Alex Aiken's lectures online. OP appears to have reimplemented Lox in Golang (glox) for reinforcement.

So far the time has been well spent. Compilers are now much more 'just another program', and I have new conceptual tools for tackling software engineering problems.

1. https://github.com/thundergolfer/uni/tree/main/books/craftin...

2. https://teachyourselfcs.com/#languages

chidiw|3 years ago

Yes, you can go through the book in much less time than six months if you're more consistent with it than I was. I took a few breaks (for days and sometimes weeks) to study and write other things.

RheingoldRiver|3 years ago

Did you read Computer Systems: A Programmer's Perspective first? I read about 300 pages of it (maybe 200 only, I forget) and got _extremely_ bored. I want to read Crafting Interpreters but I'm concerned that Computer Systems is too much of a prerequisite.

dragon96|3 years ago

As another data point, I've taken about 1.5 months for Part 1 of the book, chipping away at it for 1-2 hours on weekday mornings.