<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jonas</title>
    <description/>
    <link>https://speakerdeck.com/jonaseconomist</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/jonaseconomist.rss"/>
    <lastBuildDate>2018-05-03 09:18:37 -0400</lastBuildDate>
    <item>
      <title>Digital Publishing for Scale: The Economist and Go</title>
      <description>The Economist newspaper was first printed in 1843. Since then, readers consume news in rapidly evolving ways and technology has taken the forefront in delivering content and enabling the severe contest between intelligence, which presses forward, and an unworthy, timid ignorance obstructing our progress.

To meet these challenges, The Economist restructured its platforms for digital delivery by breaking down a monolithic CMS and adopting a distributed, microservices architecture. The Economist implemented Go to write services responsible for delivering content across products and platforms. Go has enable the team to quickly adapt to business needs and scale for growing demand, but it has not been without its own challenges. This talk will cover the struggles and victories in transitioning to Go and how Go has uniquely fit The Economist’s digital publishing goals.</description>
      <media:content url="https://files.speakerdeck.com/presentations/c8747c7aaed54ac38ad690772ac01930/preview_slide_0.jpg?10316368" type="image/jpeg" medium="image"/>
      <content:encoded>The Economist newspaper was first printed in 1843. Since then, readers consume news in rapidly evolving ways and technology has taken the forefront in delivering content and enabling the severe contest between intelligence, which presses forward, and an unworthy, timid ignorance obstructing our progress.

To meet these challenges, The Economist restructured its platforms for digital delivery by breaking down a monolithic CMS and adopting a distributed, microservices architecture. The Economist implemented Go to write services responsible for delivering content across products and platforms. Go has enable the team to quickly adapt to business needs and scale for growing demand, but it has not been without its own challenges. This talk will cover the struggles and victories in transitioning to Go and how Go has uniquely fit The Economist’s digital publishing goals.</content:encoded>
      <pubDate>Fri, 29 Jun 2018 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/jonaseconomist/digital-publishing-for-scale-the-economist-and-go</link>
      <guid>https://speakerdeck.com/jonaseconomist/digital-publishing-for-scale-the-economist-and-go</guid>
    </item>
    <item>
      <title>Happy Path To Go - GothamGo 2018</title>
      <description>You’ve been hired for an exciting new role where you’ll use Go for the first time. After your whirlwind week of training, guess what? You have to transition your team of engineers to Go. Good luck! This talk gives practical advice for building a learning culture that empowers engineers to master Go.</description>
      <media:content url="https://files.speakerdeck.com/presentations/9b9571561bdf41979651bfba8f6f65d0/preview_slide_0.jpg?9963437" type="image/jpeg" medium="image"/>
      <content:encoded>You’ve been hired for an exciting new role where you’ll use Go for the first time. After your whirlwind week of training, guess what? You have to transition your team of engineers to Go. Good luck! This talk gives practical advice for building a learning culture that empowers engineers to master Go.</content:encoded>
      <pubDate>Fri, 27 Apr 2018 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/jonaseconomist/happy-path-to-go-gothamgo-2018</link>
      <guid>https://speakerdeck.com/jonaseconomist/happy-path-to-go-gothamgo-2018</guid>
    </item>
  </channel>
</rss>
