<?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[tokenstreet tech - Medium]]></title>
        <description><![CDATA[Stories from the people who build tokenstreet - Medium]]></description>
        <link>https://medium.com/tokenstreet-tech?source=rss----af11fc72a181---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>tokenstreet tech - Medium</title>
            <link>https://medium.com/tokenstreet-tech?source=rss----af11fc72a181---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:53:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/tokenstreet-tech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Confession to Open Source]]></title>
            <link>https://medium.com/tokenstreet-tech/confession-to-open-source-dd7c2ae087d5?source=rss----af11fc72a181---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd7c2ae087d5</guid>
            <category><![CDATA[open-source-software]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[coinpanion]]></category>
            <category><![CDATA[tokenstreet]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Daniel Reichhart]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 15:41:52 GMT</pubDate>
            <atom:updated>2022-03-30T15:41:52.468Z</atom:updated>
            <content:encoded><![CDATA[<p>When the codebase grows, a sensible separation of the individual components is worth a fortune. Be it to keep the overview or to be able to delimit the origin when searching for errors. This improvement was the initial motivation to separate our <a href="https://github.com/tokenstreet-tech/react-native-idnow-videoident">wrapper for the IDnow Video Ident SDK</a> from our app.</p><p>During this decoupling, I was already playing with the idea of making the wrapper public. We use more open source technology these days than ever before. Without this groundwork, we wouldn’t be where we are today with our product. It feels fair to give something back to this community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zjrzPAY8yZ_wgF7ER38LPg.jpeg" /></figure><p>Beyond that, there are other benefits: It’s a way for developers to show the world out there that they produce “awesome shit”. By that, I don’t just mean the product for the end-user, but also writing high quality and maintainable code. They can demonstrate that they are keeping up to date with new technologies and finding innovative approaches to solve problems.</p><p>Moreover, this also attracts new talent. They can already see parts of the source code that this company is working on. This makes it easier for them to assess whether they can identify with their way of working, their ambitions and as part of the team.</p><p>Two weeks ago, <a href="https://en.coinpanion.com/">Coinpanion</a>, an Austrian company developing an app that allows investors to invest in crypto portfolios via a savings plan conveniently, approached us with a request that accelerated this process. They had tested our app and noticed our IDnow integration. Coinpanion also has a use case for this, and they asked us to share our integration with them. We were happy to comply with this request, and therefore we made our GitHub repository and the associated NPM package public the following day.</p><p>This request shows further advantages: We follow the <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">DRY</a> paradigm, only taken further. Several companies have this use case. It doesn’t make sense for each of them to have its individual integration, with its own advantages and disadvantages. Instead, we can work on it together and focus our time on the relevant features for our end customers. In addition, it strengthens inter-organisational collaboration and sharing. It can be encouraging to know that we are all facing the same challenges and also helps to share solutions. Why should we establish a dog-eat-dog society when we can reach out to each other?</p><p>Of course, this collaboration under the umbrella of our GitHub repository comes with a responsibility. Specific issues affect open source collaboration. Unfortunately, we see these far too often. That’s why we try to prevent them as much as possible. To keep it simple: We do not publish what we would not use ourselves. More precisely, we mean:</p><p>Everything we’re making open-source, we use in production. We follow common best practices and document everything well to keep it understandable for our future selves and other developers.</p><p>Nevertheless, we do not claim to write the best code. Therefore, any developer is welcome to challenge any line of written code. We are always open for contributions and suggestions for improvement. For this to work, we are committed to dealing with issues and pull requests within a reasonable time. Also, all milestones are public, and there is no internal copy of the repository that we use for our products.</p><p>To avoid security concerns, we use Dependabot to ensure that the SDKs and all packages used are always up to date. In addition, our source code is regularly checked for vulnerabilities by analysis tools.</p><p>In case we get to the point where we stop maintaining a project, we release everything under the MIT licence. This model makes it accessible for anyone to fork our code and take over maintenance.</p><p>Finally, I have to say that I am pleased with how our open source strategy has evolved in the first quarter of 2022. I am thrilled to currently have the opportunity to shape the developer culture at tokenstreet. This was only the beginning. Cheers to the open-source community and good cooperation!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd7c2ae087d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenstreet-tech/confession-to-open-source-dd7c2ae087d5">Confession to Open Source</a> was originally published in <a href="https://medium.com/tokenstreet-tech">tokenstreet tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>