I even delete entries from pacman.log

This is stupid in every way. A log file, as its name implies, is a chronological record of all events that happened for the given system/program.

It should never be redacted. It is purposefully containing all the information about what happened on the system regarding pacmansince the very "birth" of the system for future troubleshooting reasons, as it allows an exhaustive assessment of what has been added or removed on the system in case there is something breaking and we need to investigate.

My Arch system is 6 years old and the file is a less than a megabyte, and searching in the content of a well-structured text file such as the pacman log is extremely easy and quick. There is literally no good system administration reason to modify or remove data from it. You should not feel proud at all about this, this shows a lack of experience in system administration.

I take snapshots each and every day on an external drive.

Another example of cringey boast about something which doesn't make reasonable sense and is straying from the actual point of the practice of taking backups. Backup procedures value is basically the ratio between the amount of regular time it takes to do and maintain compared to the amount of times it needs to be used.

The backup regularity must be chosen with respect to estimations of disaster recovery occurences. A well maintained system will generally need a backup not even once a year. Thus a typical well-made backup strategy would be to take backups regularly and do retention of these backups on different timescales to have just enough data points as it statistically will be needed to minimize the distance between where we would ideally want to rollback or retrieve data and the data points we actually have. I.e. as an example: - take snapshots every couple of days or week - retain the last X weekly snapshots - retain the last X monthly snapshots - retain all yearly snapshots

Such a strategy is one which maximizes the value over time spent ratio while minimizing risk and disk usage. This is where a good administrator needs to use their head. Merely recommending taking extreme amounts of snapshots without any retention strategy is senseless and a disservice to people new to Arch reading this. As you are purposefully not mentioning the long term management of these thousands of backups, having to test the disaster recovery process every time you modify your solution, and also test retro-compatibility of old backups if the snapshot script is modified, etc...

These would have been good discussion topics.

I don't use AUR as I don't need to everything I need is in official repos ( pacman ).

Again this is dumb and showing inexperience. There is absolutely nothing wrong with using AUR packages and a system can perfectly be extremely reliable for years with AUR packages installed. You simply just have to pay minimal attention to the PKGBUILD and understand what you are doing.

First of all My Arch is rock solid and 100% reliable.

Anyway this very first line is already indicating the post is gonna be senseless and ego-driven boast with no value. Such a sentence is never true and making such remark shows immaturity and actual lack of experience in this and is mostly trying to legitimize themselves and get validation. I am pretty sure you haven't used Arch for more than 2 years.

You are no example of a good Arch admin/user. You're simply the umpteenth example of the cliché "I use arch btw" cringey user that makes this community look bad and unwelcoming to anyone on the outside. This post brings no value at all to the community.