<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Personal Projects on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/personal-projects/</link>
    <description>Recent content in Personal Projects on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 26 Jul 2023 19:05:41 -0400</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/personal-projects/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Journey Development vs. Destination Development: Choosing the Right Path for Software Projects</title>
      <link>https://www.bradcypert.com/journey-vs-destination/</link>
      <pubDate>Tue, 25 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/journey-vs-destination/</guid>
      <description>&lt;p&gt;For me, embarking on a software development journey can take two distinct paths - the Journey Development Path and the Destination Development Path. Each approach brings its unique set of goals, challenges, and rewards. In this blog post, we will explore the key differences between these two development philosophies and discuss how they influence us as developers. By the end of this article, my hope is that you will understand the differences between these two approaches and have some insight on when and why I think you should choose a specific path.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
