1. Using vague words instead of precise ones
Many developers say thing, stuff, or it’s not working. This makes you sound unclear and unprofessional.
❌ "This thing is slow."
✅ "This algorithm has high time complexity."
✅ "This algorithm has high time complexity."
2. Misusing technical terms
Some developers mix up words like bug, error, and exception.
- Bug = flaw in logic/code.
- Error = problem detected during execution.
- Exception = specific error that can be handled.
- Error = problem detected during execution.
- Exception = specific error that can be handled.
3. Overusing jargon with non-technical people
Clients or beginners may not understand heavy jargon.
❌ "We need to optimize latency by refactoring asynchronous calls."
✅ "We need to make the app faster by improving how requests are handled."
✅ "We need to make the app faster by improving how requests are handled."
4. Mixing up singular and plural forms
Words like data, criteria, phenomena are often misused.
❌ "This datas are incorrect."
✅ "This data is incorrect."
✅ "This data is incorrect."
5. Using filler words unnecessarily
Words like basically, actually, literally weaken communication.
❌ "Basically, the code is broken."
✅ "The code throws an exception."
✅ "The code throws an exception."
📝 Quick Practice
Fix these sentences:
1. ❌ "The thing crashed again." → ✅ "The program crashed due to a memory leak."
2. ❌ "This data are wrong." → ✅ "This data is wrong."
3. ❌ "The error is a bug." → ✅ "The error was caused by a bug."
2. ❌ "This data are wrong." → ✅ "This data is wrong."
3. ❌ "The error is a bug." → ✅ "The error was caused by a bug."
0 Comments