Uses for Automation

-

Scripts can be used for automating specific tasks. Automation replaces repetitive manual steps with processes that happen automatically. Humans are fallible—they can become tired, make mistakes, fail to follow instructions, and be inconsistent in their job performance. In contrast, automated processes complete instructions exactly as coded, in a consistent manner. They can run 24 hours a day, every day, without tiring. For many tasks suitable for automation, it can be more cost-effective than human labor.

Appropriate Uses for Automation

  • The automatic timing and regulation of traffic lights
  • A repetitive task at high risk for human error
  • Sending commands to a computer
  • Detecting and removing duplicates of data
  • Sending automated emails that are personalized by pulling individual names from a database and plugging them into the email
  • Updating a large number of file permissions
  • Reporting on system data, like disk or memory usage
  • Installing software
  • Generating reports
  • Deploying a file or a computer program to all computers on a company network
  • Using a configuration management system to deploy software patches after a human has designed the system
  • Populating an e-commerce site with products
  • Setting the home directory and access permissions for users

Automation is Not Always an Appropriate or Complete Solution

Automation cannot perform all human work. Tasks that require human creativity, social connection, psychology, flexibility, ingenuity, evaluation, and/or complex analytic work are not good candidates for full automation. Sometimes automation can handle certain subtasks, but human intervention is required to complete the larger task. The following are examples of tasks that cannot or should not be fully automated:

  • Items That Require Human Evaluation and Analytic Skills:

    • Designing a configuration management system
    • Investigating and troubleshooting all end-user problems
    • Writing a computer program
    • Building a new startup business

  • Items That Require Human Creativity and/or Aesthetic Judgment:

    • Designing an attractive webpage (AI can do this, but simple automation cannot)
    • Wedding photography
    • Haircuts and styling

  • Items That Cannot Be Automated Due to Basic Physics:

    • Troubleshooting or repairing machines that cannot power on or boot up

  • Items That Need Human Interaction, Psychology, and/or Evaluation Skills:

    • Interviewing and hiring new employees
    • Customer service (chatbots cannot address every customer service need)

  • Items That Should Not Be Fully Automated Due to Costs and Safety:

    • Grocery store checkout process, including bagging groceries
    • Tasks that are less expensive to perform manually

Artificial Intelligence

It is important to understand that basic automation is not the same as artificial intelligence (AI). Automation involves explicitly instructing a machine on how to perform a task. AI, on the other hand, involves training a computing machine to perform complex tasks through a process called machine learning. This allows AI to perform new tasks without human intervention in programming explicit instructions for each task. Although AI can automate human tasks, it is much more complex than basic automation.

Comments

Post a Comment

Popular posts from this blog

Installing the Certbot Let’s Encrypt Client for NGINX on Amazon Linux 2

-
Image
Installing the Certbot Let’s Encrypt Client The certbot package is not available through the package manager by default. You will need to enable the  EPEL  repository to install Certbot. sudo yum install epel-release sudo yum install certbot-nginx Set Up NGINX certbot  can automatically configure  NGINX  for SSL/TLS. It looks for and modifies the server block in your  NGINX  configuration that contains a server_name directive with the domain name you’re requesting a certificate for. In our example, the domain is  www.mydomain.com . Assuming you’re starting with a fresh NGINX install, use a text editor to create a file in the  /etc/nginx/conf.d  directory named  domain_name.conf  (so in our example, www.mydomain.com.conf). Specify your domain name (and variants, if any) with the  server_name  directive: server { listen 80 default_server; listen [::]:80 default_server; root /var/www/html; server_name myd...
Read more

psql: error: connection to server at "localhost" (127.0.0.1), port 5433 failed: ERROR: failed to authenticate with backend using SCRAM DETAIL: valid password not found

-
Image
ERROR psql: error: connection to server at "localhost" (127.0.0.1), port 5433 failed: ERROR: failed to authenticate with backend using SCRAM DETAIL: valid password not found Since Pgpool-II is a PostgreSQL proxy that works between clients and PostgreSQL servers, the authentication comprises two steps: Authentication between client and Pgpool-II Authentication between Pgpool-II and PostgreSQL servers Starting with Pgpool-II 4.0, Pgpool-II supports scram-sha-256 authentication. scram-sha-256 authentication method is strongly recommended because it is the most secure password-based authentication method. Solution 1 If PostgreSQL servers require  MD5  or  SCRAM  authentication for some user’s authentication but the password for that user is not present in  pool_passwd , then enabling  allow_clear_text_frontend_auth  will allow the  Pgpool-II  to use clear-text-password authentication with user to get the password in plain text form from the user ...
Read more

Automate PostgreSql Backup with Cron

-
  Create The  Postgres Password File The file  .pgpass  in a user’s home directory can contain passwords to be used if the connection requires a password (and no password has been specified otherwise). On Microsoft Windows the file is named  %APPDATA%\postgresql\pgpass.conf  (where  %APPDATA%  refers to the Application Data subdirectory in the user’s profile). Alternatively, the password file to use can be specified using the connection parameter passfile or the environment variable  PGPASSFILE . Let’s see if the  postgres user  already has a password: sudo -u postgres psql select * from pg_authid; If  rolpassword  is empty, set the password: ALTER USER postgres PASSWORD 'mypassword'; \q Create  .pgpass vim ~/.pgpass # Add the following line # hostname:port:database:username:password localhost:*:*:postgres:[password] Add Environment variable  PGPASSFILE export PGPASSFILE= '/root/.pgpass' vim /etc/environment ...
Read more