<?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: Donalda Feith</title>
    <description>The latest articles on DEV Community by Donalda Feith (@donalda).</description>
    <link>https://dev.to/donalda</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%2F1836288%2F8f61439c-bc7e-40b9-901a-5f02b49efdd3.jpg</url>
      <title>DEV Community: Donalda Feith</title>
      <link>https://dev.to/donalda</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/donalda"/>
    <language>en</language>
    <item>
      <title>The 7-Minute Git Workflow That Keeps Me Sane (and My Repo From Looking Like a Crime Scene)</title>
      <dc:creator>Donalda Feith</dc:creator>
      <pubDate>Mon, 11 Aug 2025 01:35:09 +0000</pubDate>
      <link>https://dev.to/donalda/the-7-minute-git-workflow-that-saves-me-hours-every-week-j47</link>
      <guid>https://dev.to/donalda/the-7-minute-git-workflow-that-saves-me-hours-every-week-j47</guid>
      <description>&lt;p&gt;Git is powerful. It’s also a black hole where hours disappear if you’re still typing the same long commands you learned in 2014 or digging through a history full of “fix typo” commits from three months ago. I’ve whittled my daily routine down to something I can do without cursing into my soda. It’s fast, clean, and takes under seven minutes per task.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Make a new branch every time&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;git checkout -b feature/short-descriptive-name&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;No “one branch to rule them all.” Bug fixes, new features, experiments—each gets its own.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Stage only what you mean to commit&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;git add -p&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Keeps you from cramming unrelated changes into one commit, which is basically code hoarding.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Keep commit messages short and clear
Format:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;[type] present-tense description&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;fix: correct typo in config loader&lt;/code&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Rebase for cleanup, don’t merge&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;git pull --rebase origin main&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Keeps history straight so you don’t need a red string conspiracy board to follow it later.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Squash before you send it off&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;git rebase -i HEAD~n&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Replace n with however many commits you’re mashing together.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Push it up&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;code&gt;git push -u origin feature/short-descriptive-name&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;This saves me from the “what fresh hell is this” moment when reviewing old code. History stays readable. Brain stays uncluttered. And if you’ve been treating your repo like a junk drawer, try this for a week. You won’t go back.&lt;/p&gt;

</description>
      <category>git</category>
      <category>productivity</category>
      <category>programming</category>
      <category>developers</category>
    </item>
    <item>
      <title>A Year Late to My Own Introduction</title>
      <dc:creator>Donalda Feith</dc:creator>
      <pubDate>Mon, 11 Aug 2025 01:25:39 +0000</pubDate>
      <link>https://dev.to/donalda/a-year-late-to-my-own-introduction-463f</link>
      <guid>https://dev.to/donalda/a-year-late-to-my-own-introduction-463f</guid>
      <description>&lt;p&gt;I’ve had this Dev.to account for a year and never posted. Time to fix that.&lt;/p&gt;

&lt;p&gt;I’m Donalda, a PhD in Computer Science with more than two decades in full stack development. Most of my work has been on secure, scalable systems, and I’ve built for web, mobile, and cloud across multiple industries. I work in Python, TypeScript, C#, Dart, Rust, Kotlin, Swift, Scala, and a few others I can still remember without checking my notes.&lt;/p&gt;

&lt;p&gt;I’m based in the mountains of North Carolina, where I split my time between coding, raising my 12-year-old son, and taking on side projects that tend to start as small fixes and turn into full rebuilds.&lt;/p&gt;

&lt;p&gt;I joined Dev.to to share what I’ve learned, connect with other developers, and see what everyone else is building. If you work on interesting systems, or you’re dealing with a tricky technical problem, I’d like to hear about it.&lt;/p&gt;

</description>
      <category>career</category>
      <category>python</category>
      <category>welcome</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
