state-of-the-art-shitcode
state-of-the-art-shitcode copied to clipboard
trekhleb
💩State-of-the-art shitcode principles your project should follow to call it a proper shitcode
Always write comments in languages that are rarely used among team members. So that members can identify who wrote the code easily. For example: - Always use Elvish if you...
I followed all the principles of this repository, and yet my game is very laggy and uses a lot of CPU and RAM. I don't think I can optimize my...
I know it's a ironical project, but I have question whether to write comments in native language. Using Chinese will has trouble shifting input method, and it would lead to...
Nowadays many things support complex variable names. So why not name them in your native language? That saves your time thinking of a name, and time is important. Good :thumbsup:...
Just a thought, what will happen when shitcode meets EE. There's [FizzBuzzEnterpriseEdition](https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition) showing us how over-engineering and cargo cult would devastate your codebase in a hurmorous way. It comes to...
in browser Console, {} + [] the result is 0, because browser think '{}' is code block, add () like ({} + []), it will return real result. this is...
