<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment on Bruno Pedro</title><link>https://brunopedro.com/tags/deployment/</link><description>Recent content in Deployment on Bruno Pedro</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 May 2018 10:00:15 -0700</lastBuildDate><atom:link href="https://brunopedro.com/tags/deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Use computers to do things</title><link>https://brunopedro.com/2012/09/17/use-computers-to-do-things/</link><pubDate>Mon, 17 Sep 2012 10:03:16 +0000</pubDate><guid>https://brunopedro.com/2012/09/17/use-computers-to-do-things/</guid><description>&lt;p>&lt;a href="http://zachholman.com/talk/unsucking-your-teams-development-environment" title="Use computers to do things">Use computers to do things&lt;/a>&lt;/p>
&lt;blockquote>
&lt;p>As you grow, your team&amp;rsquo;s development environment becomes really important. How long does it take to clone, set up, and boot your apps? Can your employees still be productive on an aging codebase? How can you automate CI, hooks, and other setup for new projects? Is any of this fun anymore?&lt;/p>
&lt;/blockquote></description></item></channel></rss>