Giter Club home page Giter Club logo

tips-for-becoming-a-lousy-developer's Introduction

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.

tips-for-becoming-a-lousy-developer's People

Contributors

joinedsenses avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.