LEADER 01474nam 2200481 450 001 9910271039703321 005 20170925121634.0 010 $a1-118-89631-9 010 $a1-118-89626-2 010 $a1-118-89637-8 035 $a(CKB)4330000000007405 035 $a(MiAaPQ)EBC4822496 035 $a(DLC) 2017003506 035 $a(PPN)224676857 035 $a(EXLCZ)994330000000007405 100 $a20170327h20172017 uy 0 101 0 $aeng 135 $aurcnu|||||||| 181 $2rdacontent 182 $2rdamedia 183 $2rdacarrier 200 04$aThe Cambrian fossils of Chengjiang, China $ethe flowering of early animal life /$fHou Xian-guang [and eight others] 205 $aSecond edition. 210 1$aChichester, West Sussex, England :$cWiley-Blackwell,$d2017. 210 4$dİ2017 215 $a1 online resource (331 pages) 311 $a1-118-89638-6 320 $aIncludes bibliographical references and indexes. 606 $aAnimals, Fossil$zChina$zChengjiang (Yunnan Sheng) 606 $aPaleobiology$zChina$zChengjiang (Yunnan Sheng) 606 $aPaleontology$yCambrian 615 0$aAnimals, Fossil 615 0$aPaleobiology 615 0$aPaleontology 676 $a560/.1723095135 702 $aHou$b Xianguang 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910271039703321 996 $aThe Cambrian fossils of Chengjiang, China$92815601 997 $aUNINA LEADER 04641nam 22006255 450 001 9910300754303321 005 20200706093618.0 010 $a9781484234112 010 $a1484234111 024 7 $a10.1007/978-1-4842-3411-2 035 $a(CKB)3840000000342342 035 $a(MiAaPQ)EBC5287201 035 $a(DE-He213)978-1-4842-3411-2 035 $a(iGPub)SPNA0054791 035 $a(CaSebORM)9781484234112 035 $a(PPN)224641077 035 $a(OCoLC)1154455995 035 $a(OCoLC)on1154455995 035 $a(EXLCZ)993840000000342342 100 $a20180208d2018 u| 0 101 0 $aeng 135 $aurcnu|||||||| 181 $2rdacontent 182 $2rdamedia 183 $2rdacarrier 200 10$aBad Programming Practices 101 $eBecome a Better Coder by Learning How (Not) to Program /$fby Karl Beecher 205 $a1st ed. 2018. 210 1$aBerkeley, CA :$cApress :$cImprint: Apress,$d2018. 215 $a1 online resource (221 pages) $cillustrations 311 08$a9781484234105 311 08$a1484234103 320 $aIncludes bibliographical references and index. 327 $a1. Fundamentals of Badness -- 2. Layout and Structure -- 3. Variables -- 4. Conditionals -- 5. Loops -- 6. Subroutines -- 7. Error-handling -- 8. Modules -- 9. Objects -- 10. Testing -- 11. Debugging -- Glossary -- Bibliography. 330 $aThis book takes a humorous slant on the programming practice manual by reversing the usual approach: under the pretence of teaching you how to become the world?s worst programmer who generally causes chaos, the book teaches you how to avoid the kind of bad habits that introduce bugs or cause code contributions to be rejected. Why be a code monkey when you can be a chaos monkey? OK, so you want to become a terrible programmer. You want to write code that gets vigorously rejected in review. You look forward to reading feedback plastered in comments like "WTF???". Even better, you fantasize about your bug-ridden changes sneaking through and causing untold chaos in the codebase. You want to build a reputation as someone who writes creaky, messy, error-prone garbage that frustrates your colleagues. Bad Programming Practices 101 will help you achieve that goal a whole lot quicker by teaching you an array of bad habits that will allow you to cause maximum chaos. Alternatively, you could use this book to identify those bad habits and learn to avoid them. The bad practices are organised into topics that form the basis of programming (layout, variables, loops, modules, and so on). It's been remarked that to become a good programmer, you must first write 10,000 lines of bad code to get it all out of your system. This book is aimed at programmers who have so far written only a small portion of that. By learning about poor programming habits, you will learn good practices. In addition, you will find out the motivation behind each practice, so you can learn why it is considered good and not simply get a list of rules. You will: Become a better coder by learning how (not) to program Choose your tools wisely Think of programming as problem solving Discover the consequences of a program?s appearance and overall structure Explain poor use of variables in programs Avoid bad habits and common mistakes when using conditionals and loops See how poor error-handling makes for unstable programs Sidestep bad practices related specifically to object-oriented programming Mitigate the effects of ineffectual and inadequate bug location and testing. 517 3 $aBad programming practices one hundred one 606 $aComputer programming 606 $aSoftware engineering 606 $aProgramming languages (Electronic computers) 606 $aProgramming Techniques$3https://scigraph.springernature.com/ontologies/product-market-codes/I14010 606 $aSoftware Engineering$3https://scigraph.springernature.com/ontologies/product-market-codes/I14029 606 $aProgramming Languages, Compilers, Interpreters$3https://scigraph.springernature.com/ontologies/product-market-codes/I14037 615 0$aComputer programming. 615 0$aSoftware engineering. 615 0$aProgramming languages (Electronic computers) 615 14$aProgramming Techniques. 615 24$aSoftware Engineering. 615 24$aProgramming Languages, Compilers, Interpreters. 676 $a005.133 700 $aBeecher$b Karl$4aut$4http://id.loc.gov/vocabulary/relators/aut$01058191 801 0$bUMI 801 1$bUMI 906 $aBOOK 912 $a9910300754303321 996 $aBad Programming Practices 101$92497778 997 $aUNINA