4 ms·
A wild UC Berkeley CS 61A adventure appears! https://inst.eecs.berkeley.edu/~cs61a/su13/lab/lab06a/lab06a.txt https://inst.eecs.berkeley.edu/~cs61a/su13/lab/la
by dbpokorny 11y ago
A wild UC Berkeley CS 61A adventure appears!
https://inst.eecs.berkeley.edu/~cs61a/su13/lab/lab06a/lab06a.txt https://inst.eecs.berkeley.edu/~cs61a/su13/lab/lab06a/lab06a...
You can stick your pseudocode into the "give" function: https://inst.eecs.berkeley.edu/~cs61a/sp15/lab/lab10/adventure.py https://inst.eecs.berkeley.edu/~cs61a/sp15/lab/lab10/adventu...
I'm not sure it's explicit in the original article, but I tend to agree with the sentiment that it's a lot more fun to learn about interpreters and databases when you're making games rather than corporate infrastructure (although I can't deny that building corporate infrastructure has its moments)
Joel Spolsky talks about using the compiler to catch errors on p. 68 of "The Best Software Writing I"
https://books.google.com/books?id=vPvhzDqZlaAC&pg=PA68&lpg=PA68&dq=joel+spolsky+type+compiler&source=bl&ots=cm2hRdP9W5&sig=I3gcA35aUfqoKCcQoiIm-CM6CvY&hl=en&sa=X&ved=0CFUQ6AEwCGoVChMI2YzG6KSUyQIVBcNjCh1oQAcK#v=onepage&q=joel%20spolsky%20type%20compiler&f=false https://books.google.com/books?id=vPvhzDqZlaAC&pg=PA68&lpg=P...