Language Selection

English French German Italian Portuguese Spanish

12 Worst Insertions Inside Articles and Reviews

Filed under
Just talk

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.

9. Community
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.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

12 annoyances in articles

Well, thanks for the input, it's nice to know what annoys readers, but I have a problem with some of your statements.

One in particular I'd like to address is the Add a line "In my personal opinion..." when it's the case... Do not use "All Linux most have..."

That goes against one of the core rules of writing. It is poor form to use "In my personal opinion" or "In my opinion." I'm writing the article so of course it's my opinion - who else's would it be? It's one of the first things we are taught.

...Not that I haven't ever used it, but I know it's amateurish. It's a qualifier. It gets you off the hook. Cuts down on the negative and abusive comments sometimes. If someone uses that phrase, it usually signals uncertainty or potential controversy ahead.

You're right about the use of the sentence

You're right about the use of the sentence. It's not exactly what I meant. Not the use of the sentence, but the idea behind it. Your opinion is always personal and the person behind an article, before start to write, must understand that. Sometimes who is writing the review wishes to input an idea or opinion as an universal and unique true, that can be very annoying.

PS.01. I like a lot your reviews and articles. You are not lazy to try and test every aspect before write the review.

PS.02. There are several articles written just after few minutes using an application or distribution. Another annoyance.

An Example...

Just an example. I was searching for a small and good wireless interface when I found a review of Wicd. I started to read and then the annoyance #1 appeared.. 'apt-get install blablabla'... I continued read about how Wicd is a simple, small and nice interface, but when I went to Wicd website I found it has a lot of dependencies. It can be a good interface, but the fact the writer used 'apt-get install' and forgot to say Wicd depends on Python, Dbus-python, Pygtk, PyObject and Pycairo, turned me off.

PS.03. List the dependencies when write about an application is very nice.

More in Tux Machines

Leftovers: Games

What is Linux?

