A philosophy of software design:
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Palo Alto, CA
Yaknyam Press
February 2022
|
| Ausgabe: | Second edition (2.01) |
| Schlagworte: | |
| Beschreibung: | x, 184 Seiten 21 cm |
| ISBN: | 9781732102217 173210221X |
Internformat
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV048646435 | ||
| 003 | DE-604 | ||
| 005 | 20230512 | ||
| 007 | t| | ||
| 008 | 230112s2022 xx |||| 00||| eng d | ||
| 020 | |a 9781732102217 |9 978-1-7321022-1-7 | ||
| 020 | |a 173210221X |9 173210221X | ||
| 035 | |a (OCoLC)1362874133 | ||
| 035 | |a (DE-599)BVBBV048646435 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-706 |a DE-91G |a DE-523 |a DE-703 | ||
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 084 | |a DAT 315 |2 stub | ||
| 100 | 1 | |a Ousterhout, John K. |d 1954- |e Verfasser |0 (DE-588)172296900 |4 aut | |
| 245 | 1 | 0 | |a A philosophy of software design |c John Ousterhout |
| 250 | |a Second edition (2.01) | ||
| 264 | 1 | |a Palo Alto, CA |b Yaknyam Press |c February 2022 | |
| 300 | |a x, 184 Seiten |c 21 cm | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 505 | 8 | 0 | |t Introduction -- |t The nature of complexity -- |t Working code isn't enough -- |t Modules should be deep -- |t Information hiding (and leakage) -- |t General-purpose modules are deeper -- |t Different layer, different abstraction -- |t Pull complexity downwards -- |t Better together or better apart? -- |t Define errors out of existence -- |t Design it twice -- |t Why write comments? The four excuses -- |t Comments should descibre things that aren't obvious from the code -- |t Choosing names -- |t Write the comments first -- |t Modifying existing code -- |t Consistency -- |t Code should be obvious -- |t Software trends -- |t Designing for performance -- |t Decide what matters -- |t Conclusion |
| 650 | 0 | 7 | |a Design |0 (DE-588)4011510-0 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Software |0 (DE-588)4055382-6 |2 gnd |9 rswk-swf |
| 653 | 0 | |a Computer programs / Design | |
| 653 | 0 | |a Object-oriented programming (Computer science) | |
| 653 | 0 | |a Modular programming | |
| 653 | 0 | |a Programmation orientée objet (Informatique) | |
| 653 | 0 | |a Programmation modulaire | |
| 653 | 0 | |a Computer programs / Design | |
| 653 | 0 | |a Modular programming | |
| 653 | 0 | |a Object-oriented programming (Computer science) | |
| 689 | 0 | 0 | |a Software |0 (DE-588)4055382-6 |D s |
| 689 | 0 | 1 | |a Design |0 (DE-588)4011510-0 |D s |
| 689 | 0 | |5 DE-604 | |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-034021308 | |
Datensatz im Suchindex
| _version_ | 1815612329822257152 |
|---|---|
| adam_text | |
| adam_txt | |
| any_adam_object | |
| any_adam_object_boolean | |
| author | Ousterhout, John K. 1954- |
| author_GND | (DE-588)172296900 |
| author_facet | Ousterhout, John K. 1954- |
| author_role | aut |
| author_sort | Ousterhout, John K. 1954- |
| author_variant | j k o jk jko |
| building | Verbundindex |
| bvnumber | BV048646435 |
| classification_rvk | ST 230 |
| classification_tum | DAT 315 |
| contents | Introduction -- The nature of complexity -- Working code isn't enough -- Modules should be deep -- Information hiding (and leakage) -- General-purpose modules are deeper -- Different layer, different abstraction -- Pull complexity downwards -- Better together or better apart? -- Define errors out of existence -- Design it twice -- Why write comments? The four excuses -- Comments should descibre things that aren't obvious from the code -- Choosing names -- Write the comments first -- Modifying existing code -- Consistency -- Code should be obvious -- Software trends -- Designing for performance -- Decide what matters -- Conclusion |
| ctrlnum | (OCoLC)1362874133 (DE-599)BVBBV048646435 |
| discipline | Informatik |
| discipline_str_mv | Informatik |
| edition | Second edition (2.01) |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>00000nam a2200000 c 4500</leader><controlfield tag="001">BV048646435</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20230512</controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">230112s2022 xx |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781732102217</subfield><subfield code="9">978-1-7321022-1-7</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">173210221X</subfield><subfield code="9">173210221X</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1362874133</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV048646435</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-706</subfield><subfield code="a">DE-91G</subfield><subfield code="a">DE-523</subfield><subfield code="a">DE-703</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">DAT 315</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Ousterhout, John K.</subfield><subfield code="d">1954-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)172296900</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">A philosophy of software design</subfield><subfield code="c">John Ousterhout</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">Second edition (2.01)</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Palo Alto, CA</subfield><subfield code="b">Yaknyam Press</subfield><subfield code="c">February 2022</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">x, 184 Seiten</subfield><subfield code="c">21 cm</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="505" ind1="8" ind2="0"><subfield code="t">Introduction --</subfield><subfield code="t">The nature of complexity --</subfield><subfield code="t">Working code isn't enough --</subfield><subfield code="t">Modules should be deep --</subfield><subfield code="t">Information hiding (and leakage) --</subfield><subfield code="t">General-purpose modules are deeper --</subfield><subfield code="t">Different layer, different abstraction --</subfield><subfield code="t">Pull complexity downwards --</subfield><subfield code="t">Better together or better apart? --</subfield><subfield code="t">Define errors out of existence --</subfield><subfield code="t">Design it twice --</subfield><subfield code="t">Why write comments? The four excuses --</subfield><subfield code="t">Comments should descibre things that aren't obvious from the code --</subfield><subfield code="t">Choosing names --</subfield><subfield code="t">Write the comments first --</subfield><subfield code="t">Modifying existing code --</subfield><subfield code="t">Consistency --</subfield><subfield code="t">Code should be obvious --</subfield><subfield code="t">Software trends --</subfield><subfield code="t">Designing for performance --</subfield><subfield code="t">Decide what matters --</subfield><subfield code="t">Conclusion</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Design</subfield><subfield code="0">(DE-588)4011510-0</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Software</subfield><subfield code="0">(DE-588)4055382-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Computer programs / Design</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Object-oriented programming (Computer science)</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Modular programming</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Programmation orientée objet (Informatique)</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Programmation modulaire</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Computer programs / Design</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Modular programming</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Object-oriented programming (Computer science)</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Software</subfield><subfield code="0">(DE-588)4055382-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Design</subfield><subfield code="0">(DE-588)4011510-0</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-034021308</subfield></datafield></record></collection> |
| id | DE-604.BV048646435 |
| illustrated | Not Illustrated |
| index_date | 2024-07-03T21:18:29Z |
| indexdate | 2024-11-13T13:00:47Z |
| institution | BVB |
| isbn | 9781732102217 173210221X |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-034021308 |
| oclc_num | 1362874133 |
| open_access_boolean | |
| owner | DE-706 DE-91G DE-BY-TUM DE-523 DE-703 |
| owner_facet | DE-706 DE-91G DE-BY-TUM DE-523 DE-703 |
| physical | x, 184 Seiten 21 cm |
| publishDate | 2022 |
| publishDateSearch | 2022 |
| publishDateSort | 2022 |
| publisher | Yaknyam Press |
| record_format | marc |
| spelling | Ousterhout, John K. 1954- Verfasser (DE-588)172296900 aut A philosophy of software design John Ousterhout Second edition (2.01) Palo Alto, CA Yaknyam Press February 2022 x, 184 Seiten 21 cm txt rdacontent n rdamedia nc rdacarrier Introduction -- The nature of complexity -- Working code isn't enough -- Modules should be deep -- Information hiding (and leakage) -- General-purpose modules are deeper -- Different layer, different abstraction -- Pull complexity downwards -- Better together or better apart? -- Define errors out of existence -- Design it twice -- Why write comments? The four excuses -- Comments should descibre things that aren't obvious from the code -- Choosing names -- Write the comments first -- Modifying existing code -- Consistency -- Code should be obvious -- Software trends -- Designing for performance -- Decide what matters -- Conclusion Design (DE-588)4011510-0 gnd rswk-swf Software (DE-588)4055382-6 gnd rswk-swf Computer programs / Design Object-oriented programming (Computer science) Modular programming Programmation orientée objet (Informatique) Programmation modulaire Software (DE-588)4055382-6 s Design (DE-588)4011510-0 s DE-604 |
| spellingShingle | Ousterhout, John K. 1954- A philosophy of software design Introduction -- The nature of complexity -- Working code isn't enough -- Modules should be deep -- Information hiding (and leakage) -- General-purpose modules are deeper -- Different layer, different abstraction -- Pull complexity downwards -- Better together or better apart? -- Define errors out of existence -- Design it twice -- Why write comments? The four excuses -- Comments should descibre things that aren't obvious from the code -- Choosing names -- Write the comments first -- Modifying existing code -- Consistency -- Code should be obvious -- Software trends -- Designing for performance -- Decide what matters -- Conclusion Design (DE-588)4011510-0 gnd Software (DE-588)4055382-6 gnd |
| subject_GND | (DE-588)4011510-0 (DE-588)4055382-6 |
| title | A philosophy of software design |
| title_alt | Introduction -- The nature of complexity -- Working code isn't enough -- Modules should be deep -- Information hiding (and leakage) -- General-purpose modules are deeper -- Different layer, different abstraction -- Pull complexity downwards -- Better together or better apart? -- Define errors out of existence -- Design it twice -- Why write comments? The four excuses -- Comments should descibre things that aren't obvious from the code -- Choosing names -- Write the comments first -- Modifying existing code -- Consistency -- Code should be obvious -- Software trends -- Designing for performance -- Decide what matters -- Conclusion |
| title_auth | A philosophy of software design |
| title_exact_search | A philosophy of software design |
| title_exact_search_txtP | A philosophy of software design |
| title_full | A philosophy of software design John Ousterhout |
| title_fullStr | A philosophy of software design John Ousterhout |
| title_full_unstemmed | A philosophy of software design John Ousterhout |
| title_short | A philosophy of software design |
| title_sort | a philosophy of software design |
| topic | Design (DE-588)4011510-0 gnd Software (DE-588)4055382-6 gnd |
| topic_facet | Design Software |
| work_keys_str_mv | AT ousterhoutjohnk aphilosophyofsoftwaredesign |