<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continous-Integration on Build Wrangler</title><link>/tags/continous-integration/</link><description>Recent content in Continous-Integration on Build Wrangler</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 19 Oct 2017 00:16:17 -0500</lastBuildDate><atom:link href="/tags/continous-integration/index.xml" rel="self" type="application/rss+xml"/><item><title>Lint Early and Lint Often</title><link>/posts/lint-early-lint-often/</link><pubDate>Thu, 19 Oct 2017 00:16:17 -0500</pubDate><guid>/posts/lint-early-lint-often/</guid><description>&lt;p&gt;Some of the lowest hanging fruit you can pick for an easier to maintain project is setting up and automating linting on every check-in or pull-request as early as possible. It should be one of the first steps in any build pipeline and often serves as an early indicator if you&amp;rsquo;ve tried to push something &lt;em&gt;obviously&lt;/em&gt; wrong quickly. Linting will prevent a lot of unnecessary dings on pull-requests and wasted engineering time having to point these things out as well.&lt;/p&gt;</description></item><item><title>Google: A Peek At The Campus And Culture</title><link>/posts/google-peek-inside/</link><pubDate>Wed, 11 Oct 2017 00:16:17 -0500</pubDate><guid>/posts/google-peek-inside/</guid><description>&lt;p&gt;Getting invited on a scholarship to visit a Google campus and attend their development conference is a memorable experience. It’s an excellent opportunity for a developer to learn about what makes Google tick, their software development process and what their continuous integration and continuous delivery systems are like.&lt;/p&gt;
&lt;p&gt;Here are some of the takeaways from the conference and the time I got to spend with some of their engineers:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Very few in companies in the world invest in their people like Google. I, like most people in the tech industry, overhear about the perks and internal tooling available to Googlers, but I was still surprised when I got to see it in person.&lt;/p&gt;</description></item><item><title>Highlights from the Google Automation Conference</title><link>/posts/gtac-highlights-2016/</link><pubDate>Mon, 09 Oct 2017 00:16:17 -0500</pubDate><guid>/posts/gtac-highlights-2016/</guid><description>&lt;p&gt;I have listed the talks I got the most value out of from top to bottom with supporting links when appropriate. After digging through my notes from when I attended GTAC 2016 I wanted to share the ones that stood out the most.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=CrzpkF1-VsA"&gt;&lt;strong&gt;Talk:&lt;/strong&gt; How Flaky Tests in Continuous Integration&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=CrzpkF1-VsA"&gt;&lt;!-- raw HTML omitted --&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is my pick for best talk of the conference. It&amp;rsquo;s ground breaking research into flaky tests from googles massive amounts of build data and how they use it to make developers more productive and spot legitimate bugs faster.&lt;/p&gt;</description></item></channel></rss>