<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Eric Chen</title>
    <description>The latest articles on DEV Community by Eric Chen (@echen4628).</description>
    <link>https://dev.to/echen4628</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4030892%2F95a02538-9e9f-4413-a1b7-97c359e24aa0.png</url>
      <title>DEV Community: Eric Chen</title>
      <link>https://dev.to/echen4628</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/echen4628"/>
    <language>en</language>
    <item>
      <title>find command finds things</title>
      <dc:creator>Eric Chen</dc:creator>
      <pubDate>Wed, 15 Jul 2026 18:47:13 +0000</pubDate>
      <link>https://dev.to/echen4628/find-command-finds-things-506</link>
      <guid>https://dev.to/echen4628/find-command-finds-things-506</guid>
      <description>&lt;p&gt;Recently I learned: &lt;code&gt;find&lt;/code&gt; is a useful command to find files in your directories.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;find folder1 folder2 folder3
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This dumps every file and directory under those folders.&lt;/p&gt;

&lt;p&gt;It also supports flags such as &lt;code&gt;-name "*.txt"&lt;/code&gt; to find files matching a particular pattern. There are also filters for size, permissions, and last modified date.&lt;/p&gt;

&lt;p&gt;I'm thinking this would be a great tool for sanity-testing code that creates nested directories (like a new Docker container's filesystem). This command will give me a full flat listing of the resulting tree (like a deeply nested &lt;code&gt;ls&lt;/code&gt; command`).&lt;/p&gt;

&lt;p&gt;The downside is of course it can dump a lot of output, but in sanity-testing scenarios, there shouldn't be that many files anyways.&lt;/p&gt;

&lt;p&gt;Something interesting is that this command will take multiple folders before the flags. I'm used to thinking of programs where the arguments are all positionally ordered, so if you don't pass a flag it just assumes the next thing is a regular argument. In this case, &lt;code&gt;find&lt;/code&gt; checks whether an argument looks like a flag (starts with &lt;code&gt;-&lt;/code&gt;) before deciding whether to treat it as a path or as part of the expression. I wonder if this is a common pattern across other Linux commands. (Claude says &lt;code&gt;find&lt;/code&gt; is  special case, but I need to look more into this.)&lt;/p&gt;

</description>
      <category>todayilearned</category>
      <category>cli</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
