tooyoung:shitcode

To generate bad code for code reviews, you can use a tool that applies anti-patterns like obfuscated variable names, mixed formatting, and silent failures to transform clean code into poor examples. This demonstrates what not to do in software development.

Common anti-patterns for teaching bad coding practices include obfuscated variable names, mixed naming styles, lack of comments, random language comments, silent failures, global variables, skipped type checks, unreachable code, and messy indentation.

Yes, you can transform existing JavaScript code into poorly written code by applying anti-patterns. This generates confusing and inefficient code, making it useful for training junior engineers on what to avoid during workshops.

You need to generate shitcode when you want to demonstrate poor coding practices for educational or entertainment purposes. It helps make code reviews more insightful by showing developers concrete examples of bad syntax and logic.

The best way to show junior engineers poor coding practices is to generate intentionally bad code using anti-patterns. Demonstrating obfuscated variables, nested conditionals, and silent failures provides clear examples of what to avoid.