unmaintainable-code VS FuckIt.py

Many useful lessons can be learned on what not to do: https://github.com/Droogans/unmaintainable-code

Reminds me a bit of this old gem - How To Write Unmaintainable Code

I think it can be true for coding, but in this line of work some people can output in 2 hours and 50 mins what other people require a week to do. Also it is possible for someone to create more work through their actions - a sort of anti-work (not to be confused with the subreddit). Sometimes the anti-work can create entire worker-years of work. Actually, anti-work is sort of an art form - here is a guide: https://github.com/Droogans/unmaintainable-code

This is the future of the classic essay 'How to write unmaintainable code': https://github.com/Droogans/unmaintainable-code

Two thoughts:

* This is ridiculous. Why would you do this? Which made think of this quote: "Which is ridiculous and unnecessary but when has that ever stopped programmers?" from one of my favorite Tom Scott videos: https://www.youtube.com/watch?v=gocwRvLhDf8

* How to Write Unmaintainable Code: https://github.com/Droogans/unmaintainable-code

My go-to is this one: https://github.com/Droogans/unmaintainable-code

Here's a handy style guide for how to write proper code.

Traditionally, you import a package and then use things from it to do a task. However, it is actually possible to have the import itself do stuff; I used this technique in python_ms to replicate the original JS module down to its import. And fuckit did it way before that.

"Hot programmer girls in your area, click here to get an invite to their private repositories. 😏😏😏😏😏"

Someone already made it for you: https://github.com/ajalt/fuckitpy