state-of-the-art-shitcode

by trekhleb · Developer Tools

💩State-of-the-art shitcode principles your project should follow to call it a proper shitcode

New0 ratings6,199 starsActive
Developer ToolsDeveloper Toolbest-practicebest-practices
GitHub⚑ Report
state-of-the-art-shitcode — image 1

About this project

State-of-the-Art Shitcode Principles This a list of state-of-the-art shitcode principles your project should follow to call it a proper shitcode. Read this in other languages: 简体中文, 한국어 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: Markdown source-code for the badge: The Principles 💩 Name variables in a way as if your code was already obfuscated Fewer keystrokes, more time for you. Good 👍🏻 Bad 👎🏻 💩 Mix variable/functions naming style Celebrate the difference. Good 👍🏻 Bad 👎🏻 💩 Never write comments No one is going to read your code anyway. Good…

Technologies

best-practicescode-qualitybest-practice

Project health

Low recent activity
Last update9 months ago
Contributors7
Latest release
Open issues & PRs50
LicenseMIT
On GitHubsince 2020

GitHub

6,199
stars
333
forks
7
contributors
50
open issues & PRs
best-practice
language
9 months ago
last commit
View on GitHub ↗

Reviews

out of 5 · 0 ratings
★★★★★
0%
★★★★
0%
★★★
0%
★★
0%
0%
Sign in to write a review
No reviews yet
Be the first to review state-of-the-art-shitcode.

Built by

trekhleb
Imported from GitHub · not yet claimed on GitPalace
View developer pageSign in with GitHub to claim

Maintain trekhleb/state-of-the-art-shitcode? Claiming verifies admin access through your GitHub account and gives you control of this listing.

You might also like