Leftovers: OSS

  • ISS Federal Lead Rob Rogers on Agencies’ Open Source Moves & ‘Information Advantage’ Efforts
    ExecutiveBiz recently caught up with ISS Federal Systems Vice President Rob Rogers for this interview to discuss ongoing data-related trends in government and where he sees agencies prioritizing efforts in that arena, plus his ideas for how the government should approach open source methodology. [...] We have seen a significant shift in the past five years around agencies adopting and embracing open source methods. For one, open source technology is the primary catalyst behind some of the most significant progress related to the evolution of “big data” and analytic capabilities, which is used pervasively in the intelligence community. Certain agencies have contributed major projects to the open source community, which further solidifies their position on supporting open source. One notable example is NSA’s contribution of NiFi and Accumulo to the Apache Software Foundation in 2014. If these types of actions are an indicator of the direction that the IC agencies are heading in their support of open source, then the future is bright.
  • Davos 2017: China unites 25 countries to establish Global Blockchain Business Council
    On January 17, the governmental and industrial representatives from China and 25 other countries gathered in Davos, Switzerland for the Davos Forum. According to the latest update provided by Tai Cloud Corporation to EconoTimes, Jamie Elizabeth Smith, the former spokesperson and special assistant of the U.S. president Obama, announced that the Global Blockchain Business Council (GBBC) is formally established. The first national team members include senior executives of World Bank Mariana Dahan, former Estonian President Toomas Hendrik Ilves, former Prime Minister of Haidi Laurent Lamont, former Economy Minister of Ukraine Aivaras Abromavičius.
  • Intel's BigDL deep learning framework snubs GPUs for CPUs
    Last week Intel unveiled BigDL, a Spark-powered framework for distributed deep learning, available as an open source project. With most major IT vendors releasing machine learning frameworks, why not the CPU giant, too? What matters most about Intel's project may not be what it offers people building deep learning solutions on Spark clusters, but what it says about Intel’s ambitions to promote hardware that competes with GPUs for those applications.
  • Google's VR art app is open source and ready to get weird
    Google's Tilt Brush is capable of some pretty impressive results. But what if those 3D paintings and projects you made while strapped into virtual reality could escape into the real world?
  • How is your community promoting diversity?
    Open source software is a great enabler for technology innovation. Diversity unlocks innovation and drives market growth. Open source and diversity seem like the ultimate winning combination, yet ironically open source communities are among the least diverse tech communities. This is especially true when it comes to inherent diversity: traits such as gender, age, ethnicity, and sexual orientation.
  • Walmart’s Contributions to Open Source
    You might first think about open source in the context of outstanding tools for lean startup companies, but open source also finds a welcome home in behemoth, established companies, such as Walmart. In this O’Reilly OSCON video interview with Walmart Lab’s Alex Grigoryan, learn how Walmart both benefits from and contributes back to open source. The key takeaway? Open source allows you to reuse software components in labor saving ways.
  • Librecore: Aiming To Be A Better Libre Spin Of Coreboot
    Librecore is a new project aiming to be a new Coreboot downstream with a focus remaining on providing fully-free system firmware. Separately, Minifree/Libreboot has been accused (and admitted by Leah Rowe) to not paying a vendor for a completed contract. Librecore was formed due to "[Libreboot lead developer Leah Rowe] alienating large portions of the community, plus the stagnant and hard to use libreboot firmware and build system." With Librecore, they are aiming to use industry-standard tools and build environments. Another different design decision is pursuing Petitboot as the payload for a more modern and useful interface over GRUB as a payload.
  • Use of open source software growing across telecom
    Open source software may still be a new model for the telecommunications industry, but it’s rapidly gaining traction as operators look to mimic computing world. While the open source community has quickly gaining ground in the computing space, the traditional telecommunications industry has a history of hardening its siloed approach to networking technology. This was especially apparent at a time when most mobile telecom networks were 2G-based, with 3G technology just coming online in more advanced markets.
  • Open Source Software: What Every In-House Counsel Should Know
    Open source software (OSS) is ubiquitous in software development today, enabling technical innovation, productivity gains, and touching everything from big data and cloud to mobile and embedded. Control modules on the market today commonly include OSS components such as real-time operating systems, libraries, data interfaces, firmware, and display software.
  • 4 Common Open Source License Compliance Failures and How to Avoid Them
    Companies or organizations that don’t have a strong open source compliance program often suffer from errors and limitations in processes throughout the software development cycle that can lead to open source compliance failures. The previous article in this series covered common intellectual property failures. This time, we’ll discuss the four common open source license compliance failures and how to avoid them.

Docker 1.13, Containers, and DevOps

  • Introducing Docker 1.13
    Today we’re releasing Docker 1.13 with lots of new features, improvements and fixes to help Docker users with New Year’s resolutions to build more and better container apps. Docker 1.13 builds on and improves Docker swarm mode introduced in Docker 1.12 and has lots of other fixes. Read on for Docker 1.13 highlights.
  • Docker 1.13 Officially Released, Docker for AWS and Azure Ready for Production
    Docker announced today the general availability of Docker 1.13, the third major update of the open-source application container engine for GNU/Linux, macOS, and Microsoft Windows operating systems. Docker 1.13 has been in development for the past couple of months, during which it received no less than seven RC (Release Candidate) versions that implemented numerous improvements for the new Swarm Mode introduced in Docker 1.12, a few security features, as well as a new Remote API (version 1.25) and Client.
  • Distributed Fabric: A New Architecture for Container-Based Applications
    There’s a palpable sense of excitement in the application development world around container technology. Containers bring a new level of agility and speed to app development, giving developers the ability to break large monolithic apps into small, manageable microservices that can talk to one another, be more easily tested and deployed, and operate more efficiently as a full application. However, containers also demand a new architecture for the application services managing these microservices and apps, particularly in regards to service discovery — locating and consuming the services of those microservices.
  • DevOps trends emerging for 2017 and beyond
    Finally, one of the biggest trends for 2017 will not be just a focus on engaging and implementing some of these DevOps best practices into your enterprise, but a sweeping adoption of the DevOps/agile culture. This is because one of the most important – if not the absolute most key –tenets to a successful DevOps organization is culture. The enterprises that most espouse the shared responsibility, the empowered autonomous teams, the can-do attitudes, and the continuous learning environment in which DevOps thrives will see the biggest benefits.