How do you tell someone their code is bad?

How do you tell someone their code is bad?

How do you tell someone their work sucks in a non-sucky way? The best way to do it is by asking questions and showing your colleague the respect you would want if the situation were reversed. By asking questions instead of immediately criticising their bad code, you prompt them to self-evaluate their coding practices.

How do you deal with a bad code review?

In short, reviews are a way to get team members to communicate about their code changes. So talk to the reviewer about it. IF it helps, talk in an impartial way, as if you were not even the author of the code being reviewed. The code belongs to the company or team after all, and the team will have to maintain it.

Is it okay to look at other peoples code?

Looking at some piece of code and copying it is bad but looking at a code snippet reading it, understanding it and implementing it in your own way is not. Try not to copy the codes from the web or any other source as you can get in a lot of trouble due to plagiarism.

Why you shouldn’t comment your code?

Good comments compliment your code, while bad ones pull readers away from the main points. Before putting any comments, ask yourself whether it would serve any purposes rather than distract people from comprehending your program. Good codes have rhythm while mediocre codes have a lot of pauses.

What makes a bad developer?

Bad developers don’t take ownership of their code; they don’t actively seek to grow their abilities, they’re not curious about new horizons, and they’re unwilling to recognize and learn from their mistakes.

How do you describe someone’s code?

Some things I find useful in dealing with this:

  1. Explain the code in the same language the users use.
  2. Explain the code using standard programmer terms, e.g. Terms like “buffer”, “list”, “singleton” are familiar to most of us, as are common mathematical terms.
  3. Explain what you’re doing in terms of the inputs and outputs.

Which coding technique makes a code hard to read and understand?

A tool called an obfuscator will automatically convert straightforward source code into a program that works the same way, but is more difficult to read and understand. Unfortunately, malicious code writers also use these methods to prevent their attack mechanisms from being detected by antimalware tools.

Why is no code bad?

The most common problem with no or low code platforms is that, for more complex use cases, they are too rigid and restrictive to produce the desired results. No code platforms work by locking certain blocks of code into visual components that a business user can manipulate.