Earlier quoted context omitted.
I see you as fortunate. I battled for years with frustration and loss of passion for coding until I ran into LISP/Scheme/Racket. I like how you put it that it "locked into my brain like it had always been there", I felt the same when I finally got to it. I also discovered this accidentally but much later in my career and only after I started lurking on HN few years ago. I am learning and toying frequently and am very…
Do you remember which book that was? Sounds interesting.
How to Design Programs (2014)
61–70 of 141 posts
Re: How to Design Programs (2014)
#62Earlier quoted context omitted.
I see you as fortunate. I battled for years with frustration and loss of passion for coding until I ran into LISP/Scheme/Racket. I like how you put it that it "locked into my brain like it had always been there", I felt the same when I finally got to it. I also discovered this accidentally but much later in my career and only after I started lurking on HN few years ago. I am learning and toying frequently and am very…
Do you remember which book that was? Sounds interesting.
Re: How to Design Programs (2014)
#63Earlier quoted context omitted.
I never understood the appeal of this, or SICP, or Scheme in general. I learned much more about computer science reading algorithms and data structures textbooks, especially Knuth. There's a reason MIT uses Python for its intro courses now, after all.
While I have friends (and many colleagues) who graduated from MIT CS and are very competent engineers, I don't think MIT is the shining beacon of the best SE/CS graduates. Their program is certainly very good, but if someone asked me (for CS/SE specifically) about going to MIT or NU, I'd point them to NU. For almost everything else, it would, of course, be MIT.
Re: How to Design Programs (2014)
#64Why is this posted again today?
There was this question about books on software engineering. https://news.ycombinator.com/item?id=26488944 I saw it was at least a couple of years since HtDP was discussed on HN. I appreciate its flat footed approach and systematic method. To me, these are hallmarks of professional engineering practice. There's no attempt to make the problems more interesting by adding complexity or affectations. YMMV.
Re: How to Design Programs (2014)
#65Earlier quoted context omitted.
I never understood the appeal of this, or SICP, or Scheme in general. I learned much more about computer science reading algorithms and data structures textbooks, especially Knuth. There's a reason MIT uses Python for its intro courses now, after all.
MIX/MMIX are close to how CPUs work physically. scheme is close to how computation works theoretically. The pedagogical approach that appeals to individuals tends to align with how they are most comfortable thinking about it.
Re: How to Design Programs (2014)
#66Re: How to Design Programs (2014)
#67Why is this posted again today?
Hanson & Sussman have a new SICP-related book coming out which tackles similar topics: https://mitpress.mit.edu/books/software-design-flexibility This post may ultimately be downstream of people thinking about software engineering/CS textbooks and comparing.
Re: How to Design Programs (2014)
#68Earlier quoted context omitted.
I see you as fortunate. I battled for years with frustration and loss of passion for coding until I ran into LISP/Scheme/Racket. I like how you put it that it "locked into my brain like it had always been there", I felt the same when I finally got to it. I also discovered this accidentally but much later in my career and only after I started lurking on HN few years ago. I am learning and toying frequently and am very…
Do you remember which book that was? Sounds interesting.
Re: How to Design Programs (2014)
#69I am self taught, I worked as a lawyer for six years and four of those were spent prepping for a career change - self-teaching comp sci and software dev in the evenings, then working as a volunteer a few years in. (I come from an engineering family and should have just done it from the start, but oh well.) I'm not sure if it's still on the platform, but about a year into my self studying I took a series of courses on…
I think these are the 2 courses OP is talking about: https://www.edx.org/course/how-to-code-simple-data https://www.edx.org/course/how-to-code-complex-data
Re: How to Design Programs (2014)
#70Earlier quoted context omitted.
Matthias Felleisen was my professor at Rice 2 decades ago and I can still hear his distinctive voice clearly in my head! I too was resistant at first having done some programming in high school, but I wish I could go back and tell myself to pay attention more. Now I know Matthias was both wise and passionate and that combination doesn’t show up in every CS class, so to this day I’m nostalgic for the way he introduced…
I must be the black sheep of this thread, because I had a completely different experience. Professor Felleisen was never my professor directly, but he did oversee a few of the introductory courses I took, and was very present and had a heavy hand in many of the advanced courses. I also went to him for a number of office hour sessions. He came off as incredibly self-absorbed and at times, borderline hostile. A sibling…
Notice the font size of his name, versus the font size of the students who actually wrote the book and everything will be clear to you!