<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <channel>
    
    <title><![CDATA[Engineering Blog]]></title>
    <link>https://www.ebsco.com/engineering</link>
    <description></description>
    <dc:language>en</dc:language>
    <dc:creator>EBSCO</dc:creator>
    <dc:rights>Copyright 2016</dc:rights>
    <dc:date>2016-05-11T20:56:00+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <item>
      <title><![CDATA[Continuous Delivery… Incrementally]]></title>
      <link>https://www.ebsco.com/engineering/continuous-delivery-incrementally</link>
      <guid>https://www.ebsco.com/engineering/continuous-delivery-incrementally#When:14:06:00Z</guid>
      <description><![CDATA[There is a lot of buzz amongst the development community at large about Continuous Delivery.  Everyone seems to think its a good idea but I’ve seen few execute implementation well.  In this post, we will briefly review what CD is and then I’ll give my opinions on the best way to implement it (HINT: its in the title).  ]]></description>
      <dc:subject><![CDATA[]]></dc:subject>
      <dc:date>2016-06-03T14:06:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Unit Testing: Go red or don't write unit tests!]]></title>
      <link>https://www.ebsco.com/engineering/go-red-or-dont-write-unit-tests</link>
      <guid>https://www.ebsco.com/engineering/go-red-or-dont-write-unit-tests#When:20:56:00Z</guid>
      <description><![CDATA[Unit testing is hard, I know.  Especially for new developers.  But forcing them to unit test just to say “we have unit tested” may cause more harm than good.  If they don’t take the time to really understand why we unit test and how to test correctly they are much more likely to write bad tests which provide a false sense of confidence.]]></description>
      <dc:subject><![CDATA[]]></dc:subject>
      <dc:date>2016-05-11T20:56:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[TFS 2010 to 2015 Upgrade: CodedUI Feature Test Builds]]></title>
      <link>https://www.ebsco.com/engineering/tfs-2010-to-2015-upgrade-codedui-feature-test-builds</link>
      <guid>https://www.ebsco.com/engineering/tfs-2010-to-2015-upgrade-codedui-feature-test-builds#When:22:07:00Z</guid>
      <description><![CDATA[Robb Schiefer, a solutions architect in our Enterprise & Data Services Engineering team, recently blogged about some of their experiences upgrading from TFS 2010 to TFS 2015.  The post is specifically focused on the upgrade of their CodedUI automation tests.  Robb explains some of the key changes from TFS 2010 to TFS 2015 and provides solutions to the errors they encoutered.  Check it out!
]]></description>
      <dc:subject><![CDATA[]]></dc:subject>
      <dc:date>2016-02-05T22:07:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[IISPosh - New IIS Cookbook for Chef]]></title>
      <link>https://www.ebsco.com/engineering/iisposh-new-iis-cookbook-for-chef</link>
      <guid>https://www.ebsco.com/engineering/iisposh-new-iis-cookbook-for-chef#When:16:12:00Z</guid>
      <description><![CDATA[So why create a new IIS cookbook? We focused on three areas for improvement idempotency, settings and extensibility. The original cookbook uses appcmd.exe and was not idempotent. We needed an idempotent way to configure IIS since changing some settings initiated a restart of the site. ]]></description>
      <dc:subject><![CDATA[]]></dc:subject>
      <dc:date>2015-12-04T16:12:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[Chef cookbook design for the culinarily challenged software engineer]]></title>
      <link>https://www.ebsco.com/engineering/chef-cookbook-design-for-the-culinarily-challenged-software-engineer</link>
      <guid>https://www.ebsco.com/engineering/chef-cookbook-design-for-the-culinarily-challenged-software-engineer#When:16:51:00Z</guid>
      <description><![CDATA[Early in our Chef journey, we spent a lot of time discussing what the relationship between our cookbooks would look like. We decided on the following structure for a few reasons...]]></description>
      <dc:subject><![CDATA[]]></dc:subject>
      <dc:date>2015-08-28T16:51:00+00:00</dc:date>
    </item>

    <item>
      <title><![CDATA[DevOps Meetup]]></title>
      <link>https://www.ebsco.com/engineering/devops-meetup</link>
      <guid>https://www.ebsco.com/engineering/devops-meetup#When:00:51:00Z</guid>
      <description><![CDATA[We have started a DevOps Meetup for North of Boston.  ]]></description>
      <dc:subject><![CDATA[]]></dc:subject>
      <dc:date>2015-06-30T00:51:00+00:00</dc:date>
    </item>

    
    </channel>
</rss>