Karl Beecher – författare

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 LearnBecome a better coder by learning how (not) to programChoose your tools wiselyThink of programming as problem solvingDiscover the consequences of a program's appearance and overall structureExplain poor use of variables in programsAvoid bad habits and common mistakes when using conditionals and loopsSee how poor error-handling makes for unstable programsSidestep bad practices related specifically to object-oriented programmingMitigate the effects of ineffectual and inadequate bug location and testingWho This Book Is ForThose 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.

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 maximumchaos.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 LearnBecome a better coder by learning how (not) to programChoose your tools wiselyThink of programming as problem solvingDiscover the consequences of a program’s appearance and overall structureExplain poor use of variables in programsAvoid bad habits and common mistakes when using conditionals and loopsSee how poor error-handling makes for unstable programsSidestep bad practices related specifically to object-oriented programmingMitigate the effects of ineffectual and inadequate bug location and testingWho This Book Is ForThose 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.

Computational thinking is a timeless, transferable skill that enables you to think more clearly and logically, as well as a way to solve specific problems. Beginning with the core ideas of computational thinking, with this book you'll build up an understanding of the practical problem-solving approach and explore how computational thinking aids good practice in programming, complete with a full guided example.

Computational thinking is a timeless, transferable skill that enables you to think more clearly and logically, as well as a way to solve specific problems. Beginning with the core ideas of computational thinking, with this book you''ll build up an understanding of the practical problem-solving approach and explore how computational thinking aids good practice in programming, complete with a full guided example.

Computational thinking is a timeless, transferable skill that enables you to think more clearly and logically, as well as a way to solve specific problems. Beginning with the core ideas of computational thinking, with this book you''ll build up an understanding of the practical problem-solving approach and explore how computational thinking aids good practice in programming, complete with a full guided example.

This book flips the script of generic programming manuals, using humor to teach by bad example. Discover how to become the world’s worst programmer and build bad habits that lead to buggy, poorly written code.Do you dream of writing code that gets instantly rejected in review? Do you look forward to reading feedback plastered in comments like "WTF???" Do you hope your bug-ridden changes sneak through and wreak havoc in the codebase? If your goal is to build a reputation for writing creaky, messy, error-prone code that drives your teammates up the wall, Bad Programming Practices 101 is here to help.Alternatively, you could use this book to identify those bad habits and learn to avoid them. It covers topics like the foundations of programming (layout, variables, loops, and modules) and is revised with a NEW chapter on how NOT to use AI for writing code. It’s been said that you need to write 10,000 lines of bad code before becoming a good programmer. This book helps you to fill that quota while truly understanding the “why” behind best practices.What You Will Learn: Become a better coder by learning how (not) to programChoose your tools wiselyThink of programming as problem solvingDiscover the consequences of a program’s appearance and overall structureExplain poor use of variables in programsAvoid bad habits and common mistakes when using conditionals and loopsSee how poor error-handling makes for unstable programsSidestep bad practices related specifically to object-oriented programmingMitigate the effects of ineffectual and inadequate bug location and testingLearn how to avoid sabotaging your code with misuse of AI tools 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.