<?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 Rodrigo M.S. on Medium]]></title>
        <description><![CDATA[Stories by Rodrigo M.S. on Medium]]></description>
        <link>https://medium.com/@r0dms?source=rss-e971f946d084------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cTUGliNzinS9eeNCljlhpQ.png</url>
            <title>Stories by Rodrigo M.S. on Medium</title>
            <link>https://medium.com/@r0dms?source=rss-e971f946d084------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:50:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@r0dms/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[Quine has evolved into Quira]]></title>
            <link>https://medium.com/quira/quine-has-evolved-into-quira-4dfc85c05b9e?source=rss-e971f946d084------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dfc85c05b9e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[rebranding]]></category>
            <dc:creator><![CDATA[Rodrigo M.S.]]></dc:creator>
            <pubDate>Thu, 27 Jun 2024 13:55:53 GMT</pubDate>
            <atom:updated>2024-06-27T23:06:55.491Z</atom:updated>
            <content:encoded><![CDATA[<h3>Quine has evolved into Quira 🦍🚶</h3><p>Today marks a significant milestone in our journey — we are thrilled to announce that Quine has evolved into <strong>Quira </strong>(/ˈkiːrə/ or “KEEH-rah”)<strong><em>. </em></strong>The timing for this change couldn’t be more significant. Over the last few months, our company has undergone deep and significant changes in our team, product, and strategy. These developments have led us to adopt a new identity that mirrors these transformations. This week not only marks a key chapter in our history, but also reinforces our dedication to changing the way developers monetize their skills, time, and reputation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F969096585%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F969096585&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1882391003-86687b55f6ef04e749dab513694bcf10c6f61bd867deb65085ea2fccc91435da-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/73dd66e5cf4dbe27bc64b0325d77f8fa/href">https://medium.com/media/73dd66e5cf4dbe27bc64b0325d77f8fa/href</a></iframe><h3>Reaffirming our commitment</h3><p>Our core mission remains the same: to help developers make as much money as possible form their work, time, and reputation. Echoing Stripe’s vision, we aim to <em>maximise the GDP of software creators</em>. Our approach to do this is and will continue to be heavily data-driven and centred around the concept of <em>experience quantification</em>.</p><p>To reaffirm our present commitment, it’s essential to recall our origins. Our journey began years ago when we first took on the challenge of measuring developer experience from open source contributions. Little did we know, this endeavour would lead us down a rabbit hole into some unexplored territory. It turns out that quantifying experience from code is intricately linked with a number of other exciting problems, such as evaluating the significance of open-source contributions, assessing the reputation of developers, matching developers to tasks, classifying code content, among others. Even though all of these problems are interrelated, each of them represents unique challenges in terms of data, computation, and modelling. Over the past few years, we’ve focused on modelling these problems in a rigorous way. Our efforts have now come together in our <strong><em>Quests</em></strong> products, which use these models to efficiently deploy financial and reputational bounties for the beneift of our partners and our userbase.</p><p>Through Quests, we have introduced two novel incentive mechanisms tailored for the open-source community. On the one hand, <strong><em>Creator Quests</em></strong>, reminiscent of a decentralised hackathon that operates 24/7, incentivises the creation of open-source content that drives user acquisition for dev-tools and OSS organisations. On the other hand, <strong><em>Solver Quests</em></strong> enables organisations to price issues in open-source projects to accelerate the speed of delivery or build community. Our Quests products are the cornerstone of achieving our mission, and we will continue to invest heavily in them.</p><h3>Looking ahead</h3><p>Exciting things are coming for Quira. We don’t want to throw all the spoilers just yet, but we’re working tirelessly to elevate <em>Quests</em> to entirely new levels. In the upcoming quarters, we will embrace AI, open source, and mechanism design like never before. Most importantly, we will return to our roots and tackle this next wave of challenges with curiosity, rigour, and a relentless dedication to creating value for developers and organisations.</p><p>Thank you for your support and for joining us on this journey.</p><p>— Rodrigo &amp; Team Quira 🙇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dMAAOEht_DdvEKQMmZQWWA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dfc85c05b9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quira/quine-has-evolved-into-quira-4dfc85c05b9e">Quine has evolved into Quira</a> was originally published in <a href="https://medium.com/quira">Quira</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The tragedy of commons in open source]]></title>
            <link>https://medium.com/quira/the-tragedy-of-commons-in-open-source-55a76ceb799c?source=rss-e971f946d084------2</link>
            <guid isPermaLink="false">https://medium.com/p/55a76ceb799c</guid>
            <category><![CDATA[bounties]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[digital-public-goods]]></category>
            <category><![CDATA[linux-foundation]]></category>
            <dc:creator><![CDATA[Rodrigo M.S.]]></dc:creator>
            <pubDate>Thu, 21 Mar 2024 14:45:01 GMT</pubDate>
            <atom:updated>2024-06-24T04:15:19.034Z</atom:updated>
            <content:encoded><![CDATA[<h3>The tragedy of commons in OSS 🎭</h3><p><em>A data essay exploring symptoms, remedies, and opportunities</em></p><p>Recently GitHub released <a href="https://forgoodfirstissue.github.com/">For Good First Issue</a>, a special index that tracks <a href="https://digitalpublicgoods.net/digital-public-goods/">Digital Public Goods (DPGs)</a> repos. This includes open-source software, open data, open AI system, or open content collection that supports the <a href="https://sdgs.un.org/goals">United Nations sustainable Development Goals (SDGs)</a>. Currently, the official registry counts ~132 projects which includes a variety of social and impact-focused projects like a <a href="https://github.com/simpledotorg/simple-server">webapp to track hypertensive patients across a population</a>, an <a href="https://github.com/consuldemocracy/consuldemocracy">app for citizen participation and open government</a>, and <a href="https://github.com/primeroIMS/primero">software to help social workers manage data on vulnerable children</a>.</p><p><em>For Good First Issue</em> addresses a significant need in the open-source ecosystem: directing dedicated and socially conscious talent to projects that positively impact society and would otherwise struggle to attract contributors. Initiatives like this one can help raise the collective consciousness of contributors and ameliorate the negative externalities that arise from the <em>tragedy of the commons.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*dgfwLwLKskBNZJIcmTC3-g.png" /></figure><h3>The tragedy of the commons</h3><p>In economics, the <em>tragedy of the commons</em> refers to the situation in which individuals with access to a public resource act in their own interest and, in doing so, ultimately deplete the resource. Though this concept is traditionally associated with shared environmental resources, it can also extend to the domain of open source software. While resources can’t be depleted in the context of software, they can be regarded as <em>abused</em> when users do not donate time, work, or resources to the communities they take from. In these situations one can observe a number of negative consequences like slow development, weakened community support, or even legal and licensing risks. The famous <em>monetisation</em> and <em>maintainer</em> problems in open source are nothing less than a manifestation of this economic pathology.</p><p>A number of initiatives have tried to ameliorate the tragedy, but no definite solution exists yet. In light of GitHub’s recent initiative it is important to understand in what ways the <em>tragedy of the commons</em> manifests in open source, and whether curated contributor indices like DPGs can help break it. In particular, we investigate whether initiatives like DPG projects present a real opportunity to current or aspiring open source contributors.</p><p>To do this, we compare the set of DPG projects on GitHub against three other sets of open source repos,</p><ol><li>2,395 projects from the <a href="https://github.com/orgs/apache/repositories?type=all">Apache foundation</a>,</li><li>8,129 projects under the <a href="https://www.linuxfoundation.org/projects">Linux Foundation</a> umbrella,</li><li>6,805 projects maintained by <a href="https://redhatofficial.github.io/#!/main">RedHat</a>.</li><li>1,255 repos belonging to Digital Public Goods,</li></ol><p>To perform this comparison we derive traction and engagement metrics using publicly available GitHub data. Specifically, we look at three fundamental metrics: <em>issue backlog</em>, <em>contributor retention</em>, and <em>maintainer responsiveness</em>. These metrics will help us understand the overall health of each group of projects, as measured by the activity metrics that most strongly correlate either with the resources available to a project or with the community’s support to the project. This will help us understand whether DPGs are particularly affected by the tragedy of the commons and the type of developer experience (DX) that new contributors can expect.</p><h4>#1: DPGs have (on average) less contributors per issue than other groups</h4><p>An important indicator of the “tragedy of the commons” in open source is the size of the of the issue backlog a project has. In other words, the number of unresolved open issues in the repository. Although not every open issue represents critical technical debt, an imbalance between issue creations and number of merged PRs suggests a lack of resources to manage them effectively. Public data shows that DPGs have the highest concentration of open issues per repository, but also the fewest number of contributors per issue. While this indicates a scarcity of contributor resources, the relative high number of open issues also suggests an opportunity for contributors who want to make a significant impact by applying their software skills to for-good projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xQoIQ3cK90Gm1qHlUaw56Q.png" /></figure><h4>#2: DPGs have less long-term contributor retention than RedHat &amp; Apache</h4><p>Contributor retention is important to keep a project’s issue backlog under control. To better understand contributor engagement we compute “<em>On or After Contributor Retention</em>” which we define as the percentage of contributors who merge a Pull Request (PR) at a specific time or any time thereafter after the first contribution.</p><p>Interestingly, DPGs show the highest “<em>On or After Contributor Retention</em>” contributor within a three month period. However, this engagement drops significantly after month 3 and stays below the retention shown by Apache’s and RedHat’s projects. It’s worth noting that DPGs have the hightest short-term retention, but that six months after the first contribution 60% of them don’t contribute again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1miIrCWJJD1ncXBNHxEeFw.png" /></figure><h4>#3: DPG maintainers are as responsive as maintainers from RedHat and the Linux Foundation.</h4><p>Another strong indicator of resource scarcity in a project is the waiting time a contributor experiences after submitting a PR, specifically, the average time they wait to see their PR merged into the codebase. If a maintainer has more bandwidth, they can review and give feedback more quickly, thus decreasing the average merge time. Notably, public data shows that DPG repositories exhibit a level of maintainer responsiveness comparable to that of RedHat and the Linux Foundation and superior to that of the Apache Foundation. This indicates that the level of Developer Experience (DX) when contributing to these repos is comparable to that of more established and popular projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*51IJRx3Ki-hWKcXAxg7ufA.png" /></figure><h3>Breaking the tragedy of the commons</h3><p>Let’s get contributing! Our analysis shows that DPG repos are rich in open issues and that in some respects (like maintainer responsiveness) one can expect a similar level of DX than repos under the RedHat or the Linux Foundation patronage. As the number of DPG projects grow, it’s important for aspiring contributors to use an index to browse for the most relevant communities. Considering that open source is the most secure model for developing AI systems for the public, we anticipate a significant growth in DPGs indices over the next few years.</p><p>GitHub’s <a href="https://forgoodfirstissue.github.com/">For Good First Issue</a> maintains a special index of “For Good” repos, while platforms like <a href="http://quine.sh/">Quira</a> index repos across the ecosystem and helps you discover and filter issues that align to your language and topic preferences. In fact, we just released a new interface that allows you to not only select DPG repos, but also repos in other categories mentioned in this essay like the Linux Foundation. Try it out 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NcLuTS_CYLXM4d1xCBGefQ.gif" /></figure><p>However, to fully break the tragedy of the commons it’s also important to make sure that projects are well funded and that part of those funds are distributed equally to core maintainers and casual contributors. Funding a project is now straightforward thanks to products like <a href="https://github.com/sponsors">GitHub Sponsors</a>, <a href="https://www.buymeacoffee.com/">BuyMeACoffee</a> and <a href="https://www.patreon.com/en-GB">Patreon</a>. However, distributing funds to casual contributors is less common, but platforms like <a href="https://quira.sh/">Quira</a> are launching ML-powered products that enable organisations to <strong><em>pay their contributors</em></strong> when they merge meaningul and valuable PRs. This can help organisations retain contributors and encourage them to return to contribute in situations where the opportunity cost of contributing is high for the developer.</p><p>Do you have an open source project and would like to create a reward scheme for your contributors? <a href="https://quine.sh/organisations">Get in touch!</a>📱</p><p><em>Thanks to </em><a href="https://medium.com/u/b6e118d45e45"><em>Alex Bird</em></a><em> for his help in preparing this essay and to </em><a href="https://medium.com/u/b2a26efa181b"><em>Kasiasun</em></a><em> for her feedback and comments — Artwork from </em><a href="https://www.asciiart.eu/"><em>asciiart.eu</em></a><em> — </em>Written with ❤️ by <a href="https://quira.sh/"><strong>Quira</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55a76ceb799c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quira/the-tragedy-of-commons-in-open-source-55a76ceb799c">The tragedy of commons in open source</a> was originally published in <a href="https://medium.com/quira">Quira</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer reputation in the era of LLMs]]></title>
            <link>https://medium.com/quira/developer-reputation-in-the-era-of-llms-0dd4689bb8f3?source=rss-e971f946d084------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dd4689bb8f3</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Rodrigo M.S.]]></dc:creator>
            <pubDate>Tue, 05 Mar 2024 15:25:22 GMT</pubDate>
            <atom:updated>2024-06-24T04:16:54.922Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Part I</em></strong><em>: The era of infinite code content </em>📺</p><p>Nearly a year has passed since the introduction of GPT-4. One of the public discussions we followed at the time was the one concerned with the impact LLMs would have on software development and, in particular, on jobs in this field. ChatGPT felt like magic and it was easy to extrapolate the impact of these technologies, even to the extent of rendering the software engineering profession redundant. One year later, it’s clear that LLMs are not replacing developers, but helping them focus less on the grunt work and more on the big picture.</p><p>This transition has already had a measurable impact on unit economics. For example, last year, Microsoft <a href="https://www.microsoft.com/en-us/Investor/events/FY-2023/Morgan-Stanley-TMT-Conference">reported</a> that developers using GitHub Copilot are 55% more productive than those not using it. Interestingly, they also noted that 40% of the code checked in by these developers was AI-generated and remained unmodified. Statistics like these suggest a new inflection point in the software economy and an impending shift in our path towards the future of work. Specifically, they prompt us to question, <em>in an era where code is automatically generated, how do we measure the quality of software talent?</em></p><h3>Computational talent validation</h3><p>Talent validation inherently depends on social consensus. For developers, this consensus can be reached through various means like earning a diploma, interviewing for a job, or achieving a high score in LeetCode quizzes. However, with the accelerated production of software talent that LLMs have catalysed, it’s uncertain whether these traditional consensus-building methods can truly scale or remain relevant.</p><p>At Quira, we believe that in the era of Generative AI, scalable consensus can only be achieved through <em>experience quantification</em>. Under this approach, a developer’s skills and abilities are implicitly inferred through <strong><em>data</em></strong> and <strong><em>computation</em></strong>. Specifically, by semantically understanding the code and contribution metadata that developers generate when creating software. The evolving dynamics of open source are accelerating this potential and accentuating the need for this technology. Indeed, we are observing a shift in attitude towards open source, where a new generation of eager and ambitious developers are embracing it not only to uphold its ethos of community-driven development, but also as a means to validate their work socially.</p><p>However, even in this new dynamic, the same problems persist. When code can be automatically generated from natural language, analysis of code content alone is insufficient to achieve robust consensus. To automatically quantify experience, one must incorporate additional context regarding the relevance and merit of the software created. In other words, we need to understand the <em>social proof</em> of code and how it has been “validated” by other members in the network.</p><h3><strong>Measuring the <em>social </em>proof of OSS contributions</strong></h3><p>Today we’re excited to release a new version of <a href="https://docs.quine.sh/for-developers/devrank">DevRank</a>, a metric that measures the social proof of open source contributions by quantifying <em>reputation flows</em> in the GitHub network. In a nutshell, DevRank models the ecosystem as a network of contributors and repositories linked together by a directed edge representing a reputation-inducing event on GitHub. The current version considers three types of edges.</p><ol><li><strong>Developer → Repo</strong>, to represent events where a developer stars a repo.</li><li><strong>Repo → Developer</strong>, for events where a developer commits to a repository.</li><li><strong>Repo → Repo,</strong> to incorporate events where a repository imports a package or a dependency.</li></ol><p>Considering all such edges within GitHub, we can construct a large directed network where <em>reputation</em> flows from one node into another through <em>stargazer</em>, <em>commit</em>, and <em>import</em> events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9NozKruPtwtg7qNkS3lF8Q.png" /><figcaption><em>An example of a reputation network in open source</em></figcaption></figure><p>By applying a customised version of the <a href="https://en.wikipedia.org/wiki/PageRank">PageRank algorithm</a> on this resulting graph we can compute the stationary state probabilities of a random walker in the network. These raw probabilities indicate the importance of a developer within the open source ecosystem in the same way that PageRank calculates the importance of a webpage on the internet. The higher the DevRank of a developer, the more their contributions have been socially validated by other developers through <em>star</em>, <em>commit</em>, and <em>import</em> events on GitHub. If you’re interested in the technical details of DevRank, you can read more about it <a href="https://docs.quine.sh/for-developers/devrank/the-pagerank-component">in our documentation</a>.</p><h3>Rethinking open source status</h3><p>One of the coolest applications of DevRank is that it gives us a new framework to think about <em>status</em> &amp; <em>reputation</em> in open source, not only for individual developers, but also for communities. Developer reputation is already a valuable intangible that can have a positive financial impact on the lives of developers, say, by giving them access to work opportunities or, in some cases, making them eligible for grants or venture capital funding. For these reasons, quantifying reputation in a principled and transparent way is critical to foster a meritocratic ecosystem. Think, for example, of stargazer traction, which is widely used as a measure of the success of a project in the ecosystem and that, <a href="https://www.wired.com/story/github-stars-black-market-coders-cheat/">according to Wired</a>, is now being artificially inflated and is no longer a reliable indication of traction.</p><p>Let’s look at how DevRank can change our perspective of success and status in open source.</p><h4><strong>Stargazers</strong></h4><p>Let’s start with stargazers, which are by far the most popular way to assess traction in open source. To do this, let’s first ask ourselves,</p><p><em>How would the list of most popular repos on GitHub change if instead of ranking them by number of stars, we ranked them by the DevRank of their stargazers?</em></p><p>It turns out that this adjustment would significantly alter the rankings. Certain repositories, such as <a href="https://github.com/FreeCodeCamp/freecodecamp">FreeCodeCamp/freecodecamp</a>, <a href="https://github.com/public-apis/public-apis">public-apis/public-apis</a>, or <a href="https://github.com/jwasham/coding-interview-university">jwasham/coding-interview-university</a> would not only lose their place in the top 5 of the list… they wouldn’t even feature in the top 30! On the other hand, some repositories like <a href="https://github.com/facebook/react">facebook/react</a>, <a href="https://github.com/twbs/bootstrap">twbs/bootstrap</a>, or <a href="https://github.com/electron/electron">electron/electron</a> would rise from the 10th, the 20th, and 30th, to the 1st, 3rd, and 4th place in the list. In other words, the list of top 10 repos would see a demotion of educational repos in favour of some popular development frameworks.</p><pre> <strong><em>#</em></strong> |           <strong><em>Most starred repos</em></strong>            | <strong><em>Repos with highest DevRank</em></strong> <br>--------------------------------------------------------------------------<br> 1 |  FreeCodeCamp/freecodecamp              |  facebook/react<br> 2 |  EbookFoundation/free-programming-books |  resume/resume.github.com<br> 3 |  sindresorhus/awesome                   |  twbs/bootstrap<br> 4 |  public-apis/public-apis                |  electron/electron<br> 5 |  jwasham/coding-interview-university    |  nodejs/node</pre><p>But we don’t need to stop there… We can go one level further and look at the repos that have been starred the most by developers in the top and bottom 10% (see table below). The results are qualitatively more pronounced and show that the <em>top 10%</em> tends to star repos focused on developer tooling, while the <em>bottom 10%</em> tends to star beginner resources and educational projects.</p><pre>  <strong><em>#</em></strong> |      <strong><em>Top 10%</em></strong>          |           <strong><em>Bottom 10%</em></strong>                         <br> -------------------------------------------------------------------------<br> 1  |  nektos/act           |  EbookFoundation/free-programming-books<br> 2  |  oven-sh/bun          |  kamranahmedse/developer-roadmap<br> 3  |  tauri-apps/tauri     |  practical-tutorials/project-based-learning<br> 4  |  trpc/trpc            |  public-apis/public-apis<br> 5  |  typst/typst          |  jwasham/coding-interview-university<br> 6  |  evanw/esbuild        |  codecrafters-io/build-your-own-x<br> 7  |  denoland/deno        |  FreeCodeCamp/freecodecamp<br> 8  |  zed-industries/zed   |  Snailclimb/JavaGuide<br> 9  |  colinhacks/zod       |  CyC2018/CS-Notes<br> 10 |  astral-sh/ruff       |  996icu/996.ICU</pre><h4><strong><em>Contributor growth</em></strong></h4><p>Another popular way to assess traction in open-source communities is contributor growth. Contributor growth is already a purer metric than GitHub stars because an increase in the contributor growth counter requires the submission and acceptance of a PR. However, similarly to stargazers, this metric is not resistant to noise. For example, some “first contribution repos” like <a href="https://github.com/firstcontributions/first-contributions">firstcontributions/first-contributions</a> trivialise merging requirements for PRs, making contribution events almost as frictionless as stargazing.</p><p>DevRank can help us filter out the noise and add context to these metrics. To illustrate this, consider the top repositories in the ecosystem ranked by the number of new contributors since <em>January 2023</em>. We can see that in the top 20 of the list, there are projects like <a href="https://github.com/firstcontributions/first-contributions">firstcontributions/first-contributions</a>, <a href="https://github.com/mouredev/retos-programacion-2023">mouredev/retos-programacion-2023</a>, <a href="https://github.com/Syknapse/Contribute-To-This-Project">Syknapse/Contribute-To-This-Project</a>, which have very low merging requirements.</p><pre><strong><em>#</em></strong>                               <strong><em>Repository</em></strong>       <strong><em>All contributors</em></strong><br>------------------------------------------------------------------<br>1   firstcontributions/first-contributions                  14706<br>2                        is-a-dev/register                   2505<br>3                   langchain-ai/langchain                   2127<br>4                 MicrosoftDocs/azure-docs                   1757<br>5                EddieHubCommunity/BioDrop                   1635<br>6                       mouredev/hello-git                   1503<br>7                            NixOS/nixpkgs                   1491<br>8                              mdn/content                   1177<br>9         mouredev/retos-programacion-2023                   1144<br>10         DefinitelyTyped/DefinitelyTyped                   1117<br>11                          torvalds/linux                   1105<br>12                   microsoft/winget-pkgs                    937<br>13     Syknapse/Contribute-To-This-Project                    892<br>14                       llvm/llvm-project                    826<br>15                      raycast/extensions                    745<br>16                             unifyai/ivy                    744<br>17                huggingface/transformers                    721<br>18    ordinals-wallet/ordinals-collections                    720<br>19                       uiverse-io/galaxy                    718<br>20                  mdn/translated-content                    698</pre><p>We can derive an alternative ranking if we restrict the counts to contributions by developers in the <em>Top 1% </em>of developers based on DevRank (table below). When doing this, we immediately see that 30% of places in the top 20 are replaced by top AI projects and developer tools like <a href="https://github.com/ggerganov/llama.cpp">ggerganov/llama.cpp</a>, <a href="https://github.com/run-llama/llama_index">run-llama/llama_index</a>, <a href="https://github.com/langchain-ai/langchainjs">langchain-ai/langchainjs</a>.</p><pre><strong><em>#                         Repository      Top 1% contributors</em></strong><br>-------------------------------------------------------------<br>1            langchain-ai/langchain                      312<br>2                     NixOS/nixpkgs                      190<br>3            Homebrew/homebrew-core                      157<br>4               ggerganov/llama.cpp                      143<br>5             microsoft/winget-pkgs                      135<br>6                       mdn/content                      133<br>7                    rust-lang/rust                      130<br>8          huggingface/transformers                      127<br>9   DefinitelyTyped/DefinitelyTyped                      127<br>10                   vercel/next.js                      122<br>11            run-llama/llama_index                      116<br>12                   astral-sh/ruff                      107<br>13            huggingface/diffusers                      104<br>14                      oven-sh/bun                      103<br>15         langchain-ai/langchainjs                      102<br>16                      github/docs                       96<br>17                llvm/llvm-project                       93<br>18          schemastore/schemastore                       90<br>19               raycast/extensions                       87<br>20                   cncf/landscape                       80</pre><h4>Grudge matches</h4><p>DevRank can also aid in determining a winner in classic rivalries between developer communities. For example, a frequently debated topic among AI researchers is whether <a href="https://github.com/pytorch/pytorch">PyTorch</a> is better than <a href="https://github.com/tensorflow/tensorflow">Tensorflow</a>. There are many non-violent ways to settle this matter, with our preferred option being to appeal to open-source data. Unfortunately, in this particular case, vanilla statistics provide limited insight and fail to give a definite conclusion: TensorFlow leads in the stargazer count with <strong>180.8k</strong> stars, but PyTorch is imported by <strong>265.9k</strong> repositories. To gain true insight into this question we need to increase the resolution of the data.</p><pre>         <strong><em>Repository</em></strong>       |  <strong><em>Stars</em></strong>   |  <strong><em>Dependent repos</em></strong><br> ------------------------------------------------------<br> tensorflow/tensorflow    |  <strong>180.8k</strong>  |   225.1k<br> pytorch/pytorch          |  75.6k   |   <strong>265.9k</strong></pre><p>For example, we can use DevRank to understand which repo is preferred by developers with higher reputation. To do this, we can compute the median DevRank of the contributors of each dependent repository. The results are fascinating. The median DevRank of PyTorch users turns out to be <strong>140.3</strong>, whereas for TensorFlow users, it stands at <strong>56.9</strong>. Moreover, the total DevRank sum of repos that use PyTorch is <strong>2.65 bn</strong>, while the DevRank sum of repos that import Tensorflow is <strong>1.75 bn</strong>.</p><p>This experiment shows that even though PyTorch has significantly fewer stargazers than Tensorflow, it is generally used and preferred by repositories and developers with higher DevRank. Go PyTorch! 🔥</p><pre>         <strong><em>Repository</em></strong>     |  <strong><em>Median DevRank of dependent repo contributors<br></em></strong> -----------------------------------------------------------------------<br> tensorflow/tensorflow  |                    56.9<br> pytorch/pytorch        |                    <strong>140.3</strong></pre><h3>Outro</h3><p>The future of developer work and education is evolving quickly and LLMs playing a significant role in accelerating this transformation. As the software engineering profession becomes democratised, the need to assess the quality of software talent in a scalable and systematic way becomes paramount. At Quira, we are leveraging DevRank along with other signals to algorithmically gauge the expertise of our users. This allows us to rank developers in our community across languages, frameworks, topics, and industries to ultimately match them to paid contribution opportunities in open source. Our technology is already helping a number of <a href="https://www.ycombinator.com/rfs#commercial-open-source-companies"><em>Commercial Open Source Organisations (COSS)</em></a> receive PRs from top contributors outside of their orbits. If you’d like to use Quira to build a dynamic and sustainable community of high-quality contributors, <a href="https://docs.quira.sh/get-in-touch/contact-us">drop us a line</a>, we’d love to chat.</p><p>Alternatively, if you’re a developer looking to build or monetise your reputation in open-source, then log in to <a href="https://quira.sh/">Quira</a> and start your journey with us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dd4689bb8f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quira/developer-reputation-in-the-era-of-llms-0dd4689bb8f3">Developer reputation in the era of LLMs</a> was originally published in <a href="https://medium.com/quira">Quira</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quine and the OSS creator economy]]></title>
            <link>https://medium.com/@r0dms/quine-and-the-oss-creator-economy-8d450d2e0f6?source=rss-e971f946d084------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d450d2e0f6</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[creator-economy]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Rodrigo M.S.]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 18:36:02 GMT</pubDate>
            <atom:updated>2022-03-10T22:20:02.372Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A renaissance in social media hits the open source network</em> 🖼</p><p>It’s a great time to be a <em>creator</em>… at least on social media. After years of bootstrapping social capital and profiting from user-generated content, platforms like Twitter, YouTube, and Meta have started dispensing some of their riches to the creators that feed content into them. This is an exciting paradigm shift, one that has also begun to blur the distinction between <em>passion</em> and <em>profession</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*-XW3XtMQ5EyonQA8DKI1CA.png" /></figure><h3>The OSS creator economy</h3><p>Perhaps the most vital characteristic of this <em>renaissance</em> is that content consumption has also become a precursor to creativity. The ur-platform is TikTok, which enables users to create brand new content by adding small twists to the videos they consume. Though it’s arguable that this is the secret sauce responsible for the app’s runaway success, TikTok’s own model for iterative creativity is far from unique in this regard. In fact, the model itself is a twist of the battle-tested <em>forking workflow</em> in open-source software (OSS), which allows developers to create a copy of someone else’s codebase and modify it to experiment, add new features or even pursue a new development roadmap altogether.</p><p>The fundamental principles governing the social media creator economy — <em>content creation</em>, <em>content consumption</em>, <em>monetisation</em>, and <em>attention</em> — also play a significant role in the generation of content in the OSS network. However, in this case, the process of content distribution presents unique challenges and opportunities. The most important is that in order to solve the problem of <em>attention</em>, one must not only take into account the likes and preferences of the users, but also their ability to interact and engage with such content. In the OSS creator economy, <em>content consumption</em> occurs when a developer becomes a user of a codebase or — more crucially — when a user engages with the community as a contributor. In this sense, consuming content in open source naturally yields <strong><em>experience</em></strong> and <strong><em>reputation</em></strong>. By algorithmically quantifying and storing the experience that developers accrue by using a repo or contributing to a codebase, we can systematically match them to high-value work opportunities that they can provably execute upon. This matching brings with it a possible indirect solution to the monetisation problem in OSS.</p><p><strong>👩‍💻 OSS Contributions → 🎖 Quantifiable experience → 🛠 High-value work opportunities → 💸 Monetisation + more quantifiable experience</strong></p><p>Quantifying experience is also a game-changer for the maintainers who are looking to build an audience for their content. Code contributions are generally recorded in the commit log registry and span a natural mini-network of creators. The open source community is thus a constellation of small collaboration networks interlinked by co-contribution events at the human level, and <em>consumed</em> at the software level through dependency networks. To keep this constellation of collaboration networks alive, we must guarantee that small projects can pitch their vision to the audiences that really care about them. It is for this reason that the success of OSS as a creator economy cannot rely upon hijacking the <em>attention</em> of consumers, but rather must rely upon facilitating opportunities for value creation through <em>highly relevant contributor recommendations</em>. At Quine, we believe that every project should be able to develop a contributor audience and achieve fully organic viral growth. The burden of seeking out and maintaining such an audience shouldn’t fall on the shoulders of individual creators. Instead, the process needs to be embedded as a <em>primitive</em> in content-distribution platforms. To do so, any such platform must take into account the technical ability of the audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TRRp9SUPNWL-pVccigqCgg.png" /></figure><h3>The future of work and education</h3><p>The problems of <em>monetisation</em> and <em>reputation</em> in the OSS creator economy are deeply interrelated with the problems of <em>work</em> and <em>education</em> in software development.</p><ol><li><strong>Education</strong>: For software development, alternative education has begun to seriously challenge the monopoly of traditional education. Lower barriers of entry into the software development industry are sure to benefit the economy, but will also create an apparent over-supply of coders who increasingly feel the need to stand out from the crowd. In this sense, the open source network is set to become the arena in which developers <em>create content</em> to differentiate themselves from other <em>creators</em> and build a brand for themselves. The first version of our platform includes an interface to help developers up-skill and build verifiable experience through open source contributions.</li><li><strong>Work:</strong> Freelancing is one of the most popular ways to monetise one’s reputation and time. This has shrunk the optimal size of “the firm” to one, especially in the context of public codebases and DAOs. In this setting, every software developer is set to eventually become a “<em>factory,</em>” a “<em>brand,”</em> and a unit of “<em>economic value</em>” that interoperates with other developers and organisations through APIs and decentralised protocols. As the dynamics in dev freelancing begin to resemble B2B transactions, it becomes more important than ever to be able to systematically allocate talent to the work which yields the highest value. The next major release of Quine will provide a solution to this problem through an unprecedented ML-powered solution.</li></ol><p>At Quine, we’re crunching code and OSS metadata to mathematically verify and quantify a developer’s experience, and to help every developer showcase the skills and talents which set them apart from the herd. Our objective as a company is to use systemic talent allocation to unlock the data incentives at the heart of software development in private organisations or public goods.</p><h3>Quine</h3><p>So what’s <strong><em>experience quantification</em></strong>? For us, quantifying experience does not mean reducing developers to a one-dimensional score or some sort of scalar value. Instead, we’re sketching machine-learning vector representations of developers from the content they have created in the open source ecosystem in order to connect them to the codebases and issues most in need of their specific technical skills (a technical blogpost about this is coming soon). While today we can allocate developers to the OSS repos where contributing best exercises their talents — providing them the opportunity to build a reputation they can leverage into paid work — our ambition as a company is to equip the open source software ecosystem with an end-to-end infrastructure for systematic talent allocation. That is, Quine will algorithmically connect developers to paid professional briefs which best suit their skills and interests. With the advent of DAOs and decentralised protocols, this problem is more relevant than ever.</p><p>In order to mathematically understand the experience of software creators, however, we first need to organise and understand the content they have created. To this end, we spent the last year semantically indexing over 155,000 repositories on GitHub, and wrapping those vector representations around a dev-facing UI. The alpha version of our platform is designed to help software creators build and showcase an impressive open source portfolio that highlights their superpowers as coders and their individuality as software creators. Quine-alpha features the following:</p><ul><li><strong>A recommendation system that, given a set of target languages and topics, matches developers to repositories having an unusually high concentration of <em>unassigned good-first-issues</em>.</strong> This is our first attempt to tackle the <em>attention</em> and <em>content creation</em> problem in open source, while helping maintainers build an audience of contributors for their repos. The same ML technology has also been repurposed into two uncorrelated information retrieval tools, the one designed to find new open source tooling, the other to find alternatives to target repos.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DpHi0maTad_eYMjb-jLqyg.jpeg" /></figure><ul><li><strong>A next-generation developer profile which focuses on <em>verifiability</em></strong> (computationally, a precursor to <strong><em>quantifiability</em></strong>). In this first release, Quine profiles will verify developer experience in a programming language by automatically extracting all supporting evidence from their GitHub account, down to the commit level. Users can also pin and comment on their most significant GitHub achievements, along with viewing and interacting with 100% of the metadata associated to them (including Issues, PRs, Stargazers).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wHKGDetH-VNPMBp4fSQuhg.jpeg" /></figure><p>We built Quine to <em>conserve and create value</em> in the open source ecosystem. The job market has reduced software developers to a small set of labels: ”frontend,” “backend,” “databases,” and so on. However, the sum total of a developer’s experiences is far more textured and profound than any of those labels might suggest. So much of the data which could otherwise be utilised to identify the strengths and interests of individual developers languish ignored. At Quine, we embrace the spectrum of individual insights, worldviews, and aspirations of which the open source software developer ecosystem is comprised, placing it at the centre of everything we build.</p><p>The OSS network needs to be equipped with the infrastructure necessary to provide its creators and consumers the same fluidity and opportunities for remuneration proven by other platforms to be economically viable. Together with <a href="https://quine.sh/">the rest of our products</a>, we’re equipping the OSS ecosystem with the technology necessary to manage the core elements of its creator economy: <em>content creation</em>, <em>content consumption</em>, <em>monetisation</em>, and <em>attention</em>. Solving this for the open source software ecosystem, the will directly transform the software development labour market as we know it, and the <em>future-of-work</em> as a whole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdzY7mh97m9a0LPwLlU2yw.png" /></figure><p><em>Thanks to </em><a href="http://twitter.com/emayovunefe"><em>@emayovunefe</em></a><em> for his help in preparing this blogpost! Artwork from </em><a href="https://www.asciiart.eu/"><em>asciiart.eu</em></a><em> and Michelangelo — </em>Written with ❤️ by <a href="https://quine.sh/"><strong>Quine</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d450d2e0f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 1st commit of git/git no longer belongs to Linus Torvalds]]></title>
            <link>https://medium.com/@r0dms/the-1st-commit-of-git-git-no-longer-belongs-to-linus-torvalds-ea1df6f8f025?source=rss-e971f946d084------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea1df6f8f025</guid>
            <category><![CDATA[exploit]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[nft]]></category>
            <dc:creator><![CDATA[Rodrigo M.S.]]></dc:creator>
            <pubDate>Thu, 11 Nov 2021 17:33:57 GMT</pubDate>
            <atom:updated>2021-11-12T10:52:36.799Z</atom:updated>
            <content:encoded><![CDATA[<p><em>or how the GitNFT community found an exploit in GitHub</em> ✨</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1YDejJ1NzqSd5hRULskQpg.png" /><figcaption><a href="https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23ca2e25604af290">https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23ca2e25604af290</a></figcaption></figure><p>It’s been a few months since we released the first version of <a href="https://gitnft.quine.sh/">🔮GitNFT</a>, a platform which allows open source software creators to mint NFTs of their commits on GitHub and sell them in the OpenSea marketplace <em>as art</em>. GitNFT is a tribute to the contributors who wrote the code that is at the backbone of our society and global economy, and a mechanism for OSS creators to engage with their fans and monetise their social capital. We believe that the <em>open source monetisation problem</em> can’t be fully solved through patrons and donations, so we challenged ourselves to reimagine a solution from the lenses of crypto, decentralised networks, and creator economies.</p><p>While bootstrapping our early community and incubating the project, we’ve been fortunate enough to amass <a href="https://opensea.io/collection/gitnfts">a collection</a> that now includes GitNFTs from <a href="https://github.com/metamask">MetaMask</a>, <a href="https://github.com/bitcoin">Bitcoin</a>, <a href="https://github.com/homebrew">Homebrew</a>, amongst several others. In doing so, we have had the privilege to learn from our early community and see how developers study, use, and (try to) hack our product. While we’ve benefited from most of these learnings, <strong><em>we were recently made aware of an exploit that allows anyone to claim public authorship of a particular set of open source commits</em></strong>. To make a point, <strong>@VanTudor</strong> (GitNFT’s lead developer) <a href="https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23ca2e25604af290">managed to assign git/git’s first commit on GitHub to himself</a> (see image above). The purpose of this blogpost is to raise awareness of this issue amongst the community and with GitHub more specifically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ZGD9ohfuMNW1ZyTaLkjUg.png" /></figure><p>How did this all start? Last Saturday we received an unusual message <a href="https://discord.com/invite/ChAuP3SC5H">in our Discord channel</a>. A developer going under the name of <a href="https://github.com/nbanmp"><strong>@nbanmp</strong></a> shared a link to a GitNFT minted asset for Linus Torvald’s first commit of <a href="https://github.com/git/git">https://github.com/git/git</a> titled <em>Initial revision of “git”, the information manager from hell. </em>We initially thought it was a joke, but to our surprise, the repo matched the URL of the original repository. After inspection we realised that <strong>@nbanmp</strong> had indeed managed to impersonate Linus and mint a GitNFT having as underlying the first git commit in the universe. When looking at our verification protocol we discovered an exploit on GitNFT’s side which, after further investigation, uncovered an even more serious glitch on GitHub’s side.</p><p>To understand what happened, we need to share a few more details about the way GitNFT works. By design, GitNFT will only let you mint NFTs of the commits you have authored (or co-authored). The GitHub identity of the author is verified through OAuth, while the authorship is validated by examining the commit response in the <a href="https://docs.github.com/en/rest/reference/repos#list-commits--code-samples">GitHub’s REST API</a>. The response looks something like this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f719cdc48a225875fc61b004cd459d3b/href">https://medium.com/media/f719cdc48a225875fc61b004cd459d3b/href</a></iframe><p>In particular, note that there is authorship metadata in both commit.author and author. The former is the identity information added to the commit through <strong>git</strong>, and includes the name, email, and date of the author. The latter is the author’s identity through GitHub’s lens which, along with the author’s id, login, and pointers to the user’s social metadata.</p><p>The exploit from <strong>@nbanmp</strong> was possible because GitHub’s method of populating the author field is bogus. GitHub allows users to add email addresses to their account, but does not require the user to verify the email address. When the commits have a null author field (which is the case for the commits of popular repositories that pre-date the octocat), GitHub will populate author with the data of the latest account to have added that email address, <strong><em>regardless of whether the account is verified or not!</em></strong> As a result, <strong>@nbanmp</strong> managed to<em> accidentally kill it </em>as he eloquently described in his GitNFT, while <strong>@VanTudor</strong> was able to list himself as the creator of git!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kOVz5UFdjepY7eY6b-LZsA.png" /></figure><p>This might seem like an innocent, insignificant glitch, but we think it is actually a big deal! Open source contributors don’t usually get compensated for their work, so ensuring that they get the credit they deserve is the least we can do. In open source, authorship attribution is an inalienable right — a right that should be guaranteed by the platform in charge of safeguarding the world’s open source code. We submitted a report to Github through HackerRank, but it was marked as closed after a couple of minutes. We hope that this matter gets enough attention and that GitHub helps ensure that the creation kudos go to the right persons — even if they’re not GitHub users!</p><p>How does it affect GitNFT? Certainly, our collection is now scarred by <strong>@nbanmp</strong>’s weird NFT. However, we see this imperfection as an enrichment to our collection because it immortalises the discovery of this exploit, and hopefully helps incentivise its resolution. The good news is, that GitNFT uniqueness is enforced by the author’s id on GitHub rather than the email, so if Linus ever wants to mint the real <em>Initial revision of “git”, the information manager from hell</em> he’ll be able to do so. GitNFT is still in incubation and a new version is on the way! If you’re a maintainer or open source contributor and are interested to fund your work through GitNFTs, we’d love to chat!</p><p>Kudos to <a href="https://medium.com/u/f118bbfc607f">Tudor</a>, <a href="https://medium.com/u/51421f415649">E.M. Ayovunefe</a>, and the rest of the Quine team for their help in preparing this blogpost! <em>— </em>Written with ❤️ by <a href="https://quine.sh/"><strong>Quine</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea1df6f8f025" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Devs have eaten the world]]></title>
            <link>https://medium.com/quira/devs-have-eaten-the-world-523c8a1d1da2?source=rss-e971f946d084------2</link>
            <guid isPermaLink="false">https://medium.com/p/523c8a1d1da2</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[capitalism]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Rodrigo M.S.]]></dc:creator>
            <pubDate>Wed, 27 May 2020 21:56:37 GMT</pubDate>
            <atom:updated>2024-06-24T04:17:55.922Z</atom:updated>
            <content:encoded><![CDATA[<p><em>And still have room for dessert </em>🍰</p><p>We’ve all heard about Marc Andreessen’s famous essay <a href="https://a16z.com/2011/08/20/why-software-is-eating-the-world/">“<em>Software is eating the world</em>”</a>. The essay speaks about the increasingly evident hyper-growth opportunities in the internet and software industries at the beginning of the previous decade. Nine years after its publication, software has finally eaten the world. Smartphones, online banking, and Uber are now mainstream. User interfaces are more fluid than ever and have delivered a degree of human-computer interaction that was not long ago considered futuristic. Software products and services can now be built, delivered, and scaled at an unprecedented rate. The effects of this technological bonanza are well-known to all: <em>TikTok</em>, <em>Bitcoin</em>, <em>AirPods</em>, billionaires. The causes are often attributed to the cooccurrence of key macroeconomic events like the democratisation of software education, the advent of <em>Amazon EC2</em>, and the statistical viability of the startup model. Though these events tell most part of the story, none would have been possible without the time and effort from the people that created, maintained, and popularised the stack over which syllabi, servers, and startups stand. I’m not talking about business icons like Bill Gates or Steve Jobs (although they deserve a honorary mention), but the group of hobbyists, hackers, and programmers that created the tools our economy now depends on — a group commonly know as the <em>open-source community</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*gLEBguMrnb6IWxESxKUYVA.png" /></figure><h3><strong>On the economic paradoxes of open-source</strong></h3><p>Though the genesis of open-source can be traced back to the 1950s, its triumph as a paradigm for open and decentralised collaboration is relatively recent. In terms of the economic boom of the 2010s, its importance is multifaceted. To start with, it built and socialised the software tools, coding conventions, and workflow patterns that developers around the world now work under. Thanks to open-source, devs became a globalised workforce that wield the same toolset and parlance. At the same time, it helped programming languages reach a level of universality that is almost comparable to mathematical notation. This didn’t happen overnight. The programs we now summon with yarn, brew or pip are the result of a long natural selection process which subjected their architecture, structure, and APIs to savage competition. During this evolutionary course the most capable projects were not necessarily those that secured a committed pool of maintainers, but those that made their way into the guts of other community projects and turned themselves into <em>dependencies</em>. This created a positive-sum game - a sort of mutualism between codebases in which the guest builds network effects by absorbing parts of its host’s computational skeleton thus making it cleaner, faster, and more maintainable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*-jZ62QCkxDGgElJ_HgR7bw.png" /></figure><p>Modularising code in dependencies has saved humanity billions of years in development time, but unfortunately under a negative-sum game. <em>Why? </em>Because maintaining dependencies requires developer work which, in an economy that is based on software, is as valuable as gold. A number of monetisation models for open-source work have been put forward in the last decade, but none of them has been able to scale and solve the problem in a fundamental way. The reason being, open-source work is a microeconomic singularity — a paradox in capitalism that can’t be corrected with donations, cryptocurrencies, or freemium models. Indeed, the open-source ecosystem produces economic value at scale, but this value <em>can’t</em> be back-propagated to the creators. The reason for this is more philosophical than technological: if a fair and transparent mechanism to re-distribute value existed, it would incentivise creators to organise around investable legal entities to more efficiently capture a greater chunk of the dependency market share. This would clearly antagonise the values behind the movement and vilify its spirit with for-profit aspirations. <em>Why then, do open-source contributors continue to spend time working on these projects?</em> This is a fundamental question. In some cases, incurred opportunity costs can be mapped to clear long-term incentives like learning new skills, work opportunities or even access to the venture-capital markets. However, in general, motivations are rooted in deeper human aspirations like the willingness to give back to the community, indulging into intellectual pleasure, or even the ego gratification associated with building stuff that peers may find cool or clever.</p><p>Open-source is the fabric of our digital cosmos and the raw material software products and services are built with. Our supply chain is built on software, yet code is not a fungible asset one can generally trade or exchange. <em>What then is the real source of value in our software economy?</em> It turns out that the key commodity sustaining our digital world is far from cybernetic. It’s an abstract resource that countries are desperately trying to produce and companies are fiercely fighting for: <em>developer time</em>.</p><h3><strong>Macro trends</strong></h3><p>The work of code creators has percolated into every corner of the supply-chain. They have built the databases supporting our healthcare infrastructure, the ML algorithms driving our Teslas, and the computer graphics engines rendering our video-games. In doing so, a number of powerful macroeconomic trends have started to unfold:</p><ol><li>The barriers of entry to software development have significantly lowered. MOOCs, Q&amp;A platforms, and coding bootcamps have democratised software engineering knowledge and evangelised open-source tools. Alternative education models have succeeded to the point that the credential-driven model for talent validation has began to shatter. College graduates and high-school dropouts are now competing for jobs that only 15 years ago were reserved for CS PhDs.</li><li>The industry has accepted that, for software engineering jobs, remote work works. This trend has been further validated by COVID-19 work-from-home strategies. For example, Facebook and Twitter <a href="https://thehill.com/policy/technology/499248-remote-working-takes-off-for-twitter-facebook-tech-companies">recently announced</a> permanent remote-work policies for their employees.</li><li>The market dominance of git as a version control tool, and of <a href="https://guides.github.com/features/issues/">issues</a> as a way to modularise work and manage tech-debt in public codebases have proved that <em>decentralised</em> work is also possible, at least in the software development space. This has contributed to the success of cloud code-hosting platforms like <a href="https://github.com/">Github</a>, <a href="https://about.gitlab.com/">Gitlab</a>, and <a href="https://bitbucket.org/">Bitbucket</a>, which are gradually integrating larger parts of the DevOps delivery pipelines into their products.</li><li>The success of open-source has also neutralised skeptics, or at least forced them to <a href="https://www.theverge.com/2020/5/18/21262103/microsoft-open-source-linux-history-wrong-statement">apologise and adapt</a>. Geopolitically speaking, open-source has become the new battle-ground where companies signal influence, creativity, and innovation. Facebook, for example, maintains <a href="https://github.com/pytorch/pytorch">PyTorch</a> and <a href="https://github.com/facebook/react">React</a>, both leading projects in their categories. Software is no longer an asset that has value in its own, but as vehicle used to deliver services and products.</li></ol><p>The world is changing. The present looks exciting and the future optimistic, but a number of problems have also become evident:</p><p><strong>(1)</strong> Lower barriers of entry to the dev profession have created a noisy supply side with respect to skillsets and experience. Coding education has been standardised, yet writing software remains a highly artistic, textured, and creative feat that requires time, experience, and exposure to be mastered. Talent sourcing and assessment processes need to adapt to this new complexity.</p><p><strong>(2)</strong> Remote work has started to be accepted in the private sector, but the public sector still needs to catch up. Immigration policies and taxing laws impose severe regulatory frictions in the processes of hiring foreign talent. Many startups can’t afford this type of operational overhead. Competition in a global market requires access to the global workforce.</p><p><strong>(3)</strong> Cloud code-hosting providers, especially Github, are gradually controlling more sectors of the ecosystem’s infrastructure. It recently announced <a href="https://github.blog/2020-03-16-npm-is-joining-github/">the acquisition of NPM</a>, the leading package manager for Javascript. Monopolies that lock-in code, devs, or workflows can cause irreparable damage in the ecosystem and offend open-source principles.</p><p><strong>(4)</strong> Companies are deploying considerable resources into growing their open-source agenda, but the governance of the projects they maintain is not always open. Controlling the development roadmap of a particular tool can lead to the acquisition of unique competitive advantages, often at the expense of the ecosystem.</p><p><em>How does this affect devs and companies?</em> The playground is changing. At the time of writing this article, the world is going through a mass remote-work experiment that has so far validated its feasibility. Developers and companies need to adapt to a future where work is remote and decentralised, where education opportunities are abundant and open, and where experience can no longer be summarised by a CV or a LinkedIn profile.</p><h3><strong>Dev-Market Interfaces (DMIs)</strong></h3><p><em>Developers have eaten the world</em>. Their work has not only become a main driver for economic expansion, but a key supporting vector for civilisation. Still, the labour markets are far from being efficient. Companies are fighting for talent in the same arena where devs are settling for positions that barely align with their ambitions and work-life balance requirements. In an era like this marginal improvements in talent allocation can unlock incredible amounts of economic value. This is not easy to accomplish. The market currently reduces software creators to a few sets of keywords — devops, python, frontend, full-stack, and vets them with theoretical CS tests and subjective interviews. However, the journey and experience of a developer is extremely textured and can’t be appropriately assessed with a LinkedIn profile or a coding test. With so many variables to control, it’s more important than ever to diverge from the establishment and empower companies &amp; devs with new <strong><em>interfaces</em></strong> to the labour markets. Some that can abstract away the noise from the real world and the complexities companies have inherited from dinosaur-era HR practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KfKsF9Fb-qIX-e94FJ5zyQ.png" /></figure><p>At <a href="https://quira.sh/">Quira</a> we’re building <strong><em>technology</em></strong>, <strong><em>machine intelligence</em></strong>, and <strong><em>marketplaces </em></strong>to help programmers and companies interact with the labour markets in a more fluid and human-centric way. In other words, <strong><em>dev-market interfaces</em></strong> that create frictionless experiences between software creators and capitalism. We believe that with the right mix of data, technology, and mechanism-design we can port the remote &amp; decentralised workflow that made open-source flourish to the private sector — all while empowering devs and the open-source ecosystem. We’re a company at the intersection of <em>ML</em>, <em>dev-tools</em>, and <em>economics</em>. We believe in open-source, but make no assumptions on its monetisation strategies. Instead, we treat it as a hugely underserved <em>passion economy</em> with misaligned incentives that is inadvertently guiding us towards the <em>future-of-work</em>.</p><p>Keen to hear more? <a href="https://quine-sh.typeform.com/to/MCxXb1">Sign-up to our newsletter</a> — we’d love to keep you updated. Else, shoot us an email at info [at] quira [dot] sh.</p><p><em>Artwork from </em><a href="https://www.asciiart.eu/"><em>asciiart.eu</em></a><em> — </em>Written with ❤️ by <a href="https://quira.sh/"><strong>Quira</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=523c8a1d1da2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quira/devs-have-eaten-the-world-523c8a1d1da2">Devs have eaten the world</a> was originally published in <a href="https://medium.com/quira">Quira</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>