<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Assignments-Falls on SDL: Software Development Lab</title><link>https://sdl-56e997.gitlab.io/assignments-fall/</link><description>Recent content in Assignments-Falls on SDL: Software Development Lab</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://sdl-56e997.gitlab.io/assignments-fall/index.xml" rel="self" type="application/rss+xml"/><item><title/><link>https://sdl-56e997.gitlab.io/assignments-fall/docker/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sdl-56e997.gitlab.io/assignments-fall/docker/</guid><description>&lt;h1 id="docker-for-sdl"&gt;Docker for SDL&lt;/h1&gt;
&lt;h2 id="why"&gt;Why?&lt;/h2&gt;
&lt;p&gt;There are two recurring problems in SDL projects that often block forward progress:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;It works on my machine&lt;/strong&gt;: Tests run on one person&amp;rsquo;s computer but not
another&amp;rsquo;s, typically because someone has installed a slightly different
library or has configured some option slightly differently. Software has
to work all of the time; it is not enough that one person on the team can
run the software. Everyone, including clients, must be able to run it
using published configurations.&lt;/p&gt;</description></item></channel></rss>