Tips-For-Becoming-A-Lousy-Developer

This is a compiled list of suggestions on how to become a lousy developer in no time.

• Don't spend time researching or testing before asking questions.
• Don't even think about reading your error logs.
• If you get the urge to read errors, don't. Just copy-paste half of it and ask others for help.
• Ignore documentation and instructions.
• Try posting your message in multiple, unrelated discord channels for better visibility.
• Make sure to tag @everyone or admins to ensure qualified people see your message.
• If you don't get a reply within a few minutes, ask your question again.
• Be vague when asking to help. The less details, the better.
• If something unexpected happens, say only that it's "not working" or "broken". (No details!)
• Show as little code as possible. Someone might steal it.
• If you figured out a problem, don't tell others how you solved it.
• Don't take care of yourself, don't rest, don't take breaks, eat poorly, don't drink water.
• Resist learning from your mistakes.
• If you disagree with someones ideas or suggestions, call them gay.
• Delay updates for as long as possible.
• Don't ask about your actual problem, ask instead about how you're trying to solve it.
• Don't bother with documenting your code or making it readable.
• Never revisit old projects or try to improve them.
• Don't format your code
• If you run into a problem, brute force it until it works.
• Planning sucks. Don't do it. No diagrams, no notes, just get straight to work.
• Don't step through your own code and never add debug print messages.
• Use meaningless variable names or make them a single character (eg char x[])
• Get in the habit of copy-pasting everything and don't spend time understanding what the code does.
• Don't make back ups.
• Don't waste your time trying to learn git, version control, or how to make repositories.
• Push all changes directly to production or commit directly to master without testing anything to save time.
• The less testing you do, the less bugs there are.
• Stick with using just a basic text editor such as notepad.
• Ignore compilation warnings.