國立虎尾科技大學 |

Bad Programming Practices 101 = Become a Better Coder by Learning How (Not) to Program /

紀錄類型:	書目-語言資料,印刷品 : Monograph/item
正題名/作者:	Bad Programming Practices 101/ by Karl Beecher.
其他題名:	Become a Better Coder by Learning How (Not) to Program /
作者:	Beecher, Karl.
面頁冊數:	XXII, 221 p. 15 illus. in color.online resource. :
Contained By:	Springer Nature eBook
標題:	Computer programming. -
電子資源:	https://doi.org/10.1007/978-1-4842-3411-2
ISBN:	9781484234112

Bad Programming Practices 101 = Become a Better Coder by Learning How (Not) to Program /
Beecher, Karl.

Bad Programming Practices 101Become a Better Coder by Learning How (Not) to Program /[electronic resource] :by Karl Beecher. - 1st ed. 2018. - XXII, 221 p. 15 illus. in color.online resource.

1. 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.

This 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.

ISBN: 9781484234112

Standard No.: 10.1007/978-1-4842-3411-2doiSubjects--Topical Terms:

527822
Computer programming.

LC Class. No.: QA76.6-76.66

Dewey Class. No.: 005.11

Bad Programming Practices 101 = Become a Better Coder by Learning How (Not) to Program /
LDR:03768nam a22003975i 4500 001 997982
003 DE-He213
005 20200706093618.0
007 cr nn 008mamaa
008 201225s2018 xxu| s |||| 0|eng d
020 $a 9781484234112 $9 978-1-4842-3411-2
024 7 $a 10.1007/978-1-4842-3411-2 $2 doi
035 $a 978-1-4842-3411-2
050 4 $a QA76.6-76.66
072 7 $a UM $2 bicssc
072 7 $a COM051000 $2 bisacsh
072 7 $a UM $2 thema
082 0 4 $a 005.11 $2 23
100 1 $a Beecher, Karl. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1289376
245 1 0 $a Bad Programming Practices 101 $h [electronic resource] : $b Become a Better Coder by Learning How (Not) to Program / $c by Karl Beecher.
250 $a 1st ed. 2018.
264 1 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2018.
300 $a XXII, 221 p. 15 illus. in color. $b online resource.
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
347 $a text file $b PDF $2 rda
505 0 $a 1. 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.
520 $a This 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.
650 0 $a Computer programming. $3 527822
650 0 $a Software engineering. $3 562952
650 0 $a Programming languages (Electronic computers). $3 1127615
650 1 4 $a Programming Techniques. $3 669781
650 2 4 $a Software Engineering. $3 669632
650 2 4 $a Programming Languages, Compilers, Interpreters. $3 669782
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer Nature eBook
776 0 8 $i Printed edition: $z 9781484234105
776 0 8 $i Printed edition: $z 9781484234129
776 0 8 $i Printed edition: $z 9781484245699
856 4 0 $u https://doi.org/10.1007/978-1-4842-3411-2
912 $a ZDB-2-CWD
912 $a ZDB-2-SXPC
950 $a Professional and Applied Computing (SpringerNature-12059)
950 $a Professional and Applied Computing (R0) (SpringerNature-43716)