How to Think Like a Computer Scientist: C Version (Record no. 136)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 01746nam a2200229 i 4500 |
| 001 - CONTROL NUMBER | |
| control field | UUN-OA-620 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20260922220306.0 |
| 100 1# - MAIN ENTRY--PERSONAL NAME | |
| Personal name | Allen B. Downey |
| 245 10 - TITLE STATEMENT | |
| Title | How to Think Like a Computer Scientist: C Version |
| 264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE | |
| Name of producer, publisher, distributor, manufacturer | Green Tea Press |
| Date of production, publication, distribution, manufacture, or copyright notice | 1999 |
| 300 ## - PHYSICAL DESCRIPTION | |
| Extent | 1 online resource |
| 336 ## - CONTENT TYPE | |
| Content type term | text |
| Content type code | txt |
| Source | rdacontent |
| 337 ## - MEDIA TYPE | |
| Media type term | computer |
| Media type code | c |
| Source | rdamedia |
| 338 ## - CARRIER TYPE | |
| Carrier type term | online resource |
| Carrier type code | cr |
| Source | rdacarrier |
| 520 ## - SUMMARY, ETC. | |
| Summary, etc. | The goal of this book is to teach you to think like a computer scientist. I like the way computer scientists think because they combine some of the best features of Mathematics, Engineering, and Natural Science. Like mathematicians, computer scientists use formal languages to denote ideas (specifically computations). Like engineers, they design things, assembling components into systems and evaluating trade offs among alternatives. Like scientists, they observe the behavior of complex systems, form hypotheses, and test predictions.The single most important skill for a computer scientist is problem-solving. By that I mean the ability to formulate problems, think creatively about solutions, and express a solution clearly and accurately. As it turns out, the process of learning to program is an excellent opportunity to practice problem-solving skills. That’s why this chapter is called “The way of the program.” |
| 540 ## - TERMS GOVERNING USE AND REPRODUCTION NOTE | |
| Terms governing use and reproduction | Attribution-NonCommercial |
| 650 #4 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name entry element | Computer Science - Programming Languages |
| 650 #4 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name entry element | B. Sc. Computer Science |
| Source of heading or term | local |
| 650 #4 - SUBJECT ADDED ENTRY--TOPICAL TERM | |
| Topical term or geographic name entry element | B. Sc. Software Engineering |
| Source of heading or term | local |
| 856 40 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | <a href="https://github.com/tscheffl/ThinkC">https://github.com/tscheffl/ThinkC</a> |
| Link text | Read online |
| 856 42 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | <a href="https://open.umn.edu/opentextbooks/textbooks/how-to-think-like-a-computer-scientist-c-version-1999">https://open.umn.edu/opentextbooks/textbooks/how-to-think-like-a-computer-scientist-c-version-1999</a> |
| Link text | Open Textbook Library record |
No items available.