<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Coderrob</title><link>https://coderrob.com/tags/automation/</link><description>Recent content in Automation on Coderrob</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 22 Feb 2025 17:04:43 -0600</lastBuildDate><atom:link href="https://coderrob.com/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Rethinking Enterprise Software Development: Embracing Automation Over Outdated Hierarchies</title><link>https://coderrob.com/posts/rethinking-enterprise-software-development-embracing-automation-over-outdated-hierarchies/</link><pubDate>Sat, 22 Feb 2025 17:04:43 -0600</pubDate><guid>https://coderrob.com/posts/rethinking-enterprise-software-development-embracing-automation-over-outdated-hierarchies/</guid><description>&lt;p&gt;For too long, legacy enterprise development has been constrained by a top-down model that stifles innovation and impedes progress. The conventional emphasis on individual developers paired with rigid managerial oversight is not only inefficient; it is counterproductive in today’s fast-paced, ever-evolving tech landscape.&lt;/p&gt;
&lt;p&gt;Drawing from my experience building automated code-review agents for enterprise applications, I have witnessed firsthand that current corporate development structures are fundamentally flawed. Rather than investing in isolated training programs or centralizing AI initiatives within a single division, the future lies in leveraging automation to transform enterprise software development into an agile, collaborative, and efficient process.&lt;/p&gt;</description></item><item><title>Streamlining GitHub Actions Development with Self-Documenting GitHub Actions</title><link>https://coderrob.com/posts/streamlining-github-actions-development-with-self-documenting-github-actions/</link><pubDate>Wed, 05 Feb 2025 08:57:23 -0600</pubDate><guid>https://coderrob.com/posts/streamlining-github-actions-development-with-self-documenting-github-actions/</guid><description>&lt;p&gt;In my recent project, I&amp;rsquo;ve focused on streamlining the development workflow for Cisco Collaboration by migrating thousands of repository build processes to GitHub Actions. This transition has brought numerous benefits in terms of automation and efficiency, but it also presented a challenge &lt;strong&gt;in keeping in-development GitHub Action documentation up-to-date&lt;/strong&gt; and ensuring consistency across all actions.&lt;/p&gt;
&lt;p&gt;One area that became a repetitive drain on productivity was documenting actions, specifically details like inputs, outputs, environment variable usage, and other metadata values of interest. &lt;strong&gt;The lack of consistency was the only consistency&lt;/strong&gt;; every existing and even newly created action had either no documentation, or had its own unique way to document the action.&lt;/p&gt;</description></item></channel></rss>