<?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 Iddo Gino on Medium]]></title>
        <description><![CDATA[Stories by Iddo Gino on Medium]]></description>
        <link>https://medium.com/@iddo.gino?source=rss-f7bffa07e84b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XkbNnMNpXrE2El8hyFe6iw.jpeg</url>
            <title>Stories by Iddo Gino on Medium</title>
            <link>https://medium.com/@iddo.gino?source=rss-f7bffa07e84b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:26:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iddo.gino/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[Investments in API Companies Doubled in 2018, Surpassing 1 Billion Dollars]]></title>
            <link>https://medium.com/the-era-of-apis/investments-in-api-companies-doubled-in-2018-surpassing-1-billion-dollars-2138157065dd?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2138157065dd</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Tue, 11 Dec 2018 15:01:00 GMT</pubDate>
            <atom:updated>2018-12-11T17:04:48.784Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>2018 has been a great year for API companies. We’ve seen 88 investments in API start-ups, billions of dollars in M&amp;A activity and public API companies’ valuations doubling and tripling.</strong></p><p>Over the past few years, we have been closely tracking the growth and expansion of the API economy. Every year, we are excited to see how newer and established API companies are faring financially as an indicator to the future of the API economy. Their phenomenal and consistent growth are a testament to how fundamental APIs have become in software development, and to how wide their usage have spread.</p><h3>What are APIs &amp; API Companies?</h3><p>APIs are pieces of functionality that developers can connect to and embed into their applications to perform various actions. These actions can include sending a text message (APIs: Twilio, Nexmo, Telesign), processing a credit card payment (APIs: Stripe, Braintree, Adyen) or recognizing faces in images (Microsoft Computer Vision, Kairos, AWS Rekognition), to name a few.</p><p>Where in the past developers would have had to implement these functions from scratch (assuming they even had the expertise and experience required), today they can rely on 3rd parties to provide these services — via APIs.</p><p>The benefits of using APIs in software development are abundant. They allow developers work faster and more efficiently, as they don’t have to implement those different functions from scratch. They offer better service levels, as API companies have deeper industry expertise around the individual functions, and often are able to offer an overall lower price point, by providing multiple customers with the same service and thus leveraging economies of scale.</p><p>When speaking of companies in the API economy, we refer to companies that are either building and offering APIs to developers, or are offering tools for building / consuming APIs. This is the definition used throughout the report.</p><h3>Investment in API Startups</h3><p>In 2018 alone, API startups raised $1.06 billion dollars in venture funding, according to press releases and Crunchbase data. This signifies a significant increase in fiscal activity, compared to only about $500M invested in both 2016 and 2017.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jjd1z8ed64yVffOo" /></figure><p>The average round size this year was $12.1M — indicating an increase in maturity and later financing rounds in the space. At the same time, 47 early stage rounds (pre-seed to Series A) made up 53% of the total number of rounds, showing a healthy count of new companies fueling innovation in the space. Those companies made up 12% of the total cash invested ($125M), putting the average early stage API round at $2.7M.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jAA_G2yE2a_zglRB" /></figure><p>The largest investment we’ve seen this year was Stripe’s $245M Series E, led by Tiger Global, together with Sequoia, Kleiner Perkins and others. This round puts the payment processing giant at a valuation in excess of $20B, well positioned to continue its growth in credit card processing, as well as expanding into new product lines. Stripe has recently launch a card issuing API — letting developers issue and manage physical and virtual credit cards, and announced a new terminal product, letting developers create in-store payment solutions using a new set of APIs.</p><h3>Acquisitions of API Companies</h3><p>2018 was a very active year for M&amp;As in the API space with 25 acquisitions — a 32% increase from last year. The most notable (and the largest) deal was the $6.5 billion acquisition of MuleSoft by Salesforce. MuleSoft, who is focusing on API and data integration, should fit well into Salesforce’s overall strategy of integrating with all its customers data sources and systems, in order to provide more value and critical insights across the organization. In conjunction with Heroku (which Salesforce acquired in 2010 for $212M) and force.com, MuleSoft will help bolster Salesforce’s portfolio of tools and solutions to allow developers to build on top of its platform.</p><p>Another notable deal was Twilio’s $2B acquisition of SendGrid. Twilio, positioning itself as a communications platform, will add SendGrid’s email APIs to its existing portfolio of SMS and Voice APIs. As competition with other telecommunications API companies (Nexmo, Telesign etc.) becomes more fierce, it makes sense for Twilio to expand horizontally into other parts of customer communications. With SendGrid clearly being the market leader in email communications, Twilio now has market leading solutions in multiple communication channels. This horizontal expansion also allows it to offer a more unified customer communication offering in the future, aggregating different channels (chat apps, SMS, email, fax etc…) into a single convenient API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lRvvfDNr6XwiN5Ms" /></figure><h3>Public API Companies Performance</h3><p>Post-IPO API companies have also been showing solid growth, continuously beating earning projections and creating new value. Both SendGrid and Twilio have grown well, with the former doubling its market cap in the past year and the latter more than trippeling it.</p><p>MuleSoft, prior to it’s $6.5B acquisition by SalesForce also showed positive growth as a public company. It’s stock soared 83% in just 5 months — from $24 in January 2018 to over $44 in May when it was acquired. The pattern of post-IPO acquisitions isn’t new in the API space. In 2016, Google acquired API Gateway leader Apigee when the latter was publicly traded.</p><p>The solid growth of public API companies alongside the high value M&amp;A activities prove that API companies can create sustainable business models in the long run, and continue growing long past infancy. This is a very strong validation for the API economy, showing that entire public company can be created around supplying developers with an API. This has now been proven true time and time again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*66qdwtIIQ4zPqsSw" /></figure><h3>So What’s in Store for 2019?</h3><p>APIs as enablers of faster and more democratized software development are on the rise. With multiple years of consistent growth from API companies and continued adoption of APIs by companies large and small, it’s clear the API economy is here to stay. As it continues to grow in 2019, there are several key trends that we think will drive much of the growth:</p><p><strong>Big Cloud Vendors</strong></p><p>Traditionally, the large cloud providers (AWS, Azure and Google Cloud) have focused most of their efforts on offering lower level infrastructure (compute, networking, storage etc.), leaving the higher level APIs for other startups and companies. This focus made sense when most companies were just moving to the cloud and the big vendors had to establish stable &amp; feature rich infrastructure to attract these large accounts.</p><p>However cloud is becoming more ubiquitous and workloads are becoming more cloud-agnostic (able to switch between vendors) thanks to platforms like Docker, Kubernetes and Serverless. This commoditization of the cloud sends these large cloud providers after ways to add value and create lock in with higher level services in the form of APIs.</p><p>All three leading vendors have released a lot of APIs in the fields of AI, visual recognition, translation, file manipulation and other areas in 2018. AWS’s annual re:Invent conference was jam-packed with API announcements, dominated by machine learning API solutions. Microsoft similarly focused on many cloud vision and machine learning APIs at its annual Connect() conference, and has a wide catalog of dozens of higher level API services as part of it’s Azure offering.</p><p>In 2019 as those big vendors look to move up the stack, we expect to see a wealth of new API services being offered on top of the basic cloud infrastructure.</p><p><strong>Internal APIs</strong></p><p>The rise of APIs is a part of a wider microservices trend: software is built by composing many smaller services, some of which are bought from external providers (“APIs”) and some of which are built and maintained internally (“Internal APIs” / “Microservices”). Larger enterprises are adopting this paradigm — developing many internal services that teams connect to in order to create user facing products.</p><p>According to a recent survey conducted by Cybersecurity firm Ping Identity, 25% of companies have over 1,000 internal APIs or microservices, and another 35% have 400–1,000 internal APIs.</p><p>Managing such a wealth of internal APIs breeds a host of challenges for responding companies. These include ensuring developers can easily discover and access those internal APIs while ensuring IT leadership has clear visibility into API usage and data flow within the organization.</p><p>As the number of internal APIs in companies increases in 2019, and the awareness of CIOs and CISOs to the challenges they breed rises, we’ll see more tooling and methodologies created to manage these internal APIs at scale.</p><p><strong>DaaS</strong></p><p>Data as a Service or DaaS APIs are a subset of the overall API economy, focusing on delivering key data that can enhance business processes via APIs. With the rise of artificial intelligence and machine learning, data is becoming the new oil. Companies are constantly looking for more data sources they can utilize to enrich their datasets to improve AI &amp; ML capabilities. As more of these models are being productionzied, companies are looking for data sources that are dynamic — like APIs they can call at runtime to enrich data and make live predictions (not just training).</p><p>This need has been fueling a breed of DaaS APIs like Crunchbase (providing information about companies &amp; fundraising), FullContact (enriching lead data) and PredictHQ (live &amp; historic data about global events). As artificial intelligence and machine learning becomes more prevenant in production use cases, the need for these DaaS APIs will increase, and we’ll see more types of data offered.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2138157065dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-era-of-apis/investments-in-api-companies-doubled-in-2018-surpassing-1-billion-dollars-2138157065dd">Investments in API Companies Doubled in 2018, Surpassing 1 Billion Dollars</a> was originally published in <a href="https://medium.com/the-era-of-apis">The Era of APIs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mashape’s API Marketplace is now part of RapidAPI]]></title>
            <link>https://medium.com/the-era-of-apis/mashapes-api-marketplace-is-now-part-of-rapidapi-53701442f5e4?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/53701442f5e4</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Tue, 23 May 2017 16:31:01 GMT</pubDate>
            <atom:updated>2017-05-23T16:31:01.167Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lzlN2bdP3FywjNk34fbZcg.jpeg" /></figure><p>In <a href="https://medium.com/the-era-of-apis/connecting-the-worlds-software-chapter-1-f2be8a59843b?utm_source=Mashape_Announcement_Post_Medium&amp;utm_medium=Link_RapidAPISeed&amp;utm_content=Mashape_Announcement">RapidAPI’s launch blog post</a> back in November 2016, I outlined RapidAPI’s mission and plan: to connect all the software in the world by helping developers find and consume APIs more easily. Today, Mashape’s API marketplace is merging into RapidAPI to form the world’s largest API hub. Developers can now find, test and connect to over 7,500 APIs in one place.</p><p><a href="https://www.youtube.com/watch?v=2kY45BBLM2U">https://www.youtube.com/watch?v=2kY45BBLM2U</a></p><p>We’re excited to continue working with the Mashape team to make this transition as smooth and easy as possible.</p><h3>Why APIs Matter</h3><p>Software is <strong>exponentially more powerful</strong> when it communicates. Think about it. When you login to a gaming app with Facebook, you can see all your friends who play. When Amazon’s shopping portal connects with the warehouse inventory, you get shipping estimates in real-time. And when you book a flight? It’s already scheduled in your Google Calendar.</p><blockquote><strong>Software alone is powerful, but connected software is game-changing.</strong></blockquote><p>APIs make these connections possible. They allow different pieces of software to talk to each other, share information and make our lives easier.</p><p>Looking forward, APIs are opening doors not previously thought possible. With an API, any developer in the world can access supercomputers from IBM, machine learning models from Google and big data from the world’s largest social networks. We’re not the only ones who recognize the power of APIs. Last year, <a href="https://medium.com/the-era-of-apis/over-500m-invested-in-api-companies-in-2016-with-16-acquisitions-cc4f3d2beef8?utm_source=Mashape_Announcement_Post_Medium&amp;utm_medium=Link_500MillionAPIs&amp;utm_content=Mashape_Announcement">over $500 million</a> was invested in API-driven companies. <a href="https://www-03.ibm.com/press/us/en/pressrelease/48026.wss">IBM estimates</a> that the API economy will become a $2.2 trillion market by 2018.</p><p>In order to fully realize this potential, we want to make it easier for developers to find, test and connect to APIs. Our plan has always been to consolidate all of the APIs in the world under one roof. Merging the Mashape API marketplace into RapidAPI makes that goal closer than ever. Together, we have 370,000 developers making 300 billion API calls a month. That’s over 100,000 API calls a second.</p><h3>What this means</h3><p>Starting today, you can use either a RapidAPI or Mashape account to log into both platforms. Your existing apps and APIs will work the same (no code changes necessary!), but you can now view your analytics and projects through different interfaces.</p><p>Most importantly, you can now explore over 7,500 APIs. Find <a href="https://rapidapi.com/package/NasaAPI/functions?utm_source=Mashape_Announcement_Post_Medium&amp;utm_medium=Link_NASAFunctions&amp;utm_content=Mashape_Announcement">the closest asteroid </a>to you with the NASA API. Pull the <a href="https://rapidapi.com/package/SpotifyPublicAPI/functions?utm_source=Mashape_Announcement_Post_Medium&amp;utm_medium=Link_SpotifyPublicFunctions&amp;utm_content=Mashape_Announcement">best running playlists</a> with the Spotify Public API. You can even make your app <a href="https://rapidapi.com/user/ismaelc/package/Yoda%20Speak/functions?utm_source=Mashape_Announcement_Post_Medium&amp;utm_medium=Link_YodaSpeakFunctions&amp;utm_content=Mashape_Announcement">talk like Yoda</a>.</p><p>For more information, check out our <a href="https://www.youtube.com/watch?v=UafJPrMx4Jk">intro to RapidAPI</a>, visit our <a href="https://goo.gl/utlfuv">full list of FAQs</a>, browse our <a href="https://goo.gl/xEO4o4">docs</a> or contact us at support@rapidapi.com.</p><h3>RapidAPI and Mashape moving forward</h3><p>Working with Mashape has been an absolute pleasure. We look forward to seeing what Mashape builds as it expands its full API gateway suite (including Kong). We will also be in constant communication as RapidAPI grows and expands the API marketplace.</p><h3>Further questions</h3><p>We welcome your feedback and questions. You can reach us at <a href="/service/mailto:support@rapiapi.com">support@rapiapi.com</a> as well as read <a href="https://goo.gl/utlfuv">FAQs</a> and <a href="https://goo.gl/xEO4o4">documentation</a> or browse our <a href="https://goo.gl/9YSMvh">product road map</a>.</p><p>We can’t wait to see what you build!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53701442f5e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-era-of-apis/mashapes-api-marketplace-is-now-part-of-rapidapi-53701442f5e4">Mashape’s API Marketplace is now part of RapidAPI</a> was originally published in <a href="https://medium.com/the-era-of-apis">The Era of APIs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Israeli Queues: Exploring a Bizarre Data Structure]]></title>
            <link>https://medium.com/the-era-of-apis/israeli-queues-exploring-a-bizarre-data-structure-2d37d32fa3d9?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d37d32fa3d9</guid>
            <category><![CDATA[israel]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[data-structures]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Wed, 11 Jan 2017 19:40:11 GMT</pubDate>
            <atom:updated>2017-01-11T20:02:32.379Z</atom:updated>
            <content:encoded><![CDATA[<p>This morning, I stumbled upon a data structure called an Israeli queue. As I’m flying to Israel tomorrow, I had to check it out. It turns out that the Israeli queue data structure isn’t just a punny data structure, it’s a useful one too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*aH8JYYRRqZ_w-PvX." /><figcaption>Source: <a href="http://www.houstonchronicle.com/business/article/Airlines-say-Congress-is-contributing-to-long-7781523.php">The Houston Chronicle</a></figcaption></figure><p>The name comes from the fact that Israel is notorious for extremely unorganized queues or lines. I can say that — I’m from there. Because of the disorganization, people tend to find their friends and wait in line with them. Similarly, an Israeli queue data structure is based on grouping and prioritizing items based on “friendships.” Here’s how it works.</p><h3>Defining simple priority queues</h3><p>The idea behind priority queues is pretty simple: you have a collection of items / tasks that need to be performed, and you can pull out one item at a time. When inserting items into a priority queue, you attach a <strong>priority</strong> to each item. When pulling those items out (dequeuing), the item with the highest priority at that point will get dequeued. Here’s an example of a first-in, first-out (FIFO) queue (prioritized by time of entry).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/0*bSSUKS-qB5L_FTkQ." /><figcaption>Source: <a href="https://en.wikipedia.org/wiki/Queue_(abstract_data_type)">Wikipedia</a></figcaption></figure><p>An example for the use of priority queue could be the queue for an MRI scan in a hospital.</p><p>Imagine the following scenario*:</p><p><em>*Following example based on my binge watching House MD and thus is probably not medically correct. Be warned.</em></p><blockquote><strong>Patient 1-Abdominal pain: </strong>The first person waiting is a patient with unexplained abdominal pain. The doctor recommends an MRI to see if there are any problems, but it’s not urgent as the situation is not life-threatening. The patient is placed in the queue for the MRI with a low priority of 1.</blockquote><blockquote><strong>Patient 2-Lung cancer: </strong>Another patient arrives with suspected lung cancer. A lung MRI is required to confirm the diagnosis and start treatment. The faster the treatment starts, the higher his chances of healing are. He’s placed on the queue with priority 5, bumping him to the top.</blockquote><blockquote><strong>Patient 3-Car accident: </strong>But then, a car accident occurs. A critical patient comes in and requires an MRI to locate an abdominal bleeding. As this condition is immediately life-threatening, she is enqueued with a 10 priority.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*NhUMHqno-dbrbzj0." /><figcaption>Source: <a href="http://www.memecenter.com/fun/93341/Cat-Scan">Memecenter</a></figcaption></figure><p>This emergency room scenario demonstrates the simple idea of priority queues that we’ll try to improve upon with Israeli queues.</p><h3>The need for grouping</h3><p>Let’s introduce a new concept — <strong>friendship</strong> between items on the queue. Items can be friends if they are somehow related and if it makes sense for them to be performed together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*PuQPA3B9U5Nk413y." /><figcaption>Source: <a href="http://giphy.com/gifs/joey-lawrence-ld1RKulOqeeaI">GIPHY</a></figcaption></figure><p>Imagine the lung cancer patient from the previous scenario has <em>also</em> been complaining about mild headaches. The doctor recommends a head MRI scan and, as the issue is not urgent nor immediately life-threatening, assigns it with a low priority of 1.</p><p>We can think of the patient’s (let’s call him Patient X) two required scans as ‘friends’. These are two separate scans: one in the lungs and another in the head. However, if Patient X is already admitted and in the imaging wing for his higher priority lung scan, the doctor <em>might as well</em> do the head scan at the same time. Those two tasks are friends.</p><p>The reason doing both a high priority and low priority scan simultaneously makes sense is because the <em>cost to do both at once is lower than doing each separately.</em> Why? We can think of both of these tasks’ costs as composed of two parts:</p><ul><li><strong>Set-up cost</strong> — the cost of preparing for the task, which is shared amongst friend tasks</li><li><strong>Execution cost — </strong>the cost of actually executing the task.</li></ul><p>In the MRI scan, the set-up cost includes bringing the patient in, instructing him, asking some questions and explaining the operation. The execution cost is the actual scan.</p><p><em>For friend tasks, the set-up cost is only deducted once</em>. In our MRI example, even if we do five scans, as long as they are on the same person (and thus, friend tasks), we only ‘pay’ the set-up cost once. However, we still pay the execution cost five times.</p><h3>Use case: situations with high set-up costs</h3><p>Since the set-up cost is only deduced once in an Israeli queue,<strong> if set-up cost is high, it may make sense to group together friend tasks.</strong> Another example of this is industrial printing. Imagine a case where you have a monochromatic manual printer. You can put one color in it at a time, and print in that colour. You get a lot of orders, and each has a different priority (e.g. “We need those flyers ready for a parade tomorrow” vs. “we need that newspaper printed by the end of the week”). However, it takes time to switch the colour in the printer — that constitutes the setup cost of those tasks. Thus, it may make sense to make jobs of similar colors ‘friends’ and perform them all together.</p><h3>The algorithm</h3><p>We’ll start off with a basic priority queue, making two critical changes:</p><ol><li><strong>Groups:</strong> Instead of just containing items, the queue will contain <em>groups</em> of items. Groups may have one or more items in them, but cannot be empty. They may be organized in order (by priority) or not. A group will only contain enqueue items that are friends.</li><li><strong>Enqueueing: </strong>When enqueueing a new item, we’ll iterate over all the groups in the queue. If the item being inserted to the queue is friend with an item in any of the group (friendship is a transitive relation, so if he’s friend with one, he’s friend with all), the item will be added to the group and its priority will be added to the group’s priority (group priority is sum of its members).</li></ol><p>Here’s the pseudo code:</p><pre>def <strong>Insert_Item</strong>(queue, item):<br>//Check if there is a friendly group. If so — add to that and return</pre><pre>For group in queue.groups:</pre><pre>   If (are_friends(item, group[0])):</pre><pre>     group.append(item)</pre><pre>     group.priority += item.priority</pre><pre>     return</pre><pre>//Reached here — no friendly groups</pre><pre>G := new Group(members = [item], priority = item.priority);</pre><pre>queue.enqueue(G)</pre><p>And there you have it! It actually turns out pretty useful.</p><p>Has anyone used an Israeli queue before? Or have an actual code snippet or example you’d like to share? Let me know in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d37d32fa3d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-era-of-apis/israeli-queues-exploring-a-bizarre-data-structure-2d37d32fa3d9">Israeli Queues: Exploring a Bizarre Data Structure</a> was originally published in <a href="https://medium.com/the-era-of-apis">The Era of APIs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Over $500M invested in API companies in 2016, with 16 acquisitions]]></title>
            <link>https://medium.com/the-era-of-apis/over-500m-invested-in-api-companies-in-2016-with-16-acquisitions-cc4f3d2beef8?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc4f3d2beef8</guid>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[2016]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Thu, 29 Dec 2016 14:01:01 GMT</pubDate>
            <atom:updated>2017-05-16T22:06:27.084Z</atom:updated>
            <content:encoded><![CDATA[<p>Software has infiltrated and fundamentally changed every aspect of our lives. How software is being developed though, is changing. Developers are actually building software differently— relying more on APIs and microservices.</p><p>It’s no surprise then that 2016 has been a huge year for the API industry. We exported data from TechCrunch to see how huge. Over $500 million was invested in companies where the primary business model was an API, or an application programming interface.</p><blockquote>Over $500 million was invested in companies where the primary business model was an API, or an application programming interface.</blockquote><p>As you can see from this infographic, there’s been some big API headlines this year. Twilio filed its IPO priced at $15/share. Stripe raised a $150 million Round D at a $9 billion valuation. But overall, in 2016, we saw three important things happen in the API space:</p><ol><li>Multiple API-focused companies (Twilio, SendGrid and Stripe) crossed the $1 billion threshold, proving the API economy is here to stay.</li><li>Some bigger companies moved into using APIs for their software, showing APIs are reliable and scaleable.</li><li>A lot of tools and aggregators have been created around APIs, giving developers more access to them.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*mSaItg9aX8ZDtVyW." /></figure><h3>Enterprises move from monolithic software to microservices</h3><p>2016 was the year microservices really started growing. Introduced by Amazon and Netflix, microservices provide a new way for developers to create software. Rather than having one huge piece of code that does everything, enterprises are building multiple smaller microservices that each perform a small task. For example, a traditional app can be broken down into a user management microservice, a billing microservice, a file storage microservice, a notification microservice and many more.</p><p>This microservices approach introduces many benefits for software companies. Multiple, smaller pieces of code allows companies to have smaller teams manage different projects, and to reuse certain components (ex. user management) in multiple apps.</p><p>The rise of microservices across organizations lets us take the idea of reusability a step further. Some of these micro-services could exist in multiple companies. For example: most companies send emails, and many process credit card payments. Ergo, they could all use the same microservice.</p><p>This universal utility is the exact idea API companies are based on: provide one, basic functionality that many software developers can utilize in their apps. For the $9 billion Stripe, this piece of functionality was payment processing; for $2.2 billion Twilio, it was sending SMS and for &gt;$1 billion SendGrid it was email delivery. For this new wave of companies, the API is the way to do business.</p><p>As companies move to using microservices, the choice becomes to implement software yourself or use a third party API. In many cases, the quality of those third party services and their price point make this a clear choice. As developers become more expensive, companies opt-in to using these off-the-shelf APIs. <strong>The move to microservices fueled the rapid growth of the API economy in 2016.</strong></p><h3>Larger companies make APIs publicly available to developers</h3><p>APIs aren’t only the storefront of startups however. During 2016, the big cloud companies seemed to be joining the party as well. Just a month ago, Amazon introduced a host of new APIs during its Las Vegas Developer conference, Re:Invent. These new APIs let developers add smarter functionality into their apps.</p><p>Amazon isn’t the only one. This year, Google acquired API.ai (an artificial intelligince API) and Apigee (an API gateway), foraying into the API space. These acquisitions were closely followed by the launch of machine learning APIs to enable developers to sprinkle some Google wisdom into their apps.</p><p>Finally, IBM also made a big push into the API economy by promoting its’ set of machine learning, storage and communication APIs under the BlueMix and Watson platforms.</p><h3>2016 was only the beginning</h3><p>As more tooling and infrastructure is built around microservices and APIs, it’s clear that the software development paradigm is shifting. Rather than build everything internally, companies rely on third party APIs in their software to speed up their development process.</p><p>That being said, most of the &gt;$400B software industry still relies on monolithic applications. Now that there are bigger players showing APIs are the way to go — more of the industry is going to shift into using them. I believe that this shift will fuel rapid expansion in the API economy, which is going to soar through 2017.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc4f3d2beef8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-era-of-apis/over-500m-invested-in-api-companies-in-2016-with-16-acquisitions-cc4f3d2beef8">Over $500M invested in API companies in 2016, with 16 acquisitions</a> was originally published in <a href="https://medium.com/the-era-of-apis">The Era of APIs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Mark Zuckerberg Proved AI is All about APIs]]></title>
            <link>https://medium.com/the-era-of-apis/how-mark-zuckerberg-proved-ai-is-all-about-apis-7dbacf9e28e1?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dbacf9e28e1</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[comics]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Tue, 20 Dec 2016 15:24:11 GMT</pubDate>
            <atom:updated>2016-12-20T18:25:29.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Qt2htL9hyeGd0N94QPKntw.jpeg" /><figcaption>Image via <a href="http://www.thegeekocracy.com/cool-iphone-interface-marvels-iron-man-3-jarvis-ios-app/">Geekocracy</a> from JARVIS iOS app</figcaption></figure><p>This week, Mark Zuckerberg published the results of his 2016 project — building a real world Jarvis. This AI-based personal assistant gets commands from Zuck, and in turn, operates certain parts of his home. Here’s a <a href="https://www.facebook.com/zuck/videos/10103351034741311/">video</a> he posted (with a special voice actor) showing Jarvis’ functionalities.</p><p>In a <a href="https://www.facebook.com/notes/mark-zuckerberg/building-jarvis/10154361492931634">Facebook post</a>, Mark described how his modern butler works with the following chart:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*wiW5tUWrGIOItlCG." /></figure><p>One of the things I immediately noticed about this diagram is that Jarvis gains most of his power from connecting through APIs. As you probably know, an API is an applied programming interface that allows one piece of software to talk to another.</p><p>The fundamental idea of artificial intelligence is not new. A robot butler has been in the public consciousness since the Jetsons first hired Alice or Ironman was first assisted by Jarvis. What <em>is</em> new, however, is the sheer amount of data and actions available through APIs, and the quality of voice, image and text processing APIs out there. And those APIs are what makes Mark Zuckerberg’s project, and other artificial intelligence projects so powerful.</p><p>Most of Jarvis’ core functionalities are not from building original functionality from scratch, but from connecting to APIs. These three types of APIs are the real fuel for the future of artificial intelligence.</p><h3>1) User Interface APIs: Tell Jarvis a command</h3><p>User interfaces are different systems (Messenger, iOS Voice and Door Camera) that let Mark interface with Jarvis. First, Whenever Zuckerberg interacts with one of them (e.g. send a message to the Jarvis Messenger Bot or says a command using iOS Voice), the user interfaces tell Jarvis (through the API) to do something in the home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/295/1*pEvbxi058sWNaQMxIyoqOQ.png" /></figure><p>These user interface APIs are the way the user interacts with the AI and they connect to the AI (Jarvis) through an API.</p><h3>2) AI System APIs: Let Jarvis Interpret the Command</h3><p>AI system APIs help Jarvis make sense of the commands passed through the user interfaces. When Mark talks to Jarvis, he does so in a more human than computer-focused way. For example, he talks to the iOS Voice App to speak commands vs. typing them in an interface. He also talks to Jarvis using more broad and slang terms. In his post, he tells his new robo-butler to “shoot me a new gray t-shirt,” rather than something more computer friendly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/234/1*6YjsJ9IazLTvafNtw9ThpA.png" /></figure><p>Jarvis, however, needs to translate these more human requests into computer commands. “Shoot me a gray t-shirt” has to be understood by the AI and broken down into actions( ex. load t-shirt cannon, fire t-shirt cannon). This translation process occurs through AI services like Speech Recognition (which translates Mark’s speech to text) and Language Processing (which extract operations and intents out of the text).</p><p>These AI systems are the backbone of Jarvis, and are consumed through APIs. In the past year, we have seen many new AI companies systems grow and gather more attention. Facebook itself acquired Wit.ai, which falls under the Language Processing bucket (more precisely, it lets bots take human sentences and understand user intent). Similarily, Google acquired a Language Processing API (and Wit.ai competitor) called API.ai. Speech Recognition systems are also gaining popularity, with both <a href="https://cloud.google.com/speech/">Google </a>and <a href="https://www.microsoft.com/cognitive-services/en-us/speech-api">Microsoft</a> providing them to developers through public APIs.</p><h3>3) Home Systems/Data APIs: Enable Jarvis to Take Action</h3><p>So far, the user interfaces let Jarvis get commands and the AI systems let it interpret them. But, without more functionality, Jarvis cannot actually <em>do </em>anything with those commands. That’s where home systems and data APIs come in. Home systems allow developers to connect to smart home devices (like bulbs, locks and thermostats) through an API. Data APIs allow developers to connect and retrieve data from an outside program (ex. getting a song from Spotify).</p><p>Home systems and data APIs translate Mark’s commands into action. For example, here he is turning on and off the lights (thanks, <a href="https://www.fastcompany.com/3066478/mind-and-machine/mark-zuckerberg-jarvis">Fast Company</a>!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*FSpkmzaHfttV2LOiRavE2Q.gif" /></figure><p>When Mark wants to make it warmer, he can tell Jarvis to use the thermostat API to turn the heat up. When Mark wants to have an impromptu dance party with his daughter Max, Jarvis can connect to the Spotify API and play a song with a simple verbal command.</p><h3>AI is All about APIs</h3><p>In his post, Mark proved that the future of AI and AI-driven assistants is all about APIs. Interface APIs let them get commands from the users. AI APIs let Jarvis interpret those commands and understand what they mean. Home systems APIs let Jarvis actually take action.</p><p>It’s not just Jarvis that runs on APIs. In fact, any AI I can think of works that way.</p><p>Take Siri for example. Siri uses the iOS API to get a user’s voice commands. Siri then uses a (presumably proprietary) AI to convert that speech into text and the text into meaning. And lastly, Siri uses multiple APIs to return data to the user. For example, Siri may use…</p><ul><li>The IMDB API to return movie times and showings</li><li>The Wolfram Alpha API to solve mathematical questions</li><li>The Yahoo! API to share the results of last night’s game</li><li>The Maps API to give directions</li></ul><p>And many, many more…</p><p>In this example, Siri acts just like Jarvis. It uses three types of APIs to interface with, interpret and execute user commands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*h_iMmXN5ApgRXUPr." /></figure><p>More generally, we can model all AI into that system: user interfaces APIs &gt; AI APIs &gt; Home systems / data APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*IjebN_JbAHAfmxq9." /></figure><p>This model shows that <strong>AIs will only be as good as the APIs they use</strong>. The better the APIs and the more data and actions they let AI take — the better AIs will be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dbacf9e28e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-era-of-apis/how-mark-zuckerberg-proved-ai-is-all-about-apis-7dbacf9e28e1">How Mark Zuckerberg Proved AI is All about APIs</a> was originally published in <a href="https://medium.com/the-era-of-apis">The Era of APIs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connecting the World’s Software — Chapter 1]]></title>
            <link>https://medium.com/the-era-of-apis/connecting-the-worlds-software-chapter-1-f2be8a59843b?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2be8a59843b</guid>
            <category><![CDATA[a16z]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[funding]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[investment]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Mon, 21 Nov 2016 14:01:02 GMT</pubDate>
            <atom:updated>2016-12-14T23:15:18.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*BpxPmCSvCFxPDHygRPq_dg.png" /></figure><p>I am delighted to announce that we have recently finalized <a href="https://goo.gl/MkjIih">RapidAPI</a>’s first formal investment round, led by <a href="https://goo.gl/T1PEFe">Martin Casado</a> at Andreessen Horowitz, with participation from FundersClub, SV Angel and Green Bay Advisors. With the new capital we have raised, we will be able to help more developers find and connect to APIs to create new software experiences.</p><h3>We now live in a software world</h3><p>Software has fundamentally changed every aspect of our lives. We don’t drive — we take Uber. We don’t go the the store — we use Amazon or Instacart. Factories don’t log their inventories — they use an ERP driven by a connected set of sensors. The biggest innovations in recent memory were powered by software, and with most people and industries using hundreds of pieces of software every day, there is no turning back.</p><p>But while everything is in software and online, these different pieces of software are working separately, not together. The reality in this software-driven world is that software operates in silos in a disjointed manner. It’s nearly impossible to share data, and for apps to work in concert with one another. For example, my GPS app is connected to the web and knows when I’m on my way home, but it can’t tell my internet connected Nest thermostat to turn on the AC. A CRM can predict a company’s sales volume, but the ERP cannot automatically use it to order raw materials. The information already exists, and we feel there’s a tremendous opportunity to connect that information in a safe and valuable way.</p><p>It’s 2016, and it’s time software talks to each other.</p><p>Most of the software people use every day allows access through an API, letting developers connect to it. However, every API uses a different set of formats, standards and protocols — essentially a different language. ‘Translating’ these languages is rough, and for a developer connecting to 100s of APIs, it an be an impossible mess to navigate. Moreover, this problem becomes even greater as more APIs are created and new formats are introduced. This is terribly inefficient and disjointed, and it means developers spend more time on ‘translation’ and less on developing. We can do better.</p><h3>Enter RapidAPI</h3><p>Initially, we launched RapidAPI as an open source project — a collection of API wrappers giving developers unified API access. Over time, we’ve seen over thousands developers use the platform to discover and connect software in new ways. We’ve witnessed true inter-app connectivity that has yielded amazing new experiences for people. Gone are the days of fragmentation developers — welcome to the<strong> </strong>Era of the API!</p><p>Since releasing RapidAPI in private beta, we have seen tremendous adoption. Over 25,000 developers have used RapidAPI to explore and connect with over 200 APIs. We have even seen interest from enterprise companies like eBay where developers understood the powerful potential of internal APIs and brought them in-house. We’re excited to now make the RapidAPI platform public and make APIs accessible to any developer in the world.</p><h3>Partnering with Andreessen Horowitz to Fund Our Next Step</h3><p>As developers ourselves, we realized the pain of the API location and connection process and the enormous opportunity that can exist if we help to solve it. In setting up RapidAPI, we knew we had to do two things out of the gate:</p><ul><li>Create a platform that connects to as many APIs as possible.</li><li>Get this platform in the hands of developers as quickly as possible.</li></ul><p>In building a platform for the future, it was important that we think about the right team to make this vision a reality. We were fortunate enough to meet with Martin Casado and Ben Horowitz at Andreessen Horowitz, and instantly knew that we’d found the perfect partner — one who shared our passion for software and could help us accelerate our growth plans.</p><h3>What’s Next?</h3><p>It’s time for software to start talking to each other, and with this newly raised capital, we plan to keep working on our mission: to help developers find and connect to more APIs, quickly and easily. We have expanded the product team so that it’s now faster than ever to find and test those APIs. And now, we are doing everything we can to help developers unleash the potential of APIs.</p><p>As we move forward and grow the company, RapidAPI will continue to be free and open source, with no strings attached. It’s important that we continue to help developers use technology in new and valuable ways, and to make the process as smooth and seamless as possible.</p><p>By connecting the different dots between the millions of applications that are already out there, developers can add exponential value on top of preexisting data and functionality. I’m incredibly excited about living in this interconnected world, and we’ll keep providing developers with the tools to get us there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2be8a59843b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-era-of-apis/connecting-the-worlds-software-chapter-1-f2be8a59843b">Connecting the World’s Software — Chapter 1</a> was originally published in <a href="https://medium.com/the-era-of-apis">The Era of APIs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Sundays: Why I Do Sunday Projects]]></title>
            <link>https://medium.com/@iddo.gino/coding-sundays-why-i-do-sunday-projects-12c0c468aa9?source=rss-f7bffa07e84b------2</link>
            <guid isPermaLink="false">https://medium.com/p/12c0c468aa9</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Iddo Gino]]></dc:creator>
            <pubDate>Fri, 04 Nov 2016 14:44:10 GMT</pubDate>
            <atom:updated>2016-12-14T23:10:34.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eRRIqLmAsOMlxhj4htC9YA.jpeg" /></figure><p>Every Sunday, I take a few hours to sit down and code for fun. Sunday projects were originally an informal excuse to experiment with new products. However, they’ve turned into a surprisingly valuable and semi-regular ritual for me.</p><p>My only rules for selecting Sunday projects are as follows:</p><ol><li>They have to be technical and involve writing code.</li><li>They should be completely new and sandboxed, unrelated to what we build at RapidAPI.</li><li>They have to incorporate technologies that I haven’t used yet.</li></ol><p>The act of writing code for the sake of writing code may seem overly ambitious or a waste of time. But I’ve actually found it to be quite helpful in my role as a CEO, especially when the company in question is a developer platform.</p><p>Here’s how Sunday Projects have helped me and why I’m going to keep doing them for the time being.</p><h3>Benefit 1: Build a better platform for developers</h3><p>At RapidAPI, we’ve created a platform that helps developers find and connect to APIs. Ultimately, we’re a company of developers building for developers.</p><p>Having a team that inherently gets developers helps us build a more valuable platform. For example, our team in Israel is creating a marketplace that is easy for developers to navigate. The team in the Ukraine builds API packages with blocks in multiple programming languages so developers can easily incorporate APIs into their projects.</p><p>Going from being the only developer to working with a team of developers has been incredible. But, as my role has shifted away from building a platform to building a company, actively maintaining a developer mindset is even more crucial.</p><p>My role today is completely different than it was ten months ago. When we were first building the product, I <em>was</em> primarily a developer. Sure, I talked with investors, but I spent most of my time coding, shipping features and building a great product.</p><p>My role now requires me to wear hats that I never thought that I’d wear before. It’s exhilarating. I love it. But the more time I spend growing the team, meeting with investors, planning business strategies, the less time I spend coding.</p><p>It’s easier to build a developer solution when you are a developer. Taking the time to code every Sunday means that my developer hat always stays on the rack, no matter what my current role at the company is. As long as I keep that developer mindset, I can make sure we’re building something valuable for developers.</p><p>And you know what? It’s worked. My Sunday projects are often a lot like what developers spend time hacking on their own. This commonality helps me connect with developers in a real, tangible way. For example, one weekend, I built a side project around Amazon Alexa. The very next weekend, we helped developers build similar projects using Alexa and RapidAPI right away. Since the questions that developers asked were already familiar, the conversations flowed seamlessly. After realizing this content was helpful, I wrote a <a href="http://blog.rapidapi.com/2016/10/07/4/">blog post</a> for other developers that addressed some of the most common questions.</p><h3>Benefit 2: Better work with developers</h3><p>Sunday projects don’t just come in handy for understanding the developers using RapidAPI. Regularly expanding my coding horizons has also helped with our internal development team. Experimenting with these new technologies has helped me…</p><ul><li>Better understand our engineering challenges.</li><li>Better communicate and work with our development team.</li><li>Better dedicate resources to product features that meets developers’ needs.</li></ul><p>It’s not just theoretical either. For example, RapidAPI recently switched its front-end from Angular to React. During the transition, I decided that my Sunday project would be to build a quick React + Redux app. By building a project with React in advance, I understood timelines and potential roadblocks more clearly.</p><p>Not too bad for a few hours of coding on a Sunday!</p><h3>Benefit 3: Keep up with industry trends</h3><p>I’m lucky enough to work in a field that is constantly changing and improving. Faster than pretty much any industry. This pace is one of the reasons I first fell in love with technology. It makes my field interesting and the work we do at RapidAPI exciting.</p><p>But keeping up with this rate of change is a challenge.</p><p>When I was fundraising for RapidAPI, I took a break from coding to focus on pitching. After I came back to GitHub, I wasn’t familiar with most of the biggest projects there. It had only been <em>three months.</em></p><p>Because new developments and open-source projects come out quickly, developers always have new options. Industry standards change at the drop of a dime.</p><p>Need proof? Just look at <a href="https://github.com/blog/2047-language-trends-on-github">GitHub’s language trends</a> over the past four years…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*10-Ygp9FSNNI-qNi." /></figure><p>…or run any search on <a href="http://sotagtrends.com/">Stack Overflow tag trends</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/0*k47-Z27zuQKV9HJk." /></figure><p>Developer preferences change quickly. In order to understand their preferences, you’ve got to keep up. The best way way to keep up? Get your hands dirty and code.</p><p>Reading about new developments is fine, but I’m a firm believer in learning by <a href="http://www.huffingtonpost.com/jeff-degraff/sodoto-see-one-do-one-teach-one_b_4372803.html">SODOTO</a> (see one, do one, teach one). If I see a new technology out there that developers are adopting, I want to understand it. That’s why I dedicate a window every Sunday to explore actively by doing, not just reading.</p><h3>Conclusions</h3><p>For me, the Sunday project timeslot help me on two levels. One, I avoid overly distracting myself any time a new headline comes out. I don’t feel as pressured to switch gears immediately. I know that I will have a weekly slot dedicated to explore. Two, Sunday projects keep me accountable to actually learning this technology. I don’t have to decide where exploring a new skill falls on my priority list; I just play with it on Sunday. No more feeling guilty about not doing more to keep up with developer preferences.</p><p>So, that’s why I’ve been hanging out on GitHub every Sunday. What about you guys? Does anyone else do projects on the side to stay sharp? And, more importantly, does anyone have any cool project ideas for this Sunday?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12c0c468aa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>