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 organized 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.
What You'll Learn
- 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
Who This Book Is For
Those who have some practical programming knowledge (can program in at least one programming language), but little or no professional experience, which they would like to quickly build up. They are either still undergoing training in software development, or are at the beginning of their programming career. They have at most 1-2 years of professional experience.
這本書以幽默的角度來看待程式設計實踐手冊，顛覆了通常的教學方式：在假裝教你如何成為世界上最糟糕的程式設計師，通常會造成混亂的前提下，這本書教你如何避免那些會引入錯誤或導致程式碼貢獻被拒絕的壞習慣。
為什麼要當一個程式碼猴子，當你可以成為一個混亂猴子呢？好吧，你想成為一個糟糕的程式設計師。你想寫出在審查中被猛烈拒絕的程式碼。你期待看到評論中貼滿「WTF???」的反饋。更好的是，你幻想著你那充滿錯誤的變更悄悄通過，並在程式碼庫中造成無法估量的混亂。你想建立一個寫出吱吱作響、雜亂無章、易出錯的垃圾程式碼的聲譽，讓你的同事感到沮喪。《壞程式設計實踐 101》將幫助你更快達成這個目標，教你一系列的壞習慣，讓你能夠造成最大的混亂。
或者，你也可以利用這本書來識別那些壞習慣並學會避免它們。這些壞習慣被組織成幾個主題，構成程式設計的基礎（佈局、變數、迴圈、模組等等）。有人曾經提到，要成為一個好的程式設計師，你必須先寫出10,000行壞程式碼，才能將它們從系統中排出。這本書的目標是針對那些至今只寫出一小部分的程式設計師。通過了解不良的程式設計習慣，你將學會好的實踐。此外，你還會發現每種實踐背後的動機，這樣你就能了解為什麼它被認為是好的，而不僅僅是得到一個規則清單。
你將學到的內容：
- 通過學習如何（不）編程來成為更好的程式設計師
- 明智地選擇你的工具
- 將程式設計視為解決問題
- 發現程式外觀和整體結構的後果
- 解釋程式中變數的錯誤使用
- 避免在使用條件語句和迴圈時的壞習慣和常見錯誤
- 了解不良錯誤處理如何導致不穩定的程式
- 避免與物件導向程式設計特別相關的壞習慣
- 減輕無效和不充分的錯誤定位及測試的影響
這本書適合於：
那些擁有一些實際程式設計知識（至少能使用一種程式語言編程），但幾乎沒有或沒有專業經驗的人，他們希望能快速建立起來。他們要麼仍在接受軟體開發的培訓，要麼正處於程式設計職業的起步階段。他們最多有1-2年的專業經驗。
