Why automation with low code environments helps your peers

In my professional life, I transitioned to automation in low-code environments like #PowerAutomate and, more recently, SOAR platforms such as #Turbine from #Swimlane, moving away from using PowerShell scripts. The user interfaces provided by these #low #code #environments make it easier to visualize the execution flow, which is particularly beneficial for non-technical users or civilian engineers. Additionally, these environments simplify the transfer of knowledge about specific automations to other users.

Previously, I was deeply invested in PowerShell, even adopting object-oriented coding styles to optimize its usage. However, I encountered two significant challenges that held me back:

1. Database Usage

2. Knowledge Transfer

The first challenge was manageable with PowerShell, but there are other programming languages with better integrations that simplify database usage. However, the second challenge posed a greater obstacle. If I had adopted another language or started working extensively with databases, my code would have become even more complex, making it harder to transfer knowledge to my peers. This, in turn, would have made my tools niche products. While this could elevate my value as an expert, it could also create a gap between me and others, limiting collaboration and accessibility.

This is where low-code environments excel. They are accessible, offer numerous integrations, and make it easier for civilian engineers or superiors to understand your work. These environments bridge the gap, enabling engineers to create effective, UI-based code and work with databases through simple yet complex workflows.

Currently, my work revolves around Azure governance and asset inventories. I deploy general Azure policies via REST API and collect their states. These states are then used to either exempt resources and redeploy waivers back to Azure or, in later project stages, automate changes to resource settings.

Using #PowerShell and #Azure #DevOps, I initially developed a solution that worked quickly. However, with each iteration, the code became increasingly complex, creating a greater knowledge gap. This approach did not align with the company’s need for maintainable solutions that could be used by future generations of engineers.

While choosing low-code environments might feel like a step down for some engineers, it ultimately benefits the company by generalizing automation. In the long run, having more people involved in automation is far more valuable than relying on a few experts and dealing with a massive backlog.