61–70 of 103 posts
Earlier quoted context omitted.
Not necessarily as relevant, programming has changed a lot since SICP came out. Sussman says so himself - https://youtu.be/OgRFOjVzvm0
Did geometry become irrelevant once we stopped caring about field boundaries along the flooding river Nile?
Earlier quoted context omitted.
I'm not saying text should be full of acronyms/initialisms, but they serve a purpose of compressing the content. Maybe the chosen acronyms/initialisms don't work for you and that'd be a fair point.
In good writing you should ideally use the full name of the thing you're going to abbreviate with the acronym in parenthesis after the initial "expanded" version. e.g. "My article is about How to Design Programs (HtDP)..." Then later the article: "In the HtDP book it mentions...." This makes life easier for those less familiar with the subject matter.
http://norvig.com/spell-correct.html
Now dominated by notebooks, linked to from norvig.com:
https://github.com/norvig/pytudes#pytudes-index-of-jupyter-i...
Sure lots of it is not as applicable now as it was, but it should absolutely be on your bookshelf in addition to more modern texts.
I spent most of my professional code slinging career doing Python, but IMHO it is critical to learn to read CS books in many languages. If you use any lexically scoped language, reading the chapter on environments and what happens when you go from pure functions to a language that sets variables is invaluable.
Concepts, Techniques, and Models of Computer Programming is also a great book.
Concepts, Techniques, and Models of Computer Programming is also a great book.
Earlier quoted context omitted.
In good writing you should ideally use the full name of the thing you're going to abbreviate with the acronym in parenthesis after the initial "expanded" version. e.g. "My article is about How to Design Programs (HtDP)..." Then later the article: "In the HtDP book it mentions...." This makes life easier for those less familiar with the subject matter.
This is a technical forum, it's reasonable to expect readers who discuss a thread about a specific subject of interest to be familiar with the common vernacular and idioms related to that subject. If you can't understand the initialisms, maybe that's a sign that particular thread isn't for you, and that you likely have little of value to add.
Earlier quoted context omitted.
In good writing you should ideally use the full name of the thing you're going to abbreviate with the acronym in parenthesis after the initial "expanded" version. e.g. "My article is about How to Design Programs (HtDP)..." Then later the article: "In the HtDP book it mentions...." This makes life easier for those less familiar with the subject matter.
This is a technical forum, it's reasonable to expect readers who discuss a thread about a specific subject of interest to be familiar with the common vernacular and idioms related to that subject. If you can't understand the initialisms, maybe that's a sign that particular thread isn't for you, and that you likely have little of value to add.
As a software developer with a forty year career behind me I'm quite familiar with the "SICP" book. But for some reason my brain won't persist the connection between the full title and the SICP acronym when I bump into it. Yet somehow I can recall what each and every assembly language mnemonic means across a fairly broad range of micro and mini computer processors.
> maybe that's a sign that particular thread isn't for you, and that you likely have little of value to add.
Sure I may not have much to add, but the reason to read a thread, article or essay is to become familiar with the subject matter because it sounds interesting. Don't assume your reader is an expert in decoding your special and often made up acronyms.
https://cs.uwaterloo.ca/~plragde/flaneries/FICS/
Functional Introduction to Computer Science