<?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: Alex Carter</title>
    <description>The latest articles on DEV Community by Alex Carter (@alexopengrid).</description>
    <link>https://dev.to/alexopengrid</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3028797%2F3d6f8873-c364-46ee-8841-7ebe3f05eee1.jpg</url>
      <title>DEV Community: Alex Carter</title>
      <link>https://dev.to/alexopengrid</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alexopengrid"/>
    <language>en</language>
    <item>
      <title>How to List Things in Markdown (Properly)</title>
      <dc:creator>Alex Carter</dc:creator>
      <pubDate>Wed, 09 Apr 2025 06:13:17 +0000</pubDate>
      <link>https://dev.to/alexopengrid/how-to-list-things-in-markdown-properly-54i2</link>
      <guid>https://dev.to/alexopengrid/how-to-list-things-in-markdown-properly-54i2</guid>
      <description>&lt;p&gt;Most Markdown tutorials show the basics, &lt;code&gt;-&lt;/code&gt; for bullets, &lt;code&gt;1.&lt;/code&gt; for steps - but miss the nuances that make your lists clean, readable, and platform-safe.&lt;/p&gt;

&lt;p&gt;Here’s a quick look at two things most people get wrong:&lt;/p&gt;

&lt;h3&gt;
  
  
  Using &lt;code&gt;1.&lt;/code&gt; for Every Step (Yes, Really)
&lt;/h3&gt;

&lt;p&gt;You can write:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="p"&gt;1.&lt;/span&gt; Wake up
&lt;span class="p"&gt;1.&lt;/span&gt; Make coffee
&lt;span class="p"&gt;1.&lt;/span&gt; Write code
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And it renders as:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Wake up
&lt;/li&gt;
&lt;li&gt;Make coffee
&lt;/li&gt;
&lt;li&gt;Write code&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This trick makes your Markdown easier to maintain - especially when you reorder or copy steps.&lt;/p&gt;




&lt;h3&gt;
  
  
  Nested Lists That Don’t Break
&lt;/h3&gt;

&lt;p&gt;To nest properly, indent using &lt;strong&gt;2 or 4 spaces&lt;/strong&gt;, not tabs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; Groceries
&lt;span class="p"&gt;  -&lt;/span&gt; Fruit
&lt;span class="p"&gt;    -&lt;/span&gt; Apples
&lt;span class="p"&gt;  -&lt;/span&gt; Vegetables
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Many Markdown renderers (especially in static sites) will choke on tabs or inconsistent spacing.&lt;/p&gt;




&lt;p&gt;Want to see every type of list Markdown supports (including checkboxes, edge cases, and weird platform behavior)?&lt;/p&gt;

&lt;p&gt;Full guide here: &lt;a href="https://opengridlab.org/guides/how-to-list-things-in-markdown.html" rel="noopener noreferrer"&gt;https://opengridlab.org/guides/how-to-list-things-in-markdown.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Covers all 7 list types with examples - including task lists, description lists, and nested code.&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>productivity</category>
      <category>linux</category>
      <category>writing</category>
    </item>
    <item>
      <title>Faster Shell, Calmer Brain: Three Terminal Tweaks I Can’t Live Without</title>
      <dc:creator>Alex Carter</dc:creator>
      <pubDate>Tue, 08 Apr 2025 06:49:27 +0000</pubDate>
      <link>https://dev.to/alexopengrid/faster-shell-calmer-brain-three-terminal-tweaks-i-cant-live-without-4hpg</link>
      <guid>https://dev.to/alexopengrid/faster-shell-calmer-brain-three-terminal-tweaks-i-cant-live-without-4hpg</guid>
      <description>&lt;p&gt;Every time I start fresh on a new machine, I make the same three changes to the terminal. Not because I’m obsessive (I am), but because these tweaks keep me sane. They make the shell fast, quiet, and actually useful.&lt;/p&gt;

