<?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 Steve Boak on Medium]]></title>
        <description><![CDATA[Stories by Steve Boak on Medium]]></description>
        <link>https://medium.com/@sboak?source=rss-606cadd4e408------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oR3XaNbMmh6wBVye-lFVQA.jpeg</url>
            <title>Stories by Steve Boak on Medium</title>
            <link>https://medium.com/@sboak?source=rss-606cadd4e408------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:16:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sboak/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[Prototype a complete mobile app with Framer UI kits & boilerplate code]]></title>
            <link>https://medium.com/framer-prototyping/prototype-a-complete-mobile-app-with-framer-ui-kits-boilerplate-code-f3f87ee7d874?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3f87ee7d874</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[resources]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[framer]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 23:50:22 GMT</pubDate>
            <atom:updated>2021-07-26T16:20:39.514Z</atom:updated>
            <content:encoded><![CDATA[<h3>Prototype A Complete Mobile App Using Framer UI Kits &amp; Boilerplate Code</h3><h4>It’s that easy to design your very own <a href="http://frmaer.com?utm_source=medium&amp;utm_medium=blog&amp;utm_term=boak_boilerplatecode&amp;utm_content=subtitle">Framer </a>prototype.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URpoFVM9hp4Bn9YfIBJfyQ.jpeg" /></figure><blockquote><strong>Editor’s note: </strong>We’ve made some big changes to Framer, and this article refers to a deprecated tool. <a href="https://blog.framer.com/framer-today-interactive-design-for-real-products-1b550bf44e54">Learn more about what Framer is today →</a></blockquote><p>I see <a href="https://dribbble.com/shots/3945978-Alignment-button">lots</a> <a href="https://dribbble.com/shots/2240003-Apple-TV-Settings-Icon-in-Framer">of</a> <a href="https://dribbble.com/shots/3368130-Stepper-Touch">examples</a> showing how great Framer is for microinteractions — <em>and it is</em>—but it often gets pigeon-holed into this use case. I use it for all my interaction design work. Yeah it relies on code, but increasingly the <em>kind</em> of code I need to get things done is simple boilerplate that I can copy and paste across prototypes. This also makes it <em>fast</em>. I’m hardly any faster at building InVision prototypes than I was when I started dragging rectangles onto static images and choosing targets from dropdowns 2 years ago, but Framer grows with me and I get faster as I get better at it. In other words, <em>it does what a good tool should do</em>.</p><p>If you’re new to Framer, The <a href="https://medium.com/u/89a1103c5c78">Framer Team</a> now publishes a great <a href="https://framer.com/getstarted/resources/">collection of resources</a> to make getting started easier — including not just UI components but the code to bring them to life. There’s still a learning curve, but once you climb it you’ll never look back.</p><p>I recently put together an entire mobile app prototype using a combination of components and code from UI kits. It was a fun challenge, and I want to share it all — the process, the code, and the final product (though I’ve changed the original app content since it was using internal <a href="https://medium.com/u/acdb626ac40c">Datadog HQ</a> business logic). I hope that it helps you get started with Framer and build great things with it.</p><h4>This code s̵u̵c̵k̵s̵ is appropriate for designers</h4><p>I’m not a developer, and I’m not trying to turn you into one. I <em>do</em> think digital product designers should write some code, but mostly to gain a real understanding of the medium you’re designing for. If you’re reading this and you’re a developer, I apologize in advance and would love to see an optimized version of this code. If you’re a designer, I hope my lack of skill makes this more approachable for you.</p><h3>What you’re building</h3><p>Here’s the prototype you’re building — an app for <a href="https://twitter.com/search?q=%23sliceline">Sliceline</a>—and the resources you’ll need to build it:</p><p><a href="https://framer.cloud/UrdVB">Sliceline</a></p><h4>Fiber UI kit</h4><p>The <a href="https://framer.com/fiber/">Fiber UI Kit</a> has a few files you’ll be using:</p><ul><li>Onboarding.framer used for, well…the onboarding flow</li><li>Dropdown.framer used for…yeah, dropdowns</li></ul><h4>Voyage UI kit</h4><p>The <a href="https://framer.com/voyage/">Voyage UI Kit</a> is what you use for the pizza detail screen with some visual changes:</p><ul><li>Notifications.framer for the toggles</li></ul><h4>Dynamic type</h4><p>You’re not actually using <a href="https://blog.framer.com/framer-dynamic-type-a86317ae3ce2">dynamic type</a> in this prototype, but you can use the <a href="https://framer.cloud/oyOkN/">Dashboard.framer</a> file for the home screen transitions and screen design.</p><h4>FramerInput</h4><p>You’re not using <a href="https://medium.com/u/9f821625cfd4">Benjamin den Boer</a>’s <a href="https://github.com/benjamindenboer/FramerInput">FramerInput</a> module in this prototype, but you should know about it (especially the example code at the bottom of that page). <a href="https://framer.cloud/JdeKv/">This chat app prototype</a> is the quintessential example of something that’s trivial with Framer but almost impossible to do with other interaction design tools.</p><h3>How it’s done</h3><p>Now let’s walk through how it’s made:</p><h4>Defaults</h4><p>For the sake of simplicity, all animations in this demo use the same curve, set as a global default at the top of the code:</p><pre># SETUP AND DEFAULTS<br>Framer.Defaults.Animation.curve = Spring(damping: .6)</pre><h4>Targeting</h4><p>To use artwork you’ve drawn in Framer Code, you need to activate targets manually. For those coming from the world of Sketch imports, which turns on all objects for Code (and introduces name collisions out the wazoo), this may be helpful:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*jpeMPqG4CkITvzkeSa2oHw.gif" /><figcaption>Turning on a target in Framer Design</figcaption></figure><h4>FlowComponent</h4><p>A single <a href="https://blog.framer.com/framer-flows-bd18617bbcf5">FlowComponent</a> is used for all navigation in this prototype. If you’ve been around Framer a while, you’ve probably used other components for navigation that require more code. Scrolling in FlowComponent requires no code (just make the artboard taller than the device), and all transitions are done with the same tiny block of code. If you learn how to use FlowComponent, all basic navigation in any prototype is taken care of.</p><p>At the top, you initialize the FlowComponent and load the WELCOME screen. Setting the size to Screen.size<strong> </strong>simply tells it to fill the whole screen:</p><pre>flowMain = new FlowComponent<br> size: Screen.size<br>flowMain.showNext(WELCOME)</pre><h4>Navigation</h4><p>The only <a href="https://www.cs.utah.edu/~germain/PPS/Topics/functions.html">function</a> in this demo is to control the main nav. In the design, you have a default and active layer (just setting the color) for each icon in the nav:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*oGpBAm8W0zEnWLk3VwHtFg.gif" /><figcaption>navicon_a and navicon_a_active are the two icons for the first item</figcaption></figure><p>The function navTap is called to show the active icon and set all other items to inactive:</p><pre>navTap = (tapped) -&gt;<br> for n in navItems<br>  n.children[1].visible = false<br>  n.children[0].visible = true<br>  if n.name == tapped.name<br>   n.children[1].visible = true</pre><p>Every onClick action used or navigation is pretty similar, first using either showNext, showPrevious, or showOverlayBottom (which all just control the transition animation) to change screens, and sometimes showing or hiding the main nav completely, and running navTap:</p><pre>flowMain.showNext(PIZZA_LIST, animate:false)<br>navTap(this)</pre><h4>On-boarding</h4><p>The on-boarding flow is just an intro screen and a single configuration dropdown for your location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*GtYBj5pVy_1ScLpFWBVPNg.gif" /><figcaption>The welcome screen with some simple loading transitions</figcaption></figure><p>There’s a lot more going on in the Fiber Kit’s Onboarding.framer file than you’re using here.</p><p>On the welcome screen, the logo and Get Started button both transition in with some simple animation code.</p><p>So that you don’t have to mess with object positions in your designs, you start by moving both objects up 40px and setting the opacity to 0. Then the animation just moves them back down, while setting opacity to 1. You can wrap these in a simple for-loop and add a delay sequence to stagger the transitions — here, an additional 0.5sec delay for each element. The same code is used for the lock screen animation.</p><pre># WELCOME ANIMATIONS<br>for layer,i in [logo, GetStarted]<br> layer.opacity = 0<br> layer.y -=40<br> layer.animate<br>  opacity: 1<br>  y: layer.y + 40<br>  options:<br>   delay: i * 0.5</pre><p>The dropdown code is taken from the Fiber kit’s Dropdown.framer but again you’re only using a bit of it to control the dropdowns, which will show the text of the item I choose:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*hT-P30sqk9TsDMU_f-uPPQ.gif" /><figcaption>Dropdowns will show what you select</figcaption></figure><p>You use <a href="https://framer.com/docs/#layer.states">states</a> to set what the dropdown looks like when open/closed, animations to control the caret and dropdown content, and an action to set the text of the dropdown if any item inside it is clicked.</p><p>The dropdown is probably the most code-heavy component in here, and for the sake of brevity I need to punt on explaining it more—reach out via comments if you have questions.</p><h4>Pizza screen button and toggles</h4><p>The last significant piece of code is on the pizza screen, where you need a bit to keep the “Add to Cart” button fixed on scroll as well as control the toggles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*NHHAr759Pp8HzR0ahwgmnA.gif" /><figcaption>Topping toggles and fixed-position cart button</figcaption></figure><p>A particularly s̵h̵i̵t̵t̵y̵ designer-friendly piece of code here sets the position of the button and uses the Scroll event (but only on this artboard) to make sure it doesn’t move (I know it’s shitty because it’s being checked every single time someone scrolls anywhere, but didn’t immediately think of a better way):</p><pre># FLOWCOMPONENT SCROLLING<br>btnCart.y = Screen.height - btnCart.height - NAV.height<br>flowMain.onMove -&gt;<br> if flowMain.current == PIZZA<br>  btnCart.y = Screen.height - btnCart.height - NAV.height + flowMain.scroll.scrollY</pre><p>Similar to the dropdowns, you’re using states on the toggles, though you only need to specify the off state in code since they are on by default:</p><pre>for toggle in [toggle1, toggle2, toggle3, toggle4, toggle5, toggle6, toggle7, toggle8]<br> toggle.states.off =<br>  backgroundColor: &quot;rgba(255, 255, 255, 0.5)&quot;<br>for knob in [knob1, knob2, knob3, knob4, knob5, knob6, knob7, knob8]<br> knob.states.off =<br>  x: 263<br>  shadowSpread: 1<br>  shadowColor: &quot;rgba(0,0,0,0.2)&quot;</pre><p>Use an event on each toggle’s knob and background to cycle between the two states with stateCycle():</p><pre>for row in toppingList.children<br> row.children[0].onTap -&gt;<br>  this.stateCycle()<br>  this.siblings[0].stateCycle()<br> row.children[1].onTap -&gt;<br>  this.stateCycle()<br>  this.siblings[0].stateCycle()</pre><h3>Wrapping up</h3><p>I haven’t seen many prototypes stringing together multiple screens and simple interactions. I hope this is useful to you, and I’d love to see more prototypes of app workflows available. If you find this useful, pay it forward.</p><p><em>Thanks for reading. Find me on </em><a href="https://twitter.com/sboak"><em>Twitter</em></a><em> or </em><a href="https://www.linkedin.com/in/stephenboak/"><em>LinkedIn</em></a><em> to talk more about product design, prototyping, research, and all things design.</em></p><figure><a href="https://framer.com/features/design/?utm_source=medium&amp;utm_medium=blog&amp;utm_term=boak_boilerplatecode&amp;utm_content=footer"><img alt="" src="https://cdn-images-1.medium.com/max/600/1*sdtKFiW1YN4FaMrHeNgUQQ.png" /></a></figure><figure><a href="https://framer.com/group"><img alt="" src="https://cdn-images-1.medium.com/max/353/1*PHGNn6aQzjMXnmTEYat9GQ.png" /></a></figure><figure><a href="https://framer.com/freetrial?utm_source=medium&amp;utm_medium=blog&amp;utm_term=boak_boilerplatecode&amp;utm_content=footer"><img alt="" src="https://cdn-images-1.medium.com/max/353/1*axq8Dl8TDS3uoNDd9JzwVg.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3f87ee7d874" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framer-prototyping/prototype-a-complete-mobile-app-with-framer-ui-kits-boilerplate-code-f3f87ee7d874">Prototype a complete mobile app with Framer UI kits &amp; boilerplate code</a> was originally published in <a href="https://medium.com/framer-prototyping">Framer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Historical Data and Performance Graphs for Health Checks]]></title>
            <link>https://medium.com/the-opsee-blog/historical-data-and-performance-graphs-for-health-checks-9ff3adb49291?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ff3adb49291</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Thu, 04 Aug 2016 14:01:01 GMT</pubDate>
            <atom:updated>2016-08-04T14:01:01.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uiXELe6UiAWwPa933xEJ9Q.png" /></figure><p>We’re constantly making health checks richer in Opsee, and today we’re adding a bunch of new stuff including:</p><ul><li>Historical data for every check</li><li>Activity feeds and detail pages for check events, with complete check state</li><li>State and round-trip time graphs</li></ul><h4>Activity Feed and Events</h4><p>There’s a new view in Opsee, showing state-change events for your checks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*KlRZ-55L8RJ_95v_ZE7i8g.png" /><figcaption>The new Events view in Opsee</figcaption></figure><p>Here you get a comprehensive view into which checks have failed, and when. For each change in state, we also capture the entire state of the check and make it available to you in the product, as well as in your notifications in the event of a failure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*3ycMlf0vODI31GqnauJhRQ.png" /><figcaption>The Detail view for a failure event, with complete check state data</figcaption></figure><h4>State and Round-trip Time Graphs</h4><p>Detail pages for your checks are now enriched with uptime and round-trip time graphs. These will tell you how a check has performed over time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*qa7dHvNSEtw3m5Vw3MtyQg.png" /><figcaption>The state history for this check over the last 72 hours</figcaption></figure><p>You can easily see when a check has failed over time, and understand its uptime, and get a rich view of a check latency from each of our PoPs or internally:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*kSvAC0jX1ILDQ81CCAgWPA.png" /><figcaption>Round-trip time for a public URL check from our Singapore PoP</figcaption></figure><p>As always, we’re looking forward to hearing what you think, and if you’re not an Opsee user <a href="https://opsee.com">sign up</a> today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ff3adb49291" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/historical-data-and-performance-graphs-for-health-checks-9ff3adb49291">Historical Data and Performance Graphs for Health Checks</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring? Ain’t nobody got time for that]]></title>
            <link>https://medium.com/the-opsee-blog/monitoring-aint-nobody-got-time-for-that-97a7535642b0?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/97a7535642b0</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Wed, 25 May 2016 17:19:27 GMT</pubDate>
            <atom:updated>2016-05-25T17:19:27.973Z</atom:updated>
            <content:encoded><![CDATA[<h4>See what Opsee can do in a 2-minute demo from the SF Microservices meet-up</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fplayer.vimeo.com%2Fvideo%2F167768627&amp;url=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fvimeo.com%2F167768627&amp;image=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttp%2Fi.vimeocdn.com%2Fvideo%2F572140641_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1366" height="438" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ddc1956130979458fcf3667c632f26a/href">https://medium.com/media/3ddc1956130979458fcf3667c632f26a/href</a></iframe><p>More engineers are on autonomous teams that both write code and manage infrastructure. Fewer identify purely as engineers, having more operational responsibilities in addition to, you know, developing the software.</p><p>Many of us simply don’t have time to configure and maintain an open-source monitoring system, and many SaaS monitoring tools are powerful but expensive. There needs to be an easier, less expensive way to monitor our services and infrastructure.</p><p>In this brief demo we show a little of what Opsee can do to make that happen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97a7535642b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/monitoring-aint-nobody-got-time-for-that-97a7535642b0">Monitoring? Ain’t nobody got time for that</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with RDS Health Checks]]></title>
            <link>https://medium.com/the-opsee-blog/getting-started-with-rds-health-checks-3fe98550d006?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fe98550d006</guid>
            <category><![CDATA[rds]]></category>
            <category><![CDATA[cloudwatch]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Wed, 11 May 2016 16:59:59 GMT</pubDate>
            <atom:updated>2016-05-11T16:59:59.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uZHBTW4Ku-7lkHf2cRVkZA.png" /></figure><p>We’re excited to announce the first of our CloudWatch integrations: RDS. Among Opsee users, RDS is the most common AWS service apart from EC2, and it’s more popular than running RDBMS on EC2 instances–it seems not running a database is becoming a popular choice among dev teams.</p><p>While we’re not the first monitoring company to offer a CloudWatch integration, there are a few reasons why we believe ours is better.</p><h4>One check per target, for all metrics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*5z4Dgx2LIhJ9AIojBLA3aw.png" /><figcaption>Having multiple metrics on a single check minimizes failure notifications</figcaption></figure><p>We want to consolidate your notifications as much as possible. With Opsee, you don’t have to create a health check for each and every metric you think is important. Create one check for each <a href="http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html">RDS Database Instance</a>, and add as many metrics as you’d like to the check. This is an early effort toward a much larger project here, which you’ll hear more about later.</p><h4>Interactive Threshold Setting</h4><p>When you’re setting up thresholds on your metrics, we show you the last hour of data for context and let you see the impact of your thresholds as you’re setting them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*2vz5Prkebg2at7uksv15hQ.gif" /><figcaption>Interactive threshold setting</figcaption></figure><h4>Automatic health checks for each DB instance</h4><p>When you activate Opsee, we’ll automatically create a health check for each of your <a href="http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html">database instances</a>, with the following assertions:</p><ul><li><strong>CPU Utilization</strong> &lt; 95%</li><li><strong>Database Connections</strong> &lt; 90% of<a href="https://www.google.com/search?q=rds+max_connections+instance+size&amp;oq=rds+max_connections+instance+size"> max for instance size</a></li><li><strong>Freeable memory</strong> &lt; 10% of <a href="http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html#d0e12082">instance memory</a></li></ul><p>We’re able to determine the max connection count and memory for each of your instances, so we do these calculations for you.</p><h4>Recommendations</h4><p>A couple other specific metrics you’ll likely want to notify on, if you have them, are:</p><ul><li><strong>Replica lag</strong> — Monitoring replica lag can be an effective way to ensure your MySQL replicas are within an appropriate range of tolerance.</li><li><strong>ReadIOPS</strong>, <strong>WriteIOPS</strong> — If you’ve chosen to use provisioned IOPS for your RDS backing storage, you can monitor how effectively those IOPS are being used or if you are ever hitting your provisioned limits.</li></ul><p>Happy databasing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fe98550d006" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/getting-started-with-rds-health-checks-3fe98550d006">Getting Started with RDS Health Checks</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Team incident management with Opsee’s PagerDuty integration]]></title>
            <link>https://medium.com/the-opsee-blog/team-incident-management-with-opsees-pagerduty-integration-275c180156d6?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/275c180156d6</guid>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Mon, 09 May 2016 14:01:01 GMT</pubDate>
            <atom:updated>2016-05-09T18:03:44.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FdmNxcXeUlpBERtx4dL5AA.png" /></figure><p>We’re proud to announce our integration with PagerDuty for incident management. For any team managing an on-call rotation or escalation path PagerDuty been the application of choice for years now, and teams of all sizes are using it. Almost as soon as we had a product, we had customers asking us to integrate.</p><p>Opsee makes it easy to track the availability and performance of your services, and with PagerDuty integration it’s even easier to share that responsibility with your team and manage incidents together. If you’re new to PagerDuty, you can sign up for a <a href="https://signup.pagerduty.com/accounts/new">free trial</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c75eu62xOz2qeI8AxqtcxQ.jpeg" /><figcaption>Integrating Pagerduty with Opsee takes seconds</figcaption></figure><h4>Setup</h4><p>We’re also proud of how easy it is to add the integration to Opsee. Just visit your Profile page, and click the link to <strong>Connect to Pagerduty</strong>. After confirming the integration in Pagerduty, you’ll be able to add it as a notification to any new or existing health check. It only takes a few seconds, no more messing with webhooks.</p><p>For those not familiar with Opsee, we continuously test your services to ensure they’re working the way you expect, so you can get back to doing what you do best: shipping code. It only takes a few minutes to get complete coverage. <a href="https://opsee.com/#signup">Sign up today</a>.</p><p><strong>*Update:</strong> PagerDuty has published their own <a href="https://www.pagerduty.com/docs/guides/opsee-integration-guide/">integration guide for Opsee</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=275c180156d6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/team-incident-management-with-opsees-pagerduty-integration-275c180156d6">Team incident management with Opsee’s PagerDuty integration</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with HTTP health checks]]></title>
            <link>https://medium.com/the-opsee-blog/getting-started-with-http-health-checks-58491c006dd7?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/58491c006dd7</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Tue, 26 Apr 2016 00:01:53 GMT</pubDate>
            <atom:updated>2016-04-26T00:01:53.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXcUGg83nqN3JLuSL9eSlQ.png" /></figure><p>In this guide I’ll introduce you to some of the ways you can use <a href="http://opsee.com">Opsee’s HTTP health checks</a> to monitor your environment. Great health checks can save your dev team a ton of time by alerting you whenever a service is misbehaving or not responding the way you expect. You can learn more about the <a href="https://app.opsee.com/docs/checks">check types and targets we offer in our docs</a>, but there are basically two kinds of targets for HTTP health checks in Opsee:</p><p>1. AWS resources (e.g. Security Groups, ELBs, EC2 instances)<br>2. URLs (any public, or private, URL or IP address that’s accessible from our EC2 instance)</p><p>With different combinations of targets and assertions (the rules determining a passing check) you can create lots of useful health checks in Opsee. The goal of this guide is to introduce you to our checks and inspire you to create checks that will save you time and help you find problems faster.</p><p>The examples I’m going to cover in this guide are:</p><ol><li>Elastic Load Balancer (ELB) service response</li><li>Website availability with latency (opsee.com, backed by CloudFront CDN)</li><li>Website content &amp; defacement (google.com)</li><li>ElasticSearch</li><li>Consul</li><li>Dropwizard</li></ol><p>In each example I’ll list both the target of the check and the assertions used. These can be combined as well — for example, a single health check can cover the availability, performance, and content of your website. If you have any suggestions for this guide, or just want to get in touch, send an email to <a href="mailto:support@opsee.com">support@opsee.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4uYmQm015KKIqxL2Xd-cQ.png" /></figure><h4>Elastic Load Balancer (ELB) service response</h4><p>Targeting a health check at a load balancer normally masks what’s going on behind it, but Opsee automatically tracks ELB membership and targets instances directly to ensure not only that the ELB is functioning but that everything running behind it is as well. As you scale up and down there’s no need to update your check, since Opsee is continuously tracking changes to the ELB definition.</p><p><strong>Target:</strong> Elastic Load Balancer (ELB)</p><p><strong>Assertions:</strong></p><ul><li>Status Code <em>equal to </em><strong>200</strong></li><li>Header–Content-Type <em>equal to</em> <strong>application/json</strong></li><li>Header–Access-Control-Allow-Methods <em>equal to</em> <strong>GET,POST,DELETE,HEAD</strong></li><li>JSON Body — status <em>equal to</em> <strong>OK</strong></li></ul><p>Here, we’re checking that all of the backing instances are returning a 200 status code, that the content type is JSON, that the correct methods for the service are exposed, and that a specific key in the JSON response matches our expected value.</p><p>This check will work the same way when targeting a Security Group, Auto Scale Group, or just about any other dynamic resource in AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbAAQ1jRp_Yw6pKgUHvu9Q.jpeg" /></figure><h4>Website availability with latency (opsee.com, backed by CloudFront CDN)</h4><p>One of the most basic ways to track the health of your website is an availability check. Our website, <a href="http://opsee.com">opsee.com</a>, is backed by AWS’s CloudFront CDN. As with any CDN, it resolves to multiple IP addresses. Opsee will track all of the DNS entries for the site and make sure they’re all responding. Add in latency and you have a basic understanding of performance too.</p><p><strong>Target:</strong> <a href="https://opsee.com">https://opsee.com</a></p><p><strong>Assertions:</strong></p><ul><li>Status Code <em>equal to</em> <strong>200</strong></li><li>Response Body <em>is not empty</em></li><li>Metric–Round-Trip Time <em>less than</em> <strong>1,000ms</strong></li></ul><p>The status code ensures there are no service-level errors, and the response body check is an extra level of security that the response is coming back complete. Sub-second RTT on a website is a pretty conservative latency check, so be sure to calibrate this against your expected service level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mt6MD_vmSURFLB15xXxWCg.png" /></figure><h4>Website content &amp; defacement (Google.com)</h4><p>Nasty business getting your website hacked. Let’s make sure that doesn’t happen by putting some assertions in place for the Content-Type header and response body, as well as the response code.</p><p><strong>Target</strong>: https://www.google.com</p><p><strong>Assertions:</strong></p><ul><li>Response Body <em>contains</em> <strong>&lt;title&gt;Google&lt;/title&gt;</strong></li><li>Header–Content-Type <em>equal to</em> <strong>text/html; charset=ISO-8859–1</strong></li><li>Status Code <em>equal to</em> <strong>200</strong></li></ul><p>Validating specific content in the response is the most granular way to ensure your site’s content is right. A title tag is pretty basic, so use something specific to your site. Headers sometimes get mistakenly changed too, so verifying that along with the status code of will ensure a healthy and accurate website response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TQanAuHo02YPiO3JEaWkgA.png" /></figure><h4>ElasticSearch</h4><p>Elastic documents their health check endpoint well (<a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html">https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html</a>). Just target the <strong>/_cluster/health</strong> route and use the following assertions to ensure ES is in perfect health.</p><p><strong>Target</strong>: http://localhost:9200/_cluster/health</p><p><strong>Assertions:</strong></p><ul><li>JSON Body — status <em>equal to</em> <strong>green</strong></li><li>JSON Body — unassigned_shards <em>equal to</em> <strong>0</strong></li><li>JSON Body — active_shards_percent_as_number <em>equal to</em> <strong>100</strong></li><li>Status Code <em>equal to</em> <strong>200</strong></li></ul><p>A “red” status indicates that the specific shard is not allocated in the cluster, “yellow” means that the primary shard is allocated but replicas are not, and “green” means that all shards are allocated. The index level status is controlled by the worst shard status. The cluster status is controlled by the worst index status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*646MQlHqcCSi0_T5HENVkg.jpeg" /></figure><h4>Consul</h4><p>There are a few useful <a href="https://www.consul.io/docs/agent/http/health.html">health check endpoints available to Consul</a> users. In this example we’ll check that nothing is coming back in the critical state, and ensure that by checking for an empty array at that endpoint.</p><p><strong>Target</strong>: demo.consul.io/v1/health/state/critical</p><p><strong>Assertions:</strong></p><ul><li>Body <em>equal to</em> <strong>[]</strong></li><li>Status Code <em>equal to</em> <strong>200</strong></li></ul><p>We’re simply ensuring that the service is responding and that there are no entries in the array of critical services. There are more detailed service and node checks available to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPNjMdg9wEUUIyRix9DFUg.jpeg" /></figure><h4>DropWizard</h4><p>The library <a href="https://dropwizard.github.io/metrics/3.1.0/manual/healthchecks/">provides a convention</a> for defining health checks by extending the HealthCheck class. These can be pretty simple, returning just an “OK” or “FAIL” state based on the results of an internal check.</p><p><strong>Target</strong>: http://localhost:8080</p><p><strong>Assertions:</strong></p><ul><li>Body <em>equal to</em> <strong>OK</strong></li><li>Status Code <em>equal to</em> <strong>200</strong></li></ul><p>It’s good practice to verify any hard dependencies in a DropWizard health check. So if your service relies on a database, doing a simple <strong>`select 1;` </strong>against it in the health check endpoint will ensure that the database is connected and responding.</p><h4>How do you health check your services?</h4><p>We’d love to know how you health check your services. Write us a response, and tell us more about the services you’re checking and how you check them. We‘re always looking for ways to make Opsee better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58491c006dd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/getting-started-with-http-health-checks-58491c006dd7">Getting started with HTTP health checks</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring Built for AWS]]></title>
            <link>https://medium.com/the-opsee-blog/monitoring-built-for-aws-49c989c6a2c?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/49c989c6a2c</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Thu, 31 Mar 2016 16:31:47 GMT</pubDate>
            <atom:updated>2016-04-05T23:51:44.227Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Zo_rYOBKvPnO638dKazaw.png" /></figure><h4>We auto scale with you, reacting instantly whenever your environment changes, with no agents to install or shell scripts to cURL</h4><p>From our earliest days as a company we wanted the experience of using Opsee to be special. Monitoring isn’t an experience you’d normally call effortless or minimal, but it’s what we set out to achieve. With public cloud services like AWS, there’s a lot we can do to make monitoring effortless. We have a decent idea what your services and systems are doing, and what they’re <em>supposed to be doing</em>, using environment data. That’s the basis for the experience we’re trying to create.</p><h4>Getting Started</h4><p>All you need are AWS keys to get started with Opsee. We don’t install agents on your systems–instead, we add a new EC2 instance to your environment that’s responsible for health checking and discovery:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qU8NUeAh67oruW_lm7dHnw.png" /><figcaption>Just enter AWS keys. We’ll add our instance and cover your environment</figcaption></figure><p>Here’s how it works:</p><ol><li>You use <a href="https://app.opsee.com/docs/IAM">our IAM guide</a> to create a temporary user for installation. Importantly, these keys are used only once and never stored. You can delete the user as soon as installation is done</li><li>You tell us where to add our instance. Just choose an AWS region, VPC, and subnet and <em>we’ll do the rest.</em> We use a <a href="https://app.opsee.com/docs/permissions">CloudFormation template and AMI for our instance, and its permissions are defined by a couple of IAM roles</a></li></ol><p>That’s it! Once our instance is added, and you can easily create health checks for your infrastructure and services–we even try to <em>create checks for you</em>. We do a lot more than help you get started with monitoring, though. Our deep integration with your AWS environment is running continuously.</p><h4>Rich Context and Actionable Notifications</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*H7HiPA_jIRVRXwPwhVhH7A.gif" /><figcaption>Instance actions like restarts are simple</figcaption></figure><p>Two of the biggest benefits to using Opsee are rich and actionable notifications. Since we know where a failure occurs within a target group, we:</p><ol><li>show you the failing response in our notifications</li><li>point you to the failing instance(s) in a group, and</li><li>give you quick access to instance actions like restarts in Opsee.</li></ol><h4>Security Benefits</h4><p>There are some notable security benefits to this model:</p><ul><li>Since we don’t install any software on your systems, the probability of us crashing them is significantly lower than it would be with an agent</li><li>Our instance credentials are cycled every hour, making them a lot harder to grab</li><li>Any credentials required to run health checks are stored in an encrypted EBS volume inside your environment</li><li>Our instance’s auto scale group ensures that you always have one running</li><li>Uninstalling is as easy as activating. Should you ever need to, you can completely remove Opsee by simply deleting our CloudFormation stacks</li></ul><h4>Discovery and Auto Scaling</h4><p>The most important thing to know about Opsee health checks is that when they’re attached to dynamic targets they never need updating. Discovery is running continuously, adapting when your environment changes. Our instance captures environment data using AWS APIs, keeping your checks up to date. There are no configurations to manage or YAML files to update.</p><h4>Plans for the Future</h4><p>This model lets us make some pretty interesting updates in the future. For example:</p><ul><li>Running multiple, redundant instances inside your environment can make Opsee highly available, even in parts of your network that aren’t exposed to the internet</li><li>Opsee could run without a persistent connection to the internet, allowing it to continue running checks offline. This is interesting territory for a SaaS monitoring product</li></ul><p>We think this is a better way to do monitoring: deeply integrated with your environment, with richer context, better performance, and <strong>a lot less work</strong> to get started and maintain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49c989c6a2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/monitoring-built-for-aws-49c989c6a2c">Monitoring Built for AWS</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Health Checks: Your First Line of Defense]]></title>
            <link>https://medium.com/the-opsee-blog/health-checks-your-first-line-of-defense-17d6b9c94383?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/17d6b9c94383</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Mon, 29 Feb 2016 17:57:35 GMT</pubDate>
            <atom:updated>2016-02-29T17:57:35.933Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuyMX35SHzJsngCIGoH5fQ.png" /></figure><h4>There’s an easier way to be sure your services are working as you expect — Opsee’s health checks have you covered</h4><p>Health checks are the core of the <a href="https://opsee.com/">Opsee product</a>. You create checks for your services and infrastructure, and we seamlessly integrate with your AWS environment so your checks are always up-to-date.</p><p>Our health checks do some things we’re really proud of:</p><h4>They’re Automatic</h4><p>When you start using Opsee, we discover your infrastructure and services and create health checks automatically:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1g4dMyiHAx-hPRRBzfjb9A.png" /><figcaption>Just enter AWS keys and add our instance to cover your environment</figcaption></figure><h4>They’re Elastic</h4><p>When you create a health check for a dynamic target like an ELB, Security Group, or Auto Scaling Group, that check never needs maintenance as the target changes. We track changes and react instantly.</p><h4>They Have Meaningful Assertions</h4><p>Service health is more than a status code. In Opsee you can also set assertions against the headers and body of a response, including specific JSON keys in a response body.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*LAtFJvniw9kt8GpT34KxYA.png" /><figcaption>Assertions on status codes and response bodies ensure correctness</figcaption></figure><h4>They Show You What Went Wrong</h4><p>When a check fails in Opsee, we capture the failing responses to show them when and how it failed. This gives you some better context to understand what happened and fix it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9fGtu1JMD1opSGI6C8I4aw.png" /><figcaption>A failing event showing a complete response for context</figcaption></figure><h4>They Help You Take Action</h4><p>Deep integration with AWS means you can do things like restart problem instances right from the Opsee app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*bvKNoagml7fBSGLiFCHo0w.gif" /><figcaption>Actions like instance restarts are available from the app</figcaption></figure><h4>They’re the Start of Something Bigger</h4><p>This is just the beginning of what we plan to do with health checks in Opsee. If you like what you see, <a href="http://www.opsee.com">sign up and try</a> out the product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17d6b9c94383" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/health-checks-your-first-line-of-defense-17d6b9c94383">Health Checks: Your First Line of Defense</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s Talk About Developer Experience (DX) Design]]></title>
            <link>https://medium.com/the-opsee-blog/let-s-talk-about-developer-experience-dx-design-f62ee4c2ee05?source=rss-606cadd4e408------2</link>
            <guid isPermaLink="false">https://medium.com/p/f62ee4c2ee05</guid>
            <category><![CDATA[dx]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Steve Boak]]></dc:creator>
            <pubDate>Tue, 19 Jan 2016 17:16:20 GMT</pubDate>
            <atom:updated>2016-01-19T17:16:20.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Do5nqcLRiJ9FnupS706Bw.png" /></figure><p>I’m a designer, but I have some trouble talking with other designers about what I do. I make developer tools, and though our goals are the same there’s a lot about this work that other designers don’t relate to. On-boarding new users is complicated (<em>does your product require new users to deploy code?</em>), the importance of good API documentation can’t be overstated, and building a successful product means becoming part of a developer’s flow.</p><p>As software consumes the world around us, good design in our tools is a growing competitive advantage. The term <strong>Developer Experience (DX) Design</strong> isn’t getting used much right now, but it has a huge impact. Our tools shape our work, and great tools change the shape of our industry. The influence Amazon Web Services (AWS) has on the way we write and deploy code, the impact that Twilio has had on the availability of VOIP in our applications, and the iOS SDK’s introduction of an entirely new platform to developers are just a few examples of the impact our work can have when we do it well.</p><p>We talk a lot about the importance of a strong engineering team, but not enough about the design of our tools and the impact it has on the quality of the products we build. We should be talking about DX more, and it’s not enough to talk about UX alone.</p><h4>What Makes DX Different?</h4><p>The conversation about UX still feels fresh, and design’s seat at the table is still being earned. With all this new attention on UX, why should we fork DX into its own topic?</p><ol><li><strong>Our Customers Write Code</strong><br>Early use of the term DX was more-or-less synonymous with API design, which definitely isn’t something a typical product designer is concerned with. Though a well designed API with strong documentation and example code is important, it’s not always applicable — and in a fast-growing ecosystem of developer tools, designing the developer experience is about much more than that. It’s about how we weave our tools into the everyday workflows of developers, which will mean different things to each of us, and it’s a unique and important consideration in building our products.</li><li><strong>The Stakes Are High</strong><br>We ask for a lot of trust, and have to earn it. If our product goes down, our users don’t want to see their own products taken down with it. Potential customers try us out in personal or staging environments before they risk putting us in production, so we have to show value in less than ideal circumstances. We have to earn trust by designing experiences that feel intuitive and powerful <em>before</em> we get the keys to the castle.</li><li><strong>Designing Developer Tools Is a Partnership</strong><br>As a designer building products for developers, I’m dependent on a design-focused engineering team to help me find elegant solutions to our product problems. In the past few months alone I’ve had to learn how container scheduling works, how VPCs and subnets work, and how to measure the health and performance of a SQL database. I can try (and have tried) to design solutions to these problems in a vacuum, but it fails every time. One of the reasons I like designing in this space is getting to work with great engineers who care about improving their tools, and since I’m not a user of the product I need lots of help. I think this is a barrier to entry for a lot of designers, which means there’s also a lot of opportunity for improvement.</li></ol><p>There are, however, problems with focusing on DX at the expense of UX as a whole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RNq0vrY36SvPTLuZX8osMg.png" /><figcaption>Monitoring tools generally aim to maximize information density at the cost of usability</figcaption></figure><h4>What’s Important to Remember About UX?</h4><p>Thinking of our customers as experts and power-users can be a red herring. As we aim to design better tools, we need to keep a few universal UX principles in mind:</p><ol><li>Our customers can write code, but that doesn’t mean they want to. What they want is the same as any other user: “<a href="http://www.amazon.com/Dont-Make-Me-Think-Usability-ebook/dp/B000SEGQNS/ref=mt_kindle"><em>don’t make me think</em></a><em>”</em>.</li><li>Designing for power-users, we tend to maximize information density and functionality at the cost of usability. Simplicity and clarity are always the most important goals in designing a product, no matter who the user is.</li></ol><p>This is only the beginning of the conversation, though.</p><h4>Let’s Continue the Conversation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/164/1*uX1rRyayBIqVlpa8yp80Ig.png" /><figcaption><a href="http://www.twitter.com/dontmakemecode">@dontmakemecode</a></figcaption></figure><p>If you want to talk more about DX, you’re in luck. I’m co-hosting a new podcast called Don’t Make Me Code with <a href="https://medium.com/u/8472d18c15e">David Dollar</a>, CEO of Convox and founding member of the DX team at Heroku. Find us on Twitter <a href="http://www.twitter.com/dontmakemecode">@dontmakemecode</a>. We’re releasing our first episode on Wednesday, January 20th. We’d love to hear about your experiences building developer tools, and to have you as a guest on the show. Email us at <a href="mailto:dmmc@heavybit.com">dmmc@heavybit.com</a> if you’re interested.</p><p>You can follow me on Twitter <a href="http://twitter.com/sboak">@sboak</a>. I’m looking forward to a lot more conversation about DX.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f62ee4c2ee05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-opsee-blog/let-s-talk-about-developer-experience-dx-design-f62ee4c2ee05">Let’s Talk About Developer Experience (DX) Design</a> was originally published in <a href="https://medium.com/the-opsee-blog">The Opsee Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>