Tag Archives: techops

The Role of Automation in Modern Software Development

July 6, 2024Techautomation, cicd, cloud, devops, paas, saas, sdlc, software, sysadmin, sysops, techopsHarout

Automation in the software development industry refers to the use of tools, scripts, and processes to perform repetitive tasks with minimal human intervention. It streamlines the software development lifecycle, including activities like code integration, testing, deployment, and monitoring. Automation helps to increase efficiency, reduce errors, and ensure consistency across all stages of development, ultimately leading to faster delivery of high-quality software. In this context, it becomes an integral part of modern development methodologies like DevOps and Continuous Integration/Continuous Deployment (CI/CD).

Continue reading →

Every Cloud Architecture

January 12, 2023Techcloudarchitecture, cloudcomputing, cloudnetworking, containers, dataanalytics, datalake, devops, devsecops, infrastructure, sysops, techopsHarout

Source: https://www.goodtechthings.com/every-cloud-architecture/

I recall a few environments that fit this narrative 🙂

Pipelines…

May 10, 2022Techconfigmgr, development, devops, devsecops, git, hudson, jenkins, legacy, oldschool, softwareengineering, sysadmin, techops, thinkoutsidetheboxHarout

About 12 years ago, we used a piece of software called Hudson to automate various tasks that were otherwise run by hand. Things like running backup jobs, initiating web server warm-ups, checking on stale DNS records, sending emails reports, executing shell scripts on remote servers, updating firewall rules during peak times of day (think home brew auto-scaling logic), and later on, integrating with Git repositories, and deploying code and config to servers in data-centers.

On a side note, did you know Jenkins used to be called Hudson? It has been around since 2005, and deploying code from Git is only one of the many many things it is otherwise used for by professionals.

Always think outside the box…

Automate all the things?

February 17, 2022Techautomateallthethings, automation, automationengineer, cloud, cloudcomputing, complexity, devops, techopsHarout

Look… we get it; it’s easy to get carried away with the “let’s automate this, let’s automate that, let’s automate everything!” enthusiasm.

Before you go ahead and commit your team to a ton of automation work spanning the foreseeable sprints, it is best to have a sit down with your leads and establish an outline of all domains in which automation makes sense, prioritize those where repetitive high-frequency tasks reside, reduce hours consumed by your in-house skill overwhelmed by running routine tasks, and work your way down that list.

The last thing any directive would want is for their team spending months on an automation build-out, only to no longer be needed due to product life-cycle deprecation.

The goal of automation is to simplify and streamline workflow, reduce overhead, and allow skill to be leveraged where it is needed most… and that is not, in troubleshooting automation complexity issues.