<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software Development on Raygun Blog</title>
    <link>https://raygun.com/blog/tags/software-development/</link>
    <description>Recent content in Software Development on Raygun Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 Jun 2022 09:17:09 +1300</lastBuildDate>
    <atom:link href="https://raygun.com/blog/tags/software-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The SDLC: Popular models, benefits &amp; best practices</title>
      <link>https://raygun.com/blog/software-development-life-cycle/</link>
      <pubDate>Wed, 01 Jun 2022 09:17:09 +1300</pubDate>
      <guid>https://raygun.com/blog/software-development-life-cycle/</guid>
      <description>&lt;p&gt;The Software Development Life Cycle (SDLC) refers to the process we follow to deliver software to customers. It captures each step of creating software, from ideation to delivery, and eventually to maintenance.&lt;/p&gt;&#xA;&lt;p&gt;In this post, we’ve broken down everything you need to understand the SDLC:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#history&#34; target=&#34;_blank&#34; &gt;History of the SDLC&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#what-is-the-sdlc&#34; target=&#34;_blank&#34; &gt;What is the SDLC, and why did it evolve?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#how-does-sdlc-work&#34; target=&#34;_blank&#34; &gt;How does the SDLC work?&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#benefits&#34; target=&#34;_blank&#34; &gt;Benefits of the SDLC&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#the-seven-phases&#34; target=&#34;_blank&#34; &gt;The seven phases of the SDLC&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#infographic&#34; target=&#34;_blank&#34; &gt;Seven phases of the SDLC infographic&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#models&#34; target=&#34;_blank&#34; &gt;Popular SDLC models&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#practices&#34; target=&#34;_blank&#34; &gt;SDLC best practices&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;#systems&#34; target=&#34;_blank&#34; &gt;SDLC management systems&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;h2 id=&#34;history-of-the-sdlc&#34;&gt;&lt;a id=&#34;history&#34; name=&#34;history&#34;&gt;&lt;/a&gt;History of the SDLC&lt;/h2&gt;&#xA;&lt;p&gt;The field of software development as a profession has existed since the first computers and their operators, as far back as ENIAC and vacuum tubes. As the disclipine has matured, practices and methods for developing software have evolved.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why building internal tools could become a costly mistake</title>
      <link>https://raygun.com/blog/building-it-yourself-vs-paying/</link>
      <pubDate>Fri, 18 May 2018 10:30:09 +1300</pubDate>
      <guid>https://raygun.com/blog/building-it-yourself-vs-paying/</guid>
      <description>&lt;p&gt;Having worked closely with software developers for almost a decade, I’ve noticed some common traits amongst them.&lt;/p&gt;&#xA;&lt;p&gt;Technically minded people think about problems in different ways. I’m often stunned how I could miss such an obvious data point or edge case when discussing product changes with people who have a far greater technical mind than myself.&lt;/p&gt;&#xA;&lt;p&gt;I also find myself looking around for third party tools to solve problems, whereas developers like to scratch their own itches and have the skills to be able to build pretty much any tool or product themselves.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Six essential software deployment tools for error-free applications</title>
      <link>https://raygun.com/blog/software-deployment-tools/</link>
      <pubDate>Sun, 16 Jul 2017 23:59:35 +0000</pubDate>
      <guid>https://raygun.com/blog/software-deployment-tools/</guid>
      <description>&lt;p&gt;&lt;span&gt;Bad deployments are a resource-draining problem for every development team. Without the help of software deployment tools, s&lt;/span&gt;&lt;span&gt;potting a bad deployment is like finding a needle in a haystack.&lt;/span&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;span&gt;Almost 1/3 of software businesses count on their end users to report these errors. In the last company I worked for, we’d deploy, wait a day or two, and assume it was all fine because we didn’t hear many complaints.&lt;/span&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;span&gt;What we &lt;strong&gt;didn’t&lt;/strong&gt; factor in was that only 1% of customers report software errors, and any reports were usually vague and never gave diagnostic details. But we didn’t know a better way. &lt;/span&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
