<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Justin Tulloss on Medium]]></title>
        <description><![CDATA[Stories by Justin Tulloss on Medium]]></description>
        <link>https://medium.com/@justin_tulloss?source=rss-c96d7614e36c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Ahbi0LBBO31InVB-.jpeg</url>
            <title>Stories by Justin Tulloss on Medium</title>
            <link>https://medium.com/@justin_tulloss?source=rss-c96d7614e36c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:35:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justin_tulloss/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Up Next: End-to-End Mobile Testing]]></title>
            <link>https://medium.com/spotbot/up-next-end-to-end-mobile-testing-a8f3d220792?source=rss-c96d7614e36c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8f3d220792</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[functional-testing]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[automated-testing]]></category>
            <dc:creator><![CDATA[Justin Tulloss]]></dc:creator>
            <pubDate>Tue, 16 Aug 2016 22:11:10 GMT</pubDate>
            <atom:updated>2016-08-16T22:11:10.167Z</atom:updated>
            <content:encoded><![CDATA[<p>The long-term vision for <a href="https://spotbot.qa/">Spotbot</a> is simple: create an AI that can test any software user interface. Today we’re excited to announce that we’re looking for beta users for our next step toward that goal: end-to-end mobile application testing.</p><h4>🙈 Who We’re Looking For</h4><p>If your team has a mobile app and you wish you had end-to-end feature tests, <a href="https://spotbot.qa/">let us know</a> and we’ll take care of getting you started. We’ll write some baseline tests, maintain them, and give you an environment to develop the rest of your tests within.</p><p>We’re still developing the product, but if your team needs the things below, we’d love to have you as a part of the beta.</p><ul><li><strong>We create baseline tests for your mobile app</strong>: payments, onboarding, sign up, and sign in flows are all covered, as is simple exploratory testing. All we need is your app and some test data.</li><li><strong>Create your own custom tests</strong> with the Spotbot Javascript test runner, powered by <a href="http://appium.io/">Appium</a>.</li><li><strong>Tests run on Spotbot’s infrastructure</strong>, against an array of devices in the cloud.</li><li>Integrates with Github, CircleCI, and Jenkins with hooks for other continuous integration systems.</li><li>Provides a <strong>complete report of test status</strong> for each build, plus visual diffs of every screenshot that changed in the test.</li><li>Ongoing maintenance. <strong>We keep baseline tests up to date for you </strong>and flag custom tests that need revision.</li><li>Test stability. The build <strong>doesn’t break if one of your tests is flaky</strong>. Instead, the author of the flaky test is prompted to make their test more stable or remove it.</li><li>Debugging tools. When a test breaks, you can get into the right state on the right device with the click of a button. Then you can <strong>run the tests against a local build</strong> in order to make sure the fix works.</li><li><strong>No lock-in</strong>. If you want out, we’ll export all the tests we wrote for you.</li></ul><p>During our limited beta we’re offering all of this for a flat $499 / mo.</p><h4>📈 The Path Forward</h4><p>Training a machine to use arbitrary user interfaces is tricky business. If you squint one way, it looks like a simple pattern matching problem with way fewer edge cases than self-driving cars or even appointment schedulers. Squint a different way and it looks a lot like developing <a href="https://en.wikipedia.org/wiki/Artificial_general_intelligence">general intelligence</a> to solve the <a href="https://en.wikipedia.org/wiki/Halting_problem">halting problem</a>.</p><p>At Spotbot, we’re taking a classic approach to this problem and deferring to humans when our trained models cannot complete a task. While we’re developing and maintaining your functional tests for you, we’re also gathering a massive pile of labeled state transitions make our models better and better.</p><p>Today we’re using <a href="https://en.wikipedia.org/wiki/Reinforcement_learning">reinforcement learning</a> to automatically test signing in to websites without writing code. Currently it works for a small number of apps; with more examples it will continue to improve until it can automatically validate arbitrary goals.</p><h4>🐣 Get Started</h4><p>We’re looking for companies that could use some help getting their mobile app’s functional test suite started. If that sounds like you, <a href="https://spotbot.qa/">head to our site and sign up</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8f3d220792" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spotbot/up-next-end-to-end-mobile-testing-a8f3d220792">Up Next: End-to-End Mobile Testing</a> was originally published in <a href="https://medium.com/spotbot">Spotbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spotbot ❤️ Pantheon]]></title>
            <link>https://medium.com/spotbot/spotbot-%EF%B8%8F-pantheon-59a62852a862?source=rss-c96d7614e36c------2</link>
            <guid isPermaLink="false">https://medium.com/p/59a62852a862</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[pantheon]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Justin Tulloss]]></dc:creator>
            <pubDate>Tue, 05 Jul 2016 23:45:05 GMT</pubDate>
            <atom:updated>2016-07-05T23:45:05.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b7y_JAVlGDDOWyeHbXk6yg.png" /></figure><p><a href="https://spotbot.qa/">Spotbot</a>, by default, scans web pages every 24 hours across a number of devices and browsers. It posts changes to your Slack channel and learns over time what kinds of changes are expected and which are bugs.</p><p>For some users, that’s enough to flag issues while still deploying daily. Others want to integrate Spotbot’s scans into their development process to find problems before they deploy.</p><p>For that, we have an <a href="http://docs.spotbot.qa/api.html">API</a> that you can use to scan any URL at any time. In this article, we talk about integrating with one of our favorite hosting platforms, <a href="https://pantheon.io/">Pantheon</a>, to make sure your <a href="https://wordpress.com/">WordPress</a> or <a href="https://www.drupal.org/">Drupal</a> site looks great every time you make a change.</p><h4>🏁 Getting Started with Pantheon’s Quicksilver</h4><p><a href="https://pantheon.io/docs/quicksilver/">Quicksilver</a> is Pantheon’s system for setting up actions that occur whenever an event happens within Pantheon. For this example we’ll be integrating Spotbot whenever you deploy to the <a href="https://pantheon.io/docs/pantheon-workflow/">test environment or the live environment</a>.</p><p>First, you’ll need to <a href="https://spotbot.qa/auth/slack">sign up for Spotbot with Slack</a> if you haven’t already.</p><p>Next, create a pantheon.yml file within your code repository that is hosted on Pantheon.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7f5f1e38873997621b6c4bc50a3e0563/href">https://medium.com/media/7f5f1e38873997621b6c4bc50a3e0563/href</a></iframe><p>This will run the scripts/run_spotbot.php script every time a deploy happens. You should create the scripts directory and add a run_spotbot.php script that triggers a Spotbot scan. For instance:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f27385a6902c100f83d942fdf95334ef/href">https://medium.com/media/f27385a6902c100f83d942fdf95334ef/href</a></iframe><p>This script kicks off a Spotbot scan and prints the URL where the result can be found. You’ll also be notified in Slack when the scan is complete.</p><p>Feel free to use that script as the basis for your own integrations with Spotbot. The important bits are:</p><ul><li>$api_key. You’ll need to set your own API key which can be found here: <a href="https://spotbot.qa/api/token">https://spotbot.qa/api/token</a></li><li>$urls_to_scan. This is a list of paths that you want to scan every time you deploy. For a project I was doing for my friends over at <a href="https://urbantrailssf.com/">Urban Trails</a>, I put a flag in the URL that told the page to render as if a form had been successfully submitted. This allows us to test both the initial state and the success state without actually going through the work to submit the form.</li><li>$spotbot_request. You’ll want to add your slack channel to the notifications array.</li></ul><p>Now every time you deploy your Pantheon site to test or live, your team will get a summary of everything that changed on across many browsers and devices. 💥.</p><h4>🤔 Troubleshooting</h4><p>The easiest way to figure out what’s going wrong when you’re deploying to Pantheon is to use their <a href="https://github.com/pantheon-systems/terminus">Terminus command line tool</a>. Just run the command below and everything that’s happening within Pantheon’s workflow will be printed to your terminal.</p><pre>terminus workflows watch</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59a62852a862" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spotbot/spotbot-%EF%B8%8F-pantheon-59a62852a862">Spotbot ❤️ Pantheon</a> was originally published in <a href="https://medium.com/spotbot">Spotbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Accurate Visual Diffs]]></title>
            <link>https://medium.com/spotbot/building-accurate-visual-diffs-6b41b09973a6?source=rss-c96d7614e36c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b41b09973a6</guid>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[computer-science]]></category>
            <dc:creator><![CDATA[Justin Tulloss]]></dc:creator>
            <pubDate>Tue, 31 May 2016 15:01:01 GMT</pubDate>
            <atom:updated>2016-05-31T18:49:44.080Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://spotbot.qa/">Spotbot</a>, we’re all about helping software teams ship faster. A great way to do this is by <a href="https://www.youtube.com/watch?v=1wHr-O6gEfc">using visual diffs</a>. Visual diffs show you the difference between how a page used to look and how it looks now. When they work well, they draw your eye to exactly what changed so engineers, designers, and PMs can all work together to make sure that the product is up to their standards.</p><p>The thing is, they have to work well. If they don’t, they’re just another distraction. Since distractions only hurt a teams cadence, we knew that to build a helpful tool, we had to make them work well.</p><h4>Pixel Diffs Are Brittle</h4><p><a href="https://github.com/BBC-News/wraith">Most</a> <a href="https://github.com/bslatkin/dpxdt">tools</a> <a href="https://github.com/uber/image-diff">that</a> <a href="https://github.com/facebookarchive/huxley">manage</a> <a href="https://github.com/Huddle/PhantomCSS">visual</a> <a href="https://github.com/igorescobar/automated-screenshot-diff">diffs</a> for teams use <a href="http://www.imagemagick.org/script/compare.php">pixel diffing</a>. Unfortunately pixel diffing has a lot of issues, summed up with the example below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*XRi5QXfHhY0xiDtP6sSr-A.png" /><figcaption>A “sea of red” pixel diff</figcaption></figure><p>All that changed in that page is a banner at the top and the dates. But because the banner at the top pushed everything down 20px, it looks like <em>everything</em> changed.</p><p>Luckily there’s a better way.</p><h4>Structural Diffing is Sturdy</h4><p>By using the structure of the page instead of the raw pixels, we can generate a much more accurate diff.</p><ol><li>Create a tree that represents the page. The tree looks like a DOM tree, but it includes information like the bounding rectangle of the node and all the calculated styles.</li><li>Diff the new tree with the old tree. This is unfortunately <a href="http://www2.compute.dtu.dk/~phbi/files/publications/2005asotedarpJ.pdf">NP-hard</a>, but we can fake it (details below).</li><li>Circle the nodes that have changed (if the user hasn’t previously indicated that they don’t care about those changes).</li></ol><p>Simple and effective. We can now point out things that moved and figure out what got inserted where when the rest of the document stayed the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GiVzpkssPZrCN9EXiUufWQ.png" /><figcaption><a href="https://www.heavybit.com/">Heavybit</a> fixed one of their pages at lower resolutions. This would have been a “sea of red” if it was a pixel diff.</figcaption></figure><h4>The Gory Details of Creating a Structural Diff</h4><p>The goal of a tree diff is to describe the minimal set of operations (add, remove, move, and modify) to transform tree A into tree B. There has been a <a href="http://referaat.cs.utwente.nl/conference/3/paper/7144/change-detection-in-xml-trees-a-survey.pdf">lot</a> of <a href="https://www.cs.rutgers.edu/~amelie/papers/2002/diff.pdf">work</a> <a href="http://useless-factor.blogspot.com/2008/01/matching-diffing-and-merging-xml.html">done</a> on diffing trees, and it’s not a trivial problem. The crux of the difficulty is that a node somewhere in tree A may be anywhere in tree B, and the only way to verify that it’s not is to check all of them (that is waaaay oversimplified, read the papers for the details).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0dvXY3ZBtmC9tiz5TOyig.png" /><figcaption>Source: Grégory Cobéna, Serge Abiteboul, and Amélie Marian, <a href="https://www.cs.rutgers.edu/~amelie/papers/2002/diff.pdf">Detecting Changes in XML Documents</a>.</figcaption></figure><p>It’s possible to take some shortcuts to simplify the problem. One is to somehow uniquely identify the nodes. Another is to only identify moves among siblings in a tree. If a node has moved to a different parent, screw it, it’s a removal and an insert.</p><p>The React developers have published a <a href="https://facebook.github.io/react/docs/reconciliation.html">nice post</a> on how they take these shortcuts in <a href="https://facebook.github.io/react/">React</a>, where they <a href="https://github.com/facebook/react/blob/db6ac5c01c4ad669db7ca264bc81ae5b3d6dfa01/src/isomorphic/classic/element/ReactElementValidator.js#L101-L108">enforce unique keys among siblings</a>. React can get away with this because React is responsible for creating the tree in the first place, so it has knowledge of every node and can id them itself.</p><p>Where React has control over the input, Spotbot does not. When diffing arbitrary trees where you don’t have control over the identifiers, you need to come up with some way of uniquely identifying a node.</p><p>Our tree is a JSON structure that represents the page once it’s loaded. It contains not only DOM information but also styling.</p><pre>// Simplified representation of a node<br>{<br>  type: “h1”,<br>  class: “header title”,<br>  // ... additional DOM attributes<br>  rect: {<br>    x: 124,<br>    y: 88,<br>    width: 440,<br>    height: 72,<br>  },<br>  style: {<br>    color: “#3F51B5”,<br>    ‘background-color’: “#FAFAFA”<br>    // … etc.<br>  },<br>  textHash: 123775901831,<br>  children: [ /* A bunch of similar objects */ ],<br>}</pre><p>At Spotbot, we use a heuristic inspired by BULD (bottom up, lazy down, described in <a href="https://www.cs.rutgers.edu/~amelie/papers/2002/diff.pdf">part 5 of this paper</a>) to build an identifier that we add to these node objects.</p><p>First we compute the signatures for each node. The signature is a hash of the contents (if it’s a text node), the id, each of the classes, and the combination of its children’s hashes (if it’s an element node).</p><pre>// Pseudocode for calculating the hash<br>function hash(node) {<br>   childHash = node.children.reduce((h, c) =&gt; combine(h, hash(c)))<br>   attrHash = textHash(node.id + node.classNames)<br>   return <a href="http://www.boost.org/doc/libs/1_35_0/doc/html/boost/hash_combine_id241013.html">combine</a>(childHash, attrHash)<br>}</pre><p>There are many possible signatures, so a set of the possible signatures for the node is created. Then each signature is matched against the signatures in the other tree to find the unique one. If a unique signature is found, the corresponding node B is matched with this node A and we use the signature as the node A’s id.</p><p>Now that we have unique identifiers, we just need to come up with that minimal set of operations that will transform tree A into tree B. At Spotbot we use the excellent <a href="https://github.com/benjamine/jsondiffpatch">JSONDiffPatch</a> library alongside the node identifiers we built with the bottom up, lazy down technique. This basically does two things:</p><ul><li>Identifies nodes that are the same, but have different attributes. We note the attributes that are different and mark the node as changed.</li><li>Identifies children that have been inserted, deleted, or moved. JSONDiffPatch does this by finding the <a href="https://en.wikipedia.org/wiki/Longest_common_subsequence_problem">longest common subsequence</a> in the array of children. These nodes are also marked as changed.</li></ul><p>And that’s it! Now we’ve got a new tree B with nodes marked with the changes that were made to old tree A to get to the newer state. We can then use that information to decide whether the change is relevant (it’s visible and hasn’t been ignored). All relevant changes get boxes drawn around them in the UI so the user can jump between changes and see exactly what changed.</p><h4>Flaws in Structural Diffing</h4><p>As with any engineering decision, there are tradeoffs. Structural diffing is not perfect and there’s still a lot of work for us to do at Spotbot before it works flawlessly.</p><ul><li>Added DOM wrappers. Since we only identify moves amongst children, adding a wrapper div can cause us to think vast sections of a page were added or removed when in fact there was just a wrapper element added. This may be improved by using <a href="https://github.com/fdintino/xydiff">XYdif</a>f instead of the simple JSONDiffPatch algorithm which mostly relies on LCS.</li><li>Browser inconsistencies. Sometimes IE draws a box to be 100px wide, and sometimes that box is 101px wide. ¯\_(ツ)_/¯</li><li>Cache busting urls. It’s pretty hard to tell if an image changed because the image source was changed or if a cache-busting parameter was added. Layering pixel diffing on top of structural diffing may solve this particular problem.</li></ul><p>Those problems are all solvable, or at least manageable, and, at Spotbot, we’re getting better every day. <a href="https://spotbot.qa/">Check out Spotbot today</a> and catch issues at a glance!</p><figure><a href="https://spotbot.qa/"><img alt="" src="https://cdn-images-1.medium.com/max/128/1*b8ggbYWb6TNQqWQzrC9LLg.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b41b09973a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spotbot/building-accurate-visual-diffs-6b41b09973a6">Building Accurate Visual Diffs</a> was originally published in <a href="https://medium.com/spotbot">Spotbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Update, Optionality Edition]]></title>
            <link>https://medium.com/spotbot/product-update-optionality-edition-70e3d6244f8e?source=rss-c96d7614e36c------2</link>
            <guid isPermaLink="false">https://medium.com/p/70e3d6244f8e</guid>
            <category><![CDATA[options]]></category>
            <category><![CDATA[latest-updates]]></category>
            <dc:creator><![CDATA[Justin Tulloss]]></dc:creator>
            <pubDate>Fri, 13 May 2016 22:11:19 GMT</pubDate>
            <atom:updated>2016-05-13T22:11:19.376Z</atom:updated>
            <content:encoded><![CDATA[<p>My finance friends tell me that it’s always good to increase optionality, which is why I never commit to anything.</p><p>This week <a href="https://spotbot.qa/">Spotbot</a> gained a few new options for controlling the behavior of your <a href="https://spotbot.qa/pages">tracked pages</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*jCbK3Rv2gvPyssmmc2MiNg.png" /><figcaption>More buttons for your clicking pleasure</figcaption></figure><h4>🔍 Scanning Frequency</h4><p>Maybe you don’t care for daily checks on all your pages and just want us to check up once a week. Or maybe you want total control through <a href="http://docs.spotbot.qa/api.html">our API</a>. Either way, you’ve got an option now (unless you’re on our free plan, in which case once a week is the limit).</p><h4>🔔 Notification Thresholds</h4><p>Some people want to know about every change to a page (for instance, if you’re monitoring an <a href="http://www.ebay.com/itm/NEW-LEGO-Star-Wars-Force-Awakens-75105-Millennium-Falcon-No-Minifigures-OR-Box-/322059797323">awesome ebay auction</a>), but most people just want to know when their page is all jacked up. And some people have it under control and don’t want to be notified ever. Now we’ve got all those people covered.</p><h4>⏱Delay</h4><p>Do you have a fancy animation that your users just can’t get enough of? Well sometimes that’s confusing for Spotbot, so now you have the option to help it out and wait for a few seconds before capturing your page.</p><h4>✅ Slack Channel</h4><p>Before this option, you had better be sure that everybody was hanging out in Spotbot’s preferred channel. No longer! Now the marketing team can keep up with their fave pages over in their channel while engineering sticks to its channel and makes sure their boring old sign in pages keep the people signing in.</p><h4>🍪 Cookies</h4><p>A lot of you are getting fancy with your As and your Bs. Now you can specify cookies that should be set whenever your page is loaded, ensuring that Spotbot is getting the same version of your page every time it gets loaded.</p><h3>Older updates</h3><p>There has been a lot done in the past weeks that didn’t make the blog because the blog didn’t exist yet. The most important update is the ability to tell Spotbot what to ignore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*JCWM0kWQPJw7MpSGq8OWrg.png" /><figcaption>Moar buttons!!</figcaption></figure><p>These options feed back into Spotbot to make it able to serve your unique ❄️ needs. Ignoring changes will make sure you don’t get bothered for that set of changes again, and is great for ignoring things like dates and content that changes all the time. Letting us know that nothing actually changed will make sure that one of Spotbot’s handlers takes a look at your page to figure out why it alerted you. And the “Thanks for noticing” option? That’s just to make us feel good about serving you well 😸.</p><p>That’s all for now! Have a great weekend, and if you happen to be in San Francisco, I’ll see you at <a href="http://www.zapposbaytobreakers.com/">Bay to Breakers</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70e3d6244f8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spotbot/product-update-optionality-edition-70e3d6244f8e">Product Update, Optionality Edition</a> was originally published in <a href="https://medium.com/spotbot">Spotbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[And we’re off!]]></title>
            <link>https://medium.com/spotbot/and-were-off-a3d6a4d89b91?source=rss-c96d7614e36c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3d6a4d89b91</guid>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Justin Tulloss]]></dc:creator>
            <pubDate>Thu, 12 May 2016 04:00:13 GMT</pubDate>
            <atom:updated>2016-05-12T04:01:19.330Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bCWeXoyE3cuKrd7ENe38fw.png" /></figure><p><a href="https://spotbot.qa/">Spotbot</a> has been live for about 8 weeks now and we’ve learned a lot in that time. We wanted to have a place to share what we’ve learned, our opinions on software development, and what’s coming up in Spotbot. There’s no better place to do that than Medium.</p><p>We’ll have more to say in the future! Thanks for riding with us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3d6a4d89b91" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spotbot/and-were-off-a3d6a4d89b91">And we’re off!</a> was originally published in <a href="https://medium.com/spotbot">Spotbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>