<?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 Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/software-development/</link>
    <description>Recent content in Software Development on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Mar 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/software-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Testing, Benchmarking, Evaluating</title>
      <link>https://ronaldbradford.com/blog/testing-benchmarking-evaluating-2025-03-05/</link>
      <pubDate>Wed, 05 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/testing-benchmarking-evaluating-2025-03-05/</guid>
      <description>Testing and benchmarking are widely used terms in software technology, each serving a distinct purpose and goal. With the increasing adoption of AI in software development, the term evaluating has become significant and with this the re-emergence of what is quality assurance.</description>
    </item>
    <item>
      <title>Digital Tech Trek Digest  [#Issue 2024.01]</title>
      <link>https://ronaldbradford.com/blog/digital-tech-trek-digest-1-2024-01-03/</link>
      <pubDate>Wed, 03 Jan 2024 16:33:31 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/digital-tech-trek-digest-1-2024-01-03/</guid>
      <description>The Tiny Stack (Astro, SQLite, Litestream) I spent many years in the LAMP stack , and there are often many more acronyms of technology stacks in our evolving programming ecosystem. New today is “The Tiny Stack”, consisting of Astro , a modern meta-framework for javascript (not my words), and Lightstream Continuously stream SQLite changes.</description>
    </item>
    <item>
      <title>A reliable and dependable application requires observability</title>
      <link>https://ronaldbradford.com/blog/a-reliable-and-dependable-application-requires-observability-2022-09-29/</link>
      <pubDate>Thu, 29 Sep 2022 14:43:54 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/a-reliable-and-dependable-application-requires-observability-2022-09-29/</guid>
      <description>Observability (o11y) is a critical pre-requisite component in software architecture when advocating for and preparing organizations for making informed decisions on the success of their application. Open Telemetry from the Cloud Native Computing Foundation is the goto standard regardless of your choices of monitoring tools.</description>
    </item>
    <item>
      <title>The Legacy Dilemma</title>
      <link>https://ronaldbradford.com/blog/the-legacy-dilemma-2016-07-21/</link>
      <pubDate>Thu, 21 Jul 2016 16:04:48 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/the-legacy-dilemma-2016-07-21/</guid>
      <description>Organizations are rapidly developing new software applications to meet the need to consume ever increasing digital content and maintain market share in a given field. These newly developed applications cover a wide range of needs from advanced data analytics, to mobile applications, to personalized recommendation engines.</description>
    </item>
    <item>
      <title>The agile software development lifecycle responsibility</title>
      <link>https://ronaldbradford.com/blog/the-agile-software-development-lifecycle-responsibility-2016-07-06/</link>
      <pubDate>Wed, 06 Jul 2016 15:38:20 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/the-agile-software-development-lifecycle-responsibility-2016-07-06/</guid>
      <description>The eXtreme Programming (XP) methodology places emphasis on a number of core principles for agile software development. These include (and are not limited to) the planning game, short and frequent iterations, testing, frequent refactoring, continuous integration, ownership and standards.</description>
    </item>
    <item>
      <title>Are you a responsible developer?</title>
      <link>https://ronaldbradford.com/blog/are-you-a-responsible-developer-2016-06-08/</link>
      <pubDate>Wed, 08 Jun 2016 22:23:27 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/are-you-a-responsible-developer-2016-06-08/</guid>
      <description>What is a good example of individual developer responsibility? Here is just one example.&#xA;A developer downloads a copy of the core production database to their own development laptop. Why? Because it’s easy to work with real data, and it’s hard to consider building applicable test data that all engineers can utilize.</description>
    </item>
  </channel>
</rss>
