<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/alex-yale-loehr/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/alex-yale-loehr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vets.gov: A Modern Software Development Environment in Government</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2017/07/03/vets-gov-a-modern-software-development-environment-in-government/</link>
      <pubDate>Mon, 03 Jul 2017 15:36:05 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2017/07/03/vets-gov-a-modern-software-development-environment-in-government/</guid>
      <description>When people think of government software, they often think of COBOL and PowerBuilder 5, with manual software deploys every three to six months on a fixed number of machines in a government-run data center. This perception is sometimes justified, but sometimes entirely wrong. Regardless, the perception makes many developers reluctant to work for the government</description>
    </item>
  </channel>
</rss>
