<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Experience on Coderrob</title><link>https://coderrob.com/tags/developer-experience/</link><description>Recent content in Developer Experience on Coderrob</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 05 Feb 2025 08:57:23 -0600</lastBuildDate><atom:link href="https://coderrob.com/tags/developer-experience/index.xml" rel="self" type="application/rss+xml"/><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><item><title>Technology Choice Matters</title><link>https://coderrob.com/posts/technology-choice-matters/</link><pubDate>Thu, 25 Aug 2022 11:34:00 -0500</pubDate><guid>https://coderrob.com/posts/technology-choice-matters/</guid><description>&lt;p&gt;Developers need consistency in the tools they use, as well as a clear understanding of what is expected of them to be productive and successful in their roles. These tools not only impact productivity but also play a pivotal role in shaping the professional and personal well-being of developers.&lt;/p&gt;
&lt;p&gt;As team sizes grow, restructures occur, or new team members are added, it becomes crucial to have a consistent set of tools and technologies that everyone is expected to use.&lt;/p&gt;</description></item></channel></rss>