<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://bridgetownrb.com/" version="1.2.0">Bridgetown</generator><link href="https://andrewmcodes.dev/feed/projects.xml" rel="self" type="application/atom+xml" /><link href="https://andrewmcodes.dev/" rel="alternate" type="text/html" /><updated>2023-02-28T21:54:46-07:00</updated><id>https://andrewmcodes.dev/feed/projects.xml</id><title type="html">Andrew Mason | Projects</title><subtitle>Andrew Mason is a senior full stack software engineer, content creator, and Rubyist. Currently a senior product developer at Podia based in Phoenix, Arizona.</subtitle><author><name>Andrew Mason</name></author><entry><title type="html">dishwasher</title><link href="https://andrewmcodes.dev/projects/dishwasher/" rel="alternate" type="text/html" title="dishwasher" /><published>2020-12-31T15:03:05-07:00</published><updated>2020-12-31T15:03:05-07:00</updated><id>repo://projects.collection/_projects/dishwasher.md</id><content type="html" xml:base="https://andrewmcodes.dev/projects/dishwasher/">&lt;h2 id=&quot;usage&quot;&gt;Usage&lt;/h2&gt;

&lt;p&gt;To get started with dishwasher, simply install the gem and run the command &lt;code&gt;dishwasher&lt;/code&gt; and follow the prompts. It will then show you a list of all available forked repositories for that repository or user and give you the option to delete the forked repositories of your choice.&lt;/p&gt;

&lt;h2 id=&quot;backstory&quot;&gt;Backstory&lt;/h2&gt;

&lt;p&gt;When I was first getting into open source, I found the amount of forked repositories I had on GitHub was making it hard to browse my projects, so I decided to create a solution to automate the process of deleting forked repositories. That’s when I wrote the dishwasher gem. It uses the GitHub API to let you quickly and easily delete forked repositories, so you can keep your GitHub profile organized and up to date.&lt;/p&gt;</content><author><name>Andrew Mason</name></author></entry><entry><title type="html">Rails Extension Power Pack</title><link href="https://andrewmcodes.dev/projects/rails-extension-power-pack/" rel="alternate" type="text/html" title="Rails Extension Power Pack" /><published>2020-12-31T15:03:05-07:00</published><updated>2020-12-31T15:03:05-07:00</updated><id>repo://projects.collection/_projects/rails-extension-power-pack.md</id><content type="html" xml:base="https://andrewmcodes.dev/projects/rails-extension-power-pack/">&lt;h2 id=&quot;usage&quot;&gt;Usage&lt;/h2&gt;

&lt;p&gt;Install the extension pack from the &lt;a href=&quot;https://marketplace.visualstudio.com/items?itemName=andrewmcodes.rails-extension-power-pack&quot;&gt;Visual Studio Marketplace&lt;/a&gt; or &lt;a href=&quot;https://open-vsx.org/extension/andrewmcodes/rails-extension-power-pack&quot;&gt;Open VSX&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you find the extension pack helpful, &lt;a href=&quot;https://marketplace.visualstudio.com/items?itemName=andrewmcodes.rails-extension-power-pack&quot;&gt;consider leaving a rating on the Visual Studio Marketplace&lt;/a&gt; so that others can find it as well, thanks!&lt;/p&gt;

&lt;p&gt;A list of the extensions can be found in the README in text form, and can be seen visually if you search for the extension in VS Code.&lt;/p&gt;

&lt;h2 id=&quot;backstory&quot;&gt;Backstory&lt;/h2&gt;

&lt;p&gt;I get asked about my VS Code setup often, but it changes a lot much like the rest of my environment so it’s been hard to convince myself to write more about it. While thinking about updating an old post, I realized that I wanted a way to easily link people to my favorite VS Code extensions for developing Ruby on Rails without having to write a new one every few months.&lt;/p&gt;

&lt;p&gt;After pruning my extensions, which I usually at least once a week, I used &lt;a href=&quot;https://andrewmcodes.dev/projects/rails-extension-power-pack/&quot;&gt;Paste&lt;/a&gt; to quickly collect all of my favorite extension ids in one list, generated a VS Code extension with yo, and pasted the list in the &lt;code&gt;package.json&lt;/code&gt; file. That was it(&lt;em&gt;if you don’t count the time I spent building a workflow to automatically publish to Open VSX and VS Marketplace&lt;/em&gt;).&lt;/p&gt;

&lt;p&gt;I have closed the issues for now but the discussions board is open and that is where you can suggest new plugins, debate the need for existing ones, etc. As the description of the package says, these are MY favorite extensions so ultimately I want to keep it as close to what I am using as possible. If I missed your favorite extension, hop into the discussions and convince me! 😄&lt;/p&gt;</content><author><name>Andrew Mason</name></author></entry></feed>