&lt;p&gt;This isn’t about themes or plugins or trying to make your terminal look like a dashboard. It’s about clarity, calm, and getting out of your own way.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. A Fast, Informative Prompt
&lt;/h2&gt;

&lt;p&gt;The default &lt;code&gt;PS1&lt;/code&gt; is fine, but I want a prompt that tells me where I am without trying to be clever. I don’t need the time, username, or hostname on every line. Just the working directory and maybe a subtle color cue.&lt;/p&gt;

&lt;p&gt;Here’s my go-to:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;export PS1="\[\e[32m\]\w\[\e[m\] \$ "
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It gives me the current path in green and ends with a clean &lt;code&gt;$&lt;/code&gt;. That’s it. No lag, no clutter.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Smarter Shell History
&lt;/h2&gt;

&lt;p&gt;Shell history is one of the most underused tools in the terminal. By default, it’s noisy, redundant, and easily lost. These lines fix that:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;export HISTCONTROL=ignoredups:erasedups 
export HISTSIZE=10000
export HISTFILESIZE=20000 
shopt -s histappend
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;Removes duplicate entries
&lt;/li&gt;
&lt;li&gt;Keeps a deep backlog
&lt;/li&gt;
&lt;li&gt;Appends history across sessions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now when I hit &lt;code&gt;Ctrl+R&lt;/code&gt;, I actually get what I’m looking for.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Silence on Startup
&lt;/h2&gt;

&lt;p&gt;No banners. No motd. No last login message. No fortune telling me to seize the day.&lt;/p&gt;

&lt;p&gt;I just want a prompt, not a performance.&lt;/p&gt;

&lt;p&gt;Here’s the quickest fix:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;touch ~/.hushlogin
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If I’m using &lt;code&gt;zsh&lt;/code&gt;, I also comment out anything noisy in &lt;code&gt;.zshrc&lt;/code&gt; — especially plugin managers or echo spam.&lt;/p&gt;

&lt;h2&gt;
  
  
  That’s It
&lt;/h2&gt;

&lt;p&gt;These aren’t flashy changes, but they buy me headspace every day. A fast prompt, a better memory, and a clean slate every time I open the terminal.&lt;/p&gt;

&lt;p&gt;You don’t need a spaceship prompt or 40 plugins. Sometimes less noise is the real upgrade.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Back to theming my terminal for the third time this week.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>productivity</category>
      <category>bash</category>
      <category>cli</category>
    </item>
    <item>
      <title>Hello, I’m Alex — I Write About the Open Web (and Weird Tools That Still Work)</title>
      <dc:creator>Alex Carter</dc:creator>
      <pubDate>Tue, 08 Apr 2025 06:20:06 +0000</pubDate>
      <link>https://dev.to/alexopengrid/hello-im-alex-i-write-about-the-open-web-and-weird-tools-that-still-work-2kgf</link>
      <guid>https://dev.to/alexopengrid/hello-im-alex-i-write-about-the-open-web-and-weird-tools-that-still-work-2kgf</guid>
      <description>&lt;p&gt;I figured I'd kick things off with something simple.&lt;/p&gt;

&lt;p&gt;I'm &lt;strong&gt;Alex Carter&lt;/strong&gt; — an independent tech writer, open web advocate, and occasional builder of things that run mostly in the terminal. I write about how we interact with the web when it’s not trying to monetize our attention, and the tools that make it easier to own your workflow instead of renting it from five different SaaS platforms.&lt;/p&gt;

&lt;p&gt;Most of what I publish leans somewhere between:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Markdown obsession
&lt;/li&gt;
&lt;li&gt;Ethical scraping and automation
&lt;/li&gt;
&lt;li&gt;Browser quirks and privacy tools
&lt;/li&gt;
&lt;li&gt;Writing in public without shouting for attention&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I’m not here to go viral. I’m here because some of the most thoughtful, curious people I know are quietly posting brilliant things on Dev.to. I’d rather join that slow stream than yell into another algorithmic void.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Nice to meet you.&lt;/em&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
