Short bio: Computer Scientist, FOSS supporter (read more)
Tux Machines (TM)-specific
Everyone likes a top list. This one can make people hate them, after all writers do not like critics. This is less a top list than an advice. Please, do not occur in the same mistake listed here. Everytime I started to read a review or article I ask myself how many of these annoying inserts I will find.
The top twelve most annoying insertions inside a review are, in other of annoyance:
1. Apt-get install something
YES, the world does not revolves around the sun, just around the Debian/Ubuntu based distributions. Perhaps before include apt-get anything remember those hundreds distributions that do not use apt-get.
2. The same but for other package manager and make install
One of worst error people input to beginners is the use of make install. DO NOT ever use make install. You have to build a package to control your system. So, apt-get is the worst, make install and other manager commands follow it.
3. Where I found the source?
Most apt-get fans forget to add where to find the source. Source is important.
4. Sudo what?
Do NOT use sudo everytime. Only root can have total control of the system, before try use sudo, learn more about the command and test as root. Do not add sudo command lines to your article as well. Sudo does not make
your system more secure.
5. Something is wrong... bad system... bad system
Sometimes if something is wrong the fault is yours and not of the system. Try understand what happens before start to blame the system, perhaps you are not using it well. Also try to search if the bug or problem is known and if there is a solution.
6. Personal opinions
Personal opinions are almost necessary to all articles, but they most apper like personal opinion. Add a line "In my personal opinion..." when it's the case... Do not use "All Linux most have..."
7. Something is missing
This is mostly applied to livecds. Of course something is missing, they are small system, try see if the missing feature can be included by downloading a package.
8. Everybody loves, I will too
You have your own voice. Do not start to tell the world you like something only because most like it. If something is wrong, tell about and do not hide it. It's not about fasion, it's not about be like others.
Community is importante, but you must consider the job of the developer team. Community can help but cannot be
guilty about anything around the system or application, aside the fact it can be annoying defending it. If during write your article some member of the community treats you not well, explain it was not an attack from who really works in the development.
10. Gnome versus Kde
Try not be part of the Kde against Gnome war. When you write a review about a Gnome/Kde application, do not try make the similar of the other desktop environment a bad choice.
11. The article does not finish the job
The world will be a good place if some of the critics could help to solve the issues. After write an article, or even before, try be part of the problem, try collaborate to solve the issues you found, then try add some comments about solutions you got later.
12. All the world, but developers
If you write an article about an application or distribution, let the developer team know about it. The article can help them to solve and understand their work better. It's nice read comments of the developers when we read an article.