The rules of programming: how to write better code
Saved in:
| Main Author: | |
|---|---|
| Format: | Book |
| Language: | English |
| Published: |
Sebastopol, CA
O'Reilly
2022
|
| Edition: | First edition |
| Subjects: | |
| Abstract: | "This philosophy-of-programming guide presents a unique and entertaining take on how to think about programming. A collection of 21 pragmatic rules, each presented in a standalone chapter, captures the essential wisdom that every freshly minted programmer needs to know and provides thought-provoking insights for more seasoned programmers"-- |
| Item Description: | Includes index |
| Physical Description: | XIV, 327 Seiten 23 cm |
| ISBN: | 9781098133115 1098133110 |
Staff View
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV049087051 | ||
| 003 | DE-604 | ||
| 005 | 20240830 | ||
| 007 | t| | ||
| 008 | 230802s2022 xx |||| 00||| eng d | ||
| 020 | |a 9781098133115 |9 978-1-098-13311-5 | ||
| 020 | |a 1098133110 |9 1098133110 | ||
| 035 | |a (OCoLC)1377760210 | ||
| 035 | |a (DE-599)BVBBV049087051 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-898 |a DE-92 | ||
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 100 | 1 | |a Zimmerman, Chris |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a The rules of programming |b how to write better code |c Chris Zimmerman |
| 250 | |a First edition | ||
| 264 | 1 | |a Sebastopol, CA |b O'Reilly |c 2022 | |
| 264 | 4 | |c © 2023 | |
| 300 | |a XIV, 327 Seiten |c 23 cm | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 500 | |a Includes index | ||
| 505 | 8 | |a As simple as possible, but no simpler -- Bugs are contagious -- A good name is the best documentation -- Generalization takes three examples -- The first lesson of optimization is don't optimize -- Interlude: In which the previous chapter is criticized -- Code reviews are good for three reasons -- Eliminate failure cases -- Code that isn't running doesn't work -- Write collapsible code -- Localize complexity -- Is it twice as good? -- Big teams need strong conventions -- Find the pebble that started the avalanche -- Code comes in four flavors -- Pull the weeds -- Work backward from your result, not forward from your code --- Sometimes the bigger problem is easier to solve -- Let your code tell its own story -- Rework in parallel -- Do the math -- Sometimes you just need to hammer the nails -- Conclusion: Making the rules your own -- Appendix A. Reading C++ for Python programmers -- Appendix B. Reading C++ for JavaScript programmers | |
| 520 | 3 | |a "This philosophy-of-programming guide presents a unique and entertaining take on how to think about programming. A collection of 21 pragmatic rules, each presented in a standalone chapter, captures the essential wisdom that every freshly minted programmer needs to know and provides thought-provoking insights for more seasoned programmers"-- | |
| 650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Programmierung |0 (DE-588)4076370-5 |2 gnd |9 rswk-swf |
| 653 | 0 | |a Computer programming | |
| 653 | 0 | |a Computer programming / Philosophy | |
| 653 | 0 | |a Computer programming | |
| 653 | 0 | |a Computer programming / Philosophy | |
| 689 | 0 | 0 | |a Programmierung |0 (DE-588)4076370-5 |D s |
| 689 | 0 | 1 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 0 | |5 DE-604 | |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-034348855 | |
Record in the Search Index
| DE-BY-OTHR_call_number | F 03/ST 230 Z73 |
|---|---|
| DE-BY-OTHR_katkey | 6733800 |
| DE-BY-OTHR_location | 02 |
| DE-BY-OTHR_media_number | 067004785323 |
| _version_ | 1831256307398606848 |
| any_adam_object | |
| author | Zimmerman, Chris |
| author_facet | Zimmerman, Chris |
| author_role | aut |
| author_sort | Zimmerman, Chris |
| author_variant | c z cz |
| building | Verbundindex |
| bvnumber | BV049087051 |
| classification_rvk | ST 230 |
| contents | As simple as possible, but no simpler -- Bugs are contagious -- A good name is the best documentation -- Generalization takes three examples -- The first lesson of optimization is don't optimize -- Interlude: In which the previous chapter is criticized -- Code reviews are good for three reasons -- Eliminate failure cases -- Code that isn't running doesn't work -- Write collapsible code -- Localize complexity -- Is it twice as good? -- Big teams need strong conventions -- Find the pebble that started the avalanche -- Code comes in four flavors -- Pull the weeds -- Work backward from your result, not forward from your code --- Sometimes the bigger problem is easier to solve -- Let your code tell its own story -- Rework in parallel -- Do the math -- Sometimes you just need to hammer the nails -- Conclusion: Making the rules your own -- Appendix A. Reading C++ for Python programmers -- Appendix B. Reading C++ for JavaScript programmers |
| ctrlnum | (OCoLC)1377760210 (DE-599)BVBBV049087051 |
| discipline | Informatik |
| edition | First edition |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02671nam a2200445 c 4500</leader><controlfield tag="001">BV049087051</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20240830 </controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">230802s2022 xx |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781098133115</subfield><subfield code="9">978-1-098-13311-5</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1098133110</subfield><subfield code="9">1098133110</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1377760210</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV049087051</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-898</subfield><subfield code="a">DE-92</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="100" ind1="1" ind2=" "><subfield code="a">Zimmerman, Chris</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">The rules of programming</subfield><subfield code="b">how to write better code</subfield><subfield code="c">Chris Zimmerman</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">First edition</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Sebastopol, CA</subfield><subfield code="b">O'Reilly</subfield><subfield code="c">2022</subfield></datafield><datafield tag="264" ind1=" " ind2="4"><subfield code="c">© 2023</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XIV, 327 Seiten</subfield><subfield code="c">23 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="500" ind1=" " ind2=" "><subfield code="a">Includes index</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">As simple as possible, but no simpler -- Bugs are contagious -- A good name is the best documentation -- Generalization takes three examples -- The first lesson of optimization is don't optimize -- Interlude: In which the previous chapter is criticized -- Code reviews are good for three reasons -- Eliminate failure cases -- Code that isn't running doesn't work -- Write collapsible code -- Localize complexity -- Is it twice as good? -- Big teams need strong conventions -- Find the pebble that started the avalanche -- Code comes in four flavors -- Pull the weeds -- Work backward from your result, not forward from your code --- Sometimes the bigger problem is easier to solve -- Let your code tell its own story -- Rework in parallel -- Do the math -- Sometimes you just need to hammer the nails -- Conclusion: Making the rules your own -- Appendix A. Reading C++ for Python programmers -- Appendix B. Reading C++ for JavaScript programmers</subfield></datafield><datafield tag="520" ind1="3" ind2=" "><subfield code="a">"This philosophy-of-programming guide presents a unique and entertaining take on how to think about programming. A collection of 21 pragmatic rules, each presented in a standalone chapter, captures the essential wisdom that every freshly minted programmer needs to know and provides thought-provoking insights for more seasoned programmers"--</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Programmierung</subfield><subfield code="0">(DE-588)4076370-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Computer programming</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Computer programming / Philosophy</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Computer programming</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Computer programming / Philosophy</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Programmierung</subfield><subfield code="0">(DE-588)4076370-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</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-034348855</subfield></datafield></record></collection> |
| id | DE-604.BV049087051 |
| illustrated | Not Illustrated |
| indexdate | 2024-12-20T20:00:28Z |
| institution | BVB |
| isbn | 9781098133115 1098133110 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-034348855 |
| oclc_num | 1377760210 |
| open_access_boolean | |
| owner | DE-898 DE-BY-UBR DE-92 |
| owner_facet | DE-898 DE-BY-UBR DE-92 |
| physical | XIV, 327 Seiten 23 cm |
| publishDate | 2022 |
| publishDateSearch | 2022 |
| publishDateSort | 2022 |
| publisher | O'Reilly |
| record_format | marc |
| spellingShingle | Zimmerman, Chris The rules of programming how to write better code As simple as possible, but no simpler -- Bugs are contagious -- A good name is the best documentation -- Generalization takes three examples -- The first lesson of optimization is don't optimize -- Interlude: In which the previous chapter is criticized -- Code reviews are good for three reasons -- Eliminate failure cases -- Code that isn't running doesn't work -- Write collapsible code -- Localize complexity -- Is it twice as good? -- Big teams need strong conventions -- Find the pebble that started the avalanche -- Code comes in four flavors -- Pull the weeds -- Work backward from your result, not forward from your code --- Sometimes the bigger problem is easier to solve -- Let your code tell its own story -- Rework in parallel -- Do the math -- Sometimes you just need to hammer the nails -- Conclusion: Making the rules your own -- Appendix A. Reading C++ for Python programmers -- Appendix B. Reading C++ for JavaScript programmers Softwareentwicklung (DE-588)4116522-6 gnd Programmierung (DE-588)4076370-5 gnd |
| subject_GND | (DE-588)4116522-6 (DE-588)4076370-5 |
| title | The rules of programming how to write better code |
| title_auth | The rules of programming how to write better code |
| title_exact_search | The rules of programming how to write better code |
| title_full | The rules of programming how to write better code Chris Zimmerman |
| title_fullStr | The rules of programming how to write better code Chris Zimmerman |
| title_full_unstemmed | The rules of programming how to write better code Chris Zimmerman |
| title_short | The rules of programming |
| title_sort | the rules of programming how to write better code |
| title_sub | how to write better code |
| topic | Softwareentwicklung (DE-588)4116522-6 gnd Programmierung (DE-588)4076370-5 gnd |
| topic_facet | Softwareentwicklung Programmierung |
| work_keys_str_mv | AT zimmermanchris therulesofprogramminghowtowritebettercode |