# State-of-the-Art Shitcode Principles [![State-of-the-art Shitcode](https://img.shields.io/static/v1?label=State-of-the-art&message=Shitcode&color=7B5804)](https://github.com/trekhleb/state-of-the-art-shitcode) This a list of state-of-the-art shitcode principles your project should follow. ## Get Your Badge If your repository follows the state-of-the-art shitcode principles you may use the following "state-of-the-art shitcode" badge: ``` [![State-of-the-art Shitcode](https://img.shields.io/static/v1?label=State-of-the-art&message=Shitcode&color=7B5804)](https://github.com/trekhleb/state-of-the-art-shitcode) ``` ## The Principles ### πŸ’© Name variables in a way as if your code was already obfuscated Less keystrokes, more time for you. _Good πŸ‘πŸ»_ ```javascript let a = 42; ``` _Bad πŸ‘ŽπŸ»_ ```javascript let age = 42; ``` ### πŸ’© Mix variable/functions naming style Celebrate the difference. _Good πŸ‘πŸ»_ ```javascript let wWidth = 640; let w_height = 480; ``` _Bad πŸ‘ŽπŸ»_ ```javascript let windowWidth = 640; let windowHeight = 480; ``` ### πŸ’© Never write comments No one is going to read your code anyway. _Good πŸ‘πŸ»_ ```javascript const cdr = 700; ``` _Bad πŸ‘ŽπŸ»_ ```javascript // Callback function debounce rate in milliseconds. const callbackDebounceRate = 700; ``` ### πŸ’© Always write comments in your native language If you violated the "No comments" principle then at least try to write comments in a language that is different from the language you use to write the code. If your native language is English you may violate this principle. _Good πŸ‘πŸ»_ ```javascript // Π—Π°ΠΊΡ€ΠΈΠ²Π°Ρ”ΠΌΠΎ модальнС Π²Ρ–ΠΊΠΎΠ½Π΅Ρ‡ΠΊΠΎ ΠΏΡ€ΠΈ Π²ΠΈΠ½ΠΈΠΊΠ½Π΅Π½Π½Ρ– ΠΏΠΎΠΌΠΈΠ»ΠΊΠΈ. toggleModal(false); ``` _Bad πŸ‘ŽπŸ»_ ```javascript // Hide modal window on error. toggleModal(false); ``` ### πŸ’© Try to mix formatting style as much as possible Celebrate the difference. _Good πŸ‘πŸ»_ ```javascript let i = ['tomato', 'onion', 'mushrooms']; let d = [ "ketchup", "mayonnaise" ]; ``` _Bad πŸ‘ŽπŸ»_ ```javascript let ingredients = ['tomato', 'onion', 'mushrooms']; let dressings = ['ketchup', 'mayonnaise']; ``` ### πŸ’© Put as much code as possible into one line _Good πŸ‘πŸ»_ ```javascript document.location.search.replace(/(^\?)/,'').split('&').reduce(function(o,n){n=n.split('=');o[n[0]]=n[1];return o},{}) ``` _Bad πŸ‘ŽπŸ»_ ```javascript document.location.search .replace(/(^\?)/, '') .split('&') .reduce((searchParams, keyValuePair) => { keyValuePair = keyValuePair.split('='); searchParams[keyValuePair[0]] = keyValuePair[1]; return searchParams; }, {} ) ``` ### πŸ’© Fail silently Whenever you catch an error it is not necessary for anyone to know about it. No logs, no error modals, chill. _Good πŸ‘πŸ»_ ```javascript try { // Something unpredictable. } catch (error) { // tss... 🀫 } ``` _Bad πŸ‘ŽπŸ»_ ```javascript try { // Something unpredictable. } catch (error) { setErrorMessage(error.message); // and/or logError(error); } ``` ### πŸ’© Use global variables extensively Globalization principle. _Good πŸ‘πŸ»_ ```javascript let x = 5; function square() { x = x ** 2; } square(); // Now x is 25. ``` _Bad πŸ‘ŽπŸ»_ ```javascript let x = 5; function square(num) { return num ** 2; } x = square(x); // Now x is 25. ``` ### πŸ’© Create variables that you're not going to use. Just in case. _Good πŸ‘πŸ»_ ```javascript function sum(a, b, c) { const timeout = 1300; const result = a + b; return a + b; } ``` _Bad πŸ‘ŽπŸ»_ ```javascript function sum(a, b) { return a + b; } ``` ### πŸ’© You need to have an unreachable piece of code This is your "Plan B". _Good πŸ‘πŸ»_ ```javascript function square(num) { if (typeof num === 'undefined') { return undefined; } else { return num ** 2; } return null; // This is my "Plan B". } ``` _Bad πŸ‘ŽπŸ»_ ```javascript function square(num) { if (typeof num === 'undefined') { return undefined; } return num ** 2; } ``` ### πŸ’© Triangle principle Be like a bird - nest, nest, nest. _Good πŸ‘πŸ»_ ```javascript function someFunction() { if (condition1) { if (condition2) { asyncFunction(params, (result) => { if (result) { for (;;) { if (condition3) { } } } }) } } } ``` _Bad πŸ‘ŽπŸ»_ ```javascript async function someFunction() { if (!condition1 || !condition2) { return; } const result = await asyncFunction(params); if (!result) { return; } for (;;) { if (condition3) { } } } ``` ### πŸ’© Do not lock your dependencies Update your dependencies on each new installation in uncontrolled way. Why stick to the past, let's use the cutting edge libraries versions. _Good πŸ‘πŸ»_ ``` $ ls -la package.json ``` _Bad πŸ‘ŽπŸ»_ ``` $ ls -la package.json package-lock.json ``` ### πŸ’© Avoid covering your code with tests This is a duplicate and unnecessary amount of work. ### πŸ’© As hard as you can try to avoid code linters Write code as you want, especially if there is more than one developer in a team. This is a "freedom" principle. ### πŸ’© Start your project without a README file. And keep it that way for the time being.