15 Terrible Advice for Web Developers

Medium is full of useful articles and great advice to create robust and maintainable applications. But what If you don't like your colleagues and want to ruin their day? Then worry no more. I’m great at giving bad advice and came up with 15 tips to cause frustration and waste everyone's time.

1. Abstraction Layers

Use as many abstraction layers as possible until:

  • The code is difficult to understand and debug.
  • It is difficult to make changes to the code.
  • The code is slow or inefficient.
  • The code is not reusable.

2. Always Request Changes on Pull Requests

You should always block a pull request during the first review to assert dominance.

Some ideas for change requests are:

  • Make a variable name longer
  • Make a variable name shorter
  • Rename a variable name
  • Make code more DRY

3. No Commit Messages

Good commit messages take time to write. Instead of spending your valuable time writing something like

[JIRA-1234] build: replace vue-cli with vite

you can use the following command to push your code with an empty commit message

git commit --allow-empty-message -m "" && git push --force

4. Use Magic Numbers

Use magic numbers often to indicate that you know exactly what you are doing

window.scrollTo({
  top: 89,
  left: 12,
  behavior: "smooth",
});

5. Mix Return Statements

Never let them know your next move by mixing the return statements of a function

function shouldPayTax(income) {
  if(income.amount < 20_000) {
    return false
  }
  if(income.amount > 20_000 && income.country == 'USA') {
    return true
  }
  if(income.country == 'Panama') {
    return false
  }
  if(this.totalWorkingHoursPerWeek > 60) {
    return true
  }
  if(income.amount > 20_000 && income.isCelebrity == true) {
    return false
  }
  if(income.amount > 20_000) {
    return true
  }
}

6. Typescript

If someone had the audacity to add TypeScript to the project, you can bypass type checking by using any everywhere.

Visit Now