<?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 Jonas Peeck on Medium]]></title>
        <description><![CDATA[Stories by Jonas Peeck on Medium]]></description>
        <link>https://medium.com/@aGuyNamedJonas?source=rss-19f6e9305a42------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RHtq07as4T-ZoLvhSVmQnw.jpeg</url>
            <title>Stories by Jonas Peeck on Medium</title>
            <link>https://medium.com/@aGuyNamedJonas?source=rss-19f6e9305a42------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:10:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aGuyNamedJonas/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[Do your git blames show your technical skills? Yes and No.]]></title>
            <link>https://medium.com/axel-springer-tech/do-your-git-blames-show-your-technical-skills-yes-and-no-2da5b88315e6?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/2da5b88315e6</guid>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Thu, 29 Dec 2022 22:01:07 GMT</pubDate>
            <atom:updated>2022-12-29T22:01:07.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2sTZLC-t0ANotOr1w5goA.png" /></figure><h4>Generating tech-stacks based on git blames — an experiment</h4><p><strong>&gt; TL;DR: Today we’re releasing two POC Open Source projects:</strong><br><a href="https://github.com/axelspringer/sklls-cli">sklls-cli</a> — sklls is a simple CLI tool that aggregates git-blames by committer and generates line-counts for every committer based on file-extension and NPM dependencies.</p><p><a href="https://github.com/axelspringer/codecrew">codecrew</a> — codecrew makes it easy to discover the software developers inside your Github organization based on techstack</p><p>— — — —</p><p>In 2022 we set out to try and answer one simple question: Can you tell somebody’s tech-stack based on their git-blames?</p><p>The purpose of this experiment: Try to create a data-driven way of connecting software developers at Axel Springer based on their tech-stack.</p><p>Did it work?</p><p>Yes and no — but the reason is not what you think ;)</p><h3>The idea</h3><p>No matter if you work in frontend, backend, devops, fullstack, mobile or data &amp; AI — we all produce the same work output: Code ❤</p><p>And no matter if you use Github, Bitbucket or Gitlab, they all have one thing in common: Version Control with git. So every line of every piece of code ever written can be accurately attributed to one person inside of that Github / Gitlab / Bitbucket organization in the form of git-blames.</p><p>So the idea was simple: How can we turn git-blames into tech-usage profiles that can roughly tell how much somebody uses specific technologies?</p><h3>Hey Siri, find me someone who uses redux-mock-store v1.5.4</h3><p>As part of our experiment, we created two pieces of technology which we’re open sourcing today.</p><p>One of them is <a href="https://github.com/axelspringer/sklls-cli">sklls-cli</a>, a go based CLI that converts git-blames into line-counts for each contributor of a repository, so that it becomes easy to figure out what kind of files they contributed most to (e.g. .tsx, .py, .js etc.) and which NPM libraries were used most often by that person.</p><p>The result was stunning: All of the sudden we could actually find people who were using specific NPM libraries — in the example below you can see the search results inside codecrew when typing in “redux”.</p><p>Exactly what we wanted to achieve with our experiment: Create the ability to connect with <em>specific</em> people based on a shared use of a <em>specific</em> technology.</p><p><a href="https://github.com/axelspringer/codecrew">codecrew</a> is the other project we’re open-sourcing today — a visualization layer for the data we generated with sklls-cli. Together with the data created by the sklls-cli, and the Github API, we wanted to create a place where all members of a Github organization can find each other — based on tech-stack.</p><p>codecrew is a completely backendless approach. It’s a statically built website, hosted on (private) Github pages, automatically updated through Github Actions and fed through the Github API.</p><p>It was all coming together at that point. The right data, meeting the right kind of visualization to be useful, and then came a huge buzzkill….from Github.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*70tM6C43iHRn8_uENHrtIQ.png" /><figcaption>Screenshot from the codecrew search box — finding developers based on NPM dependencies</figcaption></figure><h3>Github’s missing verification of usernames &amp; emails</h3><p>So we created a tool that converts git-blames into technical profiles and a UI that combined that data with data from the Github API to create a self-updating team-directory for Github organizations.</p><p>Sounds pretty damn great right?</p><p>Yes in theory. But in practise there was no good way to actually map the git-blames we found to the actual Github users of a Github organization. And it’s not git’s fault — it’s Github’s fault for not verifying the usernames &amp; emails used in git commits.</p><p>Case in point: Pretending to be Dan Abramov on Github is as simple as entering his username and the public email from his Github profile in your git commit config and pushing your code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*0noSkIbt_NkvpbuUp9dIWw.png" /><figcaption>Pretending to be Dan Abramov on Github is as simple as that 👆🏻</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MjWlnc1dCWWDX23sgcW3yw.png" /><figcaption>Git commit after pushing it to github</figcaption></figure><p>And just like that one of JavaScript’s most prolific and best known Developers has contributed a commit to our little project.</p><p>Don’t believe me? Check out the live-commit below and be sure to actually click on the “gearon” username to verify that — yes — for all Github knows and makes you believe, this is <em>the</em> actual Dan Abramov (who still works for Meta and not Axel Springer) who kindly contributed a commit to our project:<br><a href="https://github.com/axelspringer/sklls-cli/commit/26f7be7f3bb03689bd0e62314c874d2b7cedd9e5">https://github.com/axelspringer/sklls-cli/commit/26f7be7f3bb03689bd0e62314c874d2b7cedd9e5</a></p><h3>Not being able to map emails ruined our experiment</h3><p>As silly as it sounds, but this is where the experiment fell flat.</p><p>We wanted to create this beautiful, auto-updating team-directory of everyone’s dreams — a place where software developers find the other software-developer-needle-in-the-haystack-of-commits who uses the same esoteric NPM dependency as they do, that now decided to introduce breaking changes and a need to find someone to talk migration strategy with.</p><p>From the looks of it, we did succeed in creating the perfect team-directory for software developers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WfyrYgk95S5hObj0ZwRtPg.gif" /><figcaption>Demo of <a href="https://github.com/axelspringer/codecrew">codecrew</a> in action</figcaption></figure><p>But obviously this fun &amp; engaging UI is powered not by the git commits — it’s powered by Github’s API spitting out pretty profile pictures &amp; usernames, links to Github profiles and what team someone belongs to.</p><p><strong>And that’s where our experiment broke down:</strong> We simply couldn’t map git commits to Github API well enough to be able to deliver a quality experience or even close to a complete coverage of all of the members of our Github Org. In our experience, most software developers in our Github organization actually ended up using 5–6 different email addresses (myself included).</p><p>Given the fact that every Github user only has one company email address linked to their account (through the SSO link), we could only get mediocre mapping results, rendering the wealth of git-blames we could aggregate fairly useless to the final product (the visual team-directory).</p><p>So to conclude the experiment and this article’s headline:</p><h3>Do git-blames show your technical skills? No they don’t!</h3><p>…they just show quantity.</p><p>That’s another thing we (obviously) discovered: Counting lines as a proxy for <em>actual</em> skill obviously is as accurate as counting a screen design by how many pixels it has. Line-counts are good as a proxy, but not as an actual <em>proof of skills</em> (not that that was ever out goal).</p><p>So no, technically git-blames don’t <em>show</em> your technical skills, they somewhat <em>hint</em> at it. Especially if you take into account our mapping inaccuracies.</p><h4>And yet they kind of do</h4><p>Still: We found that the profiles were fairly accurate. Many people had a clear focus (e.g. frontend or backend) just by looking at the file extensions they most committed to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcUKzoGM4LywL4wEQxzlfA.png" /><figcaption>Tell me you’re frontend without telling me you’re frontend (Screenshot from codecrew)</figcaption></figure><h3>So we decided to Open Source it instead</h3><p>In the last couple of years in my role as <em>Intrapreneur Global Community Development</em> at Axel Springer, I was given the chance to build and test out different ways to connect our global tech community.</p><p>Creating the sklls-cli and codecrew was another super interesting approach that we tried out, but turned out to be too flawed in the end of the more than just a proof of concept.</p><p>Still, the data we were able to draw from git-blames using the sklls-cli was super interesting — and perhaps somebody else can figure out a better way to connect that data to Github profiles. If you’d like to try — have at it!</p><p>Today, we’re open-sourcing both sklls-cli and codecrew. Check them out below &amp; happy hacking!</p><p><a href="https://github.com/axelspringer/sklls-cli">sklls-cli</a> — sklls is a simple CLI tool that aggregates git-blames by committer and generates line-counts for every committer based on file-extension and NPM dependencies.</p><p><a href="https://github.com/axelspringer/codecrew">codecrew</a> — codecrew makes it easy to discover the software developers inside your Github organization based on techstack</p><p><strong>Jonas Peeck is the founder of uncloud</strong> —the first cloud platform that configures itself based on your code — and has previously worked at Axel Springer as an Intrapreneur for Global (Tech) Community Development.</p><p><a href="https://www.linkedin.com/in/aguynamedjonas/">Connect with me on LinkedIn<br></a><a href="https://getuncloud.com/">Check out uncloud</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2da5b88315e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/do-your-git-blames-show-your-technical-skills-yes-and-no-2da5b88315e6">Do your git blames show your technical skills? Yes and No.</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Lambda Functions with 11TB RAM? Yes we can! (sort of)]]></title>
            <link>https://medium.com/axel-springer-tech/aws-lambda-functions-with-11tb-ram-yes-we-can-sort-of-e48a522c267b?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/e48a522c267b</guid>
            <category><![CDATA[aws-cdk]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 27 Sep 2021 10:18:20 GMT</pubDate>
            <atom:updated>2021-09-27T10:18:20.106Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iOz2qosTBIk_mxdNUb7oA.jpeg" /></figure><h4>Using self-terminating EC2 instances for heavy-duty tasks in serverless architectures</h4><p>In one of our recent projects, parts of our serverless processing pipeline was getting too computationally intense for what AWS Lambda functions can handle.</p><p>So instead of refactoring the whole system, we instead took an unusual route: We replaced the lambda function in question with a self-terminating EC2 instance.</p><p>Here’s what we’ve learned :)</p><h3>Exceeding lambda CPU &amp; Memory limits</h3><p>While lambda functions currently have a maximum timeout of 900 seconds (15 minutes) they also have some constraints on computational power.</p><p>AWS Lambda functions can be configured to use up to 10GB of RAM which simultaneously controls the vCPUs that are allocated for that run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-1J2nu9RDsR2ZYX-KgU-RQ.png" /><figcaption>From the AWS lambda manual: Memory and CPU limits</figcaption></figure><p>For most use-cases that’s plenty. But it can get you into trouble when your computational needs start to exceed these limits (as happened in our case).</p><p>What’s important to remember in this scenario is that <em>serverless</em> does not only mean zero-deployment work and pay-by-invocation, but also an <em>events based</em> model to trigger invocations.</p><p>So switching away from a serverless architecture for parts of the pipeline also would have meant refactoring the invocation logic away from a push- (=events trigger the computation) to a pull behavior(=Queues are filled and worker nodes listen to that queue).</p><p>Unless you find another way…</p><h3>Self-terminating EC2 instances to the rescue</h3><p>So yes, we could have probably refactored our too-big-for-its-shoes lambda function to run as an ECS task and listen to a SQS queue like a normal person.</p><p>We decided to take an unusual route instead.</p><p>To preserve our serverless architecture, where the individual parts of our processing pipeline were either triggered by a cron-schedule or by a file from the previous stage being written to S3, we decided to try and scale up the lambda function instead.</p><p>The lambda function in question was an aggregation step anyways — so nothing we’d want to invoke in a highly parallel manner. Plus we had written our lambda code with go and in a way that was locally executable. So it was easy for us to run it on EC2, instead of in a lambda context.</p><p>To make it work, we added three things to our aws-cdk based infrastructure code:</p><h4>#1 Upload binaries to S3</h4><p>First we had to make sure we have code to run on the EC2 machines. To keep it simple, we used the <a href="https://docs.aws.amazon.com/cdk/api/latest/docs/aws-s3-deployment-readme.html">aws-s3-deployment</a> aws-cdkmodule to upload our locally compiled go binaries to S3:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d0445d720bba162e33d1dc8a51d6cfe/href">https://medium.com/media/9d0445d720bba162e33d1dc8a51d6cfe/href</a></iframe><h4>#2 Create EC2 launch template with user data script</h4><p>Next, we had to find a way to run those binaries on our EC2 instances on startup.</p><p>Luckily, it is possible to define a startup-script for EC2 machines. AWS refers to this as “user data” and, like the rest of our infrastructure setup, it can easily be configured in aws-cdk code.</p><p>In this user data script, we accomplished four things: (a) Download our binaries from S3 to the local /temp folder (b) Run the binary to do its job and pipe its output into a log file (c) Upload that log file to S3 for debugging (d) Shut the machine down:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/da4fb3d403fb482d0b1fb8a2db64ecd1/href">https://medium.com/media/da4fb3d403fb482d0b1fb8a2db64ecd1/href</a></iframe><p>All we had to do next, was to bake that user-data script into an EC2 launch template, which we would use later to launch an EC2 machine from our original lambda function (the one we’re replacing with this much more powerful EC2 machine):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d616dc3634c4ef8f65260ad037a8710a/href">https://medium.com/media/d616dc3634c4ef8f65260ad037a8710a/href</a></iframe><p>Notice how we’re setting the shutdown behavior to TERMINATE. This lets us call shutdown (standard unix command) from the user-data script to ensure the machine is terminated once our binary had completed its work.</p><h4>#3 Launch EC2 instance from lambda function</h4><p>With all of the pieces in place, all that was left to do was to launch the EC2 instance from a lambda function — we actually used the lambda function we wanted to replace to accomplish that.</p><p>In effect this meant that the lambda function we needed to replace was still triggered by the same event (an S3 upload) — in this case however instead of doing the work itself, it merely launches an EC2 instance with our previously crafted launch template:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b7d6c2c978e9d021ea9adec7b6705e4d/href">https://medium.com/media/b7d6c2c978e9d021ea9adec7b6705e4d/href</a></iframe><p>Since we’re using the launch-template we defined earlier, everything the machine needs is taken care of: Access rights, machine type and the user-data (that shuts everything down after computation is done) were all previously baked into the launch-template, so now we can leave the machine to do its thing.</p><h3>Learnings &amp; Drawbacks</h3><p>Overall this approach worked surprisingly well for us. The machines did their job and we didn’t have to worry about timeouts in that particular part of our processing pipeline anymore.</p><p>There are some drawbacks to this approach however:</p><p>Spin-up time is definitely larger. If a low response-delay is critical for your app, this might be a little bit too slow for you. At the same time this approach is hard to do when you need to actually pass down event data to the EC2 machine. In our case we just needed to run an aggregation that was scanning an entire S3 bucket anyways — so no runtime parameters needed in our case.</p><p>One annoying thing we learned is that user-data scripts are a real pain in the ass to debug. You constantly have to ssh into a machine and read logs to figure out why it didn’t work that time. Things like ECS task definitions are definitely much less headache-inducing. But once it worked, it worked flawlessly.</p><p>Pricing was actually no problem either. Since we’re shutting down the EC2 machines once they’re done, we were effectively still charged on a per-use basis (you’re still not paying for idle machine time). You want to make sure to always shutdown your development machines though — in our case we generated a pretty hefty bill by not noticing that we had 10x EC2 instances running over the weekend on our development system (we had disabled the shutdown command for debugging purposes).</p><h3>Lambda Functions with 11 TB RAM?</h3><p>So no, of course we didn’t find a magic hack to circumvent AWS Lambda restrictions to magically scale lambda functions beyond their computational limits.</p><p>But we did find a way to make an EC2 instance behave <em>sort of</em> like a lambda function: It only runs when invoked and shuts itself down after it’s done.</p><p>Overall this approach worked pretty well and comes without much setup. Once we had the user-data script nailed down it was a pretty minimalistic thing. No autoscaling, no load balancers, no ECS task definitions — just a simple EC2 launch template that was triggered by a lambda function.</p><p>And we could stick with our events-based serverless pipeline. Neat :)</p><p>— — — — — — —</p><h3>Thanks for reading!</h3><p>I’m Jonas and I work at <a href="https://career.axelspringer.com/en/tech">Axel Springer</a> — Europe’s largest publisher — where I’m uniting our 3000+ developers worldwide into one global Tech Community.</p><p><strong>If you liked this blogpost, feel free to clap 👏🏻 or share it on socials!</strong></p><p><a href="https://www.linkedin.com/in/aGuyNamedJonas/">https://www.linkedin.com/in/aGuyNamedJonas/</a><br><a href="/service/mailto:jonas.peeck@axelspringer.com">jonas.peeck@axelspringer.com</a></p><p>💼 <a href="https://career.axelspringer.com/en/tech">Check out our open positions in Tech</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e48a522c267b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/aws-lambda-functions-with-11tb-ram-yes-we-can-sort-of-e48a522c267b">AWS Lambda Functions with 11TB RAM? Yes we can! (sort of)</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you only Need 1 Rule to have Clean UI Code]]></title>
            <link>https://medium.com/@aGuyNamedJonas/why-you-only-need-1-rule-to-have-clean-ui-code-35bce5fde805?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/35bce5fde805</guid>
            <category><![CDATA[simplicity]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 02 Aug 2021 11:54:17 GMT</pubDate>
            <atom:updated>2021-08-26T11:58:30.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPRLMc7wI4R2OCZ3Lqjnaw.png" /></figure><h4>Start doing this today, and your frontend code will be much cleaner pretty soon</h4><p>I recently stumbled upon this <strong>simple rule</strong> that makes <strong>your frontend code </strong>much <strong>cleaner</strong>, <strong>easier to maintain</strong> and <strong>more fun to work with</strong>.</p><p>“Clean”, “easy to maintain”, “fun to work with” — the classic hallmarks of Clean Code. And in case you haven’t read <a href="https://www.amazon.de/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=sr_1_1?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=clean+code+english&amp;qid=1627887909&amp;sr=8-1">Robert C. Martin’s classic</a> and recognize the term — clean code is source code that’s written for humans.</p><p>More specifically: Clean Code is code that your teammates will be able to work with and not hate you for it. And as a side bonus, code that’s easy to work with tends to be better maintainable, more reusable and overall more hygienic as in less bug infested (aka “cleaner”).</p><p>So between React, Vue.js, legacy Handlebars projects or just plain old Vanilla JS, <strong>how can we ensure clean frontend code?</strong> Read on to find out…</p><h3>Component Driven Development (CDD)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*cML9RG7eN3vF9U3stc_f3w.png" /><figcaption>Graphics stolen from <a href="https://www.componentdriven.org/">componentdriven.org</a></figcaption></figure><p>To understand <em>The Rule</em>, we first have to take a look at the philosophy of <em>Component Driven Development</em>. The idea behind CDD is simple — you have different granularities of frontend components that together make up your app.</p><p>It’s a little bit like the <a href="https://martinfowler.com/articles/practical-test-pyramid.html#:~:text=The%20%22Test%20Pyramid%22%20is%20a,put%20it%20into%20practice%20properly.">testing pyramid</a> — a hierarchical system to think about structuring code in a way that different levels have different responsibilities:</p><p><strong>Components</strong> are the atoms of this hierarchy, the smallest unit. Components are small things like <em>Buttons,</em> <em>Tooltips, Inputs, Avatars.</em></p><p><strong>Fragments</strong> are a combination of components into composite structures like <em>Forms, Headers &amp; Toolbars.</em></p><p><strong>Pages </strong>are combinations of fragments into the pages that are served under the different routes of your app like the <em>Home page</em>, <em>Timeline page, Settings page, login / logout page</em>.</p><p><strong>Integration</strong> is the only place where you add business logic — everything before this point is made up of purely visual components with props or attributes &amp; event handlers. The integration part is where you add logic, network requests, API calls etc. This is where your <em>visual page components</em> turn into the fully fledged <em>web app, marketing landing site, documentation page </em>that you deliver to your users<em>.</em></p><blockquote>In Component Driven Development, <strong>even pages are treated as purely visual components</strong> that <strong>don’t have</strong> any business <strong>logic, network requests, or API calls</strong> in it. All the logic is added on top of the page-components.</blockquote><h3>💡 IDEA: What if we treat our pages as purely visual components, too?</h3><p>What’s so special about CDD is that pages are treated as <em>purely visual components</em>. And that’s a good thing — think about it:</p><p>Pages are typically the most messy parts of your complete app. Often you will find logic + visuals tested together making for bloated tests that mock gravity and space-time itself.</p><p>By treating pages as purely visual components &amp; adding the business logic and network requests on top you gain the following benefits:</p><ul><li>No mocks in (page) tests — just props &amp; event handlers ✅</li><li>It’s way easier to make pages responsive ✅</li><li>Amazing separation of concerns ✅</li></ul><p><strong>Downside:</strong> Yes you have to invest more work into building good abstractions (welcome to modern software development — first time?).</p><h3>Storybook</h3><p>The second thing we need, in order to understand <em>The Rule</em> is <a href="https://storybook.js.org/">Storybook</a>. If you are one of the 60.000+ people who starred Storybook on Github, just skip this section to get straight to <em>The Rule</em> 👇🏻</p><p>For anyone who doesn’t know Storybook — here’s a quick intro: Storybook is a gallery for your visual components:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*iZnRDFRripmSWdXPked-7Q.gif" /><figcaption>Storybook in action (Source: <a href="https://storybook.js.org/">https://storybook.js.org/</a>)</figcaption></figure><p>Storybook relies on only two things: Props (the “Controls” tab) and event handlers (the “Actions” tab).</p><p>For each of your visual components, you can define <em>stories </em>which are sets of props that storybook will set for your component (the <em>Histogram </em>story<em> </em>in this case<em> </em>displays the <em>Default, Empty, and Normalize</em> states).</p><p>As you can see from the gif above, the <em>states</em> are merely predefined prop values. Storybook makes it super easy to change the props interactively to see for yourself how this affects the component. This makes it super straight-forward to test edge behavior and get the details just right.</p><p>Oh and Storybook is super easy to setup!</p><blockquote>Add storybook to an existing CreateReactApp, Vue CLI or Ember CLI project:<br>$ npx sb init</blockquote><p><a href="https://storybook.js.org/docs/react/get-started/install">Web Components, Ember, HTML, Mithril, Marko, Svelte, Riot, Preact, and Rax are supported as well</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuPRbL38DweAmGbnUBjwHg.png" /><figcaption>The beauty of Storybook in one slide (Source: The <a href="https://www.youtube.com/watch?v=z39pYqGXisM">YouTube version of this blogpost</a>)</figcaption></figure><h3>The Rule</h3><p>With Storybook explained and CDD refreshed in your mind — here’s the rule.</p><p>Are you ready?</p><blockquote><strong>Everything that the user sees must be in your Storybook. <br></strong>The Rule</blockquote><p>Sounds simple enough — so why does that work to produce clean UI code?</p><p>If we assume that everything that we see in Storybook are purely visual components (yes you can get around that — exceptions prove the rule here) which only rely on props &amp; event handlers, then that means that everything we see in Storybook is automatically made up of side-effect free, pure functions (class style components acting like essentially pure functions if they only receive through props &amp; call back through events).</p><p>So if all of your app’s visual elements are side-effect free, pure functions — what do we get? A code base that’s a lot easier to test, maintain &amp; <strong>refactor</strong>.</p><p>Want to switch from REST API calls to GraphQL? Just swap out the part of the integration that fetches data. Want to swap out your state manager or switch away from one entirely? Just change the integration part that manages state. Want to change away from Material UI to a new brand identity? Gradually migrate out the components until it’s all shiny &amp; new (without having changed a bit in its functionality).</p><p>That’s the promise of clean code — you spend a little more time &amp; effort in the beginning, but become so much faster for it down the road.</p><p>And it gets better!</p><h3>Good for you + your team</h3><p>If you’re not yet convinced, here’s how this rule is good for your team overall:</p><p><strong>Benefit #1: Easy to commit to<br></strong>This rule is truly something the whole team can commit to. Storybook can be built &amp; hosted statically, so you can easily make it accessible to your designers, POs and curious DevOps team mates :)</p><p>Everyone can double check whether the visual elements they see on the app / in a ticket also appear in the Storybook — like that it’s easy to hold each other accountable.</p><p><strong>Benefit #2: One (visual) language for the whole team<br></strong>Raise your hand if had to fence off weird feature requests from your PO or esoteric ideas from your designers because they didn’t work with the components you already have?</p><p>Storybook changes that. Got a request that re-invents the wheel? Gently nudge your team mate to the storybook and ask them to reuse what you already have as much as possible.</p><p><strong>Benefit #3: You’re freed up to focus on details (again)<br></strong>Because storybook makes it easy to develop the <em>visual</em> aspects in isolation, you can afford to take care of details again. Building a new feature and had to make a few tradeoffs between what your designer wanted and what you could build? Just show them — even before any business logic is implemented.</p><p>Shorter feedback cycles between frontend &amp; design are always a plus for the overall user experience.</p><p><strong>Benefit #4: Bring your own style</strong><br>No more discussions about class-style vs. functional-style components in React! Everybody (in theory) can bring their own style because at the end of the day, if it only relies on props &amp; event handlers, how bad can it be?</p><p>That’s exactly the point of good abstraction — it shouldn’t matter what happens behind the interface.</p><p><strong>Benefit #5: Easier Onboarding<br></strong>Last on the list, definitely not the least important one in here. Whether you’re onboarding new developers to the team, or getting a junior dev started — in both cases it’s a breeze.</p><p>New team members can really quickly figure out how everything works (due to the clean separation between business logic &amp; visuals), juniors have a very limited blast radius in what they can break and don’t have to implement everything all at once.</p><p>They can focus on just the visuals and then focus on just the business logic — or vice versa. That’s a win for anyone you’re onboarding, regardless of their skill level.</p><h3>Final Thoughts</h3><p>I can’t say whether this is the rule to end all rules when it comes to clean UI code. Your team might have individual needs for rules that help you do your best work. What I was blown away by is just how simple this rule is and how realistic it is to commit to this as a team.</p><p>Start doing this today, and your frontend code will be much cleaner pretty soon.</p><p>And no, you don’t have to refactor your complete codebase over a new tool in your belt. Just apply the Scout’s rule: Leave the campsite better than you found it — or rather leave the Storybook fuller than you found it.</p><p>— — — — — — —</p><h4><strong>Thanks for reading!</strong></h4><p>I’m Jonas and I work at <a href="https://career.axelspringer.com/en/tech">Axel Springer</a> — Europe’s largest publisher —where I’m uniting our 3000+ developers worldwide into one global Tech Community.</p><p><strong>If you liked this blogpost, feel free to clap 👏🏻 or share it on socials!</strong></p><p>If you want <strong>to get in touch</strong> or would <strong>like me to give this talk at your company or team</strong>, feel free to reach out:</p><p><a href="https://www.linkedin.com/in/aGuyNamedJonas/">https://www.linkedin.com/in/aGuyNamedJonas/</a><br><a href="/service/mailto:jonas.peeck@axelspringer.com">jonas.peeck@axelspringer.com</a></p><p>💼 <a href="https://career.axelspringer.com/en/tech">Check out our open positions in Tech</a></p><p><strong>TL;DR (too lazy ;) didn’t read):</strong> <br>You can also watch me give the talk this blogpost was based on 👇🏻</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fz39pYqGXisM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dz39pYqGXisM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fz39pYqGXisM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb75b48431ab3cef650ea49f4e24ce36/href">https://medium.com/media/fb75b48431ab3cef650ea49f4e24ce36/href</a></iframe><p>Jump to <a href="https://youtu.be/z39pYqGXisM?t=570">[09m:30s] for a quick demo of Storybook</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35bce5fde805" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[⚡️Can't find the right DB? Just build one!]]></title>
            <link>https://medium.com/axel-springer-tech/%EF%B8%8Fcant-find-the-right-db-just-build-one-c20486fc9528?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20486fc9528</guid>
            <category><![CDATA[custom]]></category>
            <category><![CDATA[realtime]]></category>
            <category><![CDATA[embedded-systems]]></category>
            <category><![CDATA[in-memory-database]]></category>
            <category><![CDATA[paywall]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 22 Feb 2021 08:47:27 GMT</pubDate>
            <atom:updated>2021-02-22T08:47:27.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIYuAeLV0cpV8ZVLaMmxCw.png" /></figure><h4>CeleraOne builds server-side rendered paywalls — powered by a custom DB + a custom programming language!</h4><p><a href="https://celeraone.com/de/"><em>CeleraOne</em></a><em> build server-side rendered paywalls for digital publishers. As a part of the Axel Springer Group, it’s also a member of the Global Axel Springer Developer Community.</em></p><p>Even as a software developer it&#39;s not everyday that you talk to someone who genuinely builds their own low-level technologies — especially not high-performance tech like a realtime streaming in-memory database that serves millions of requests every day.</p><p>That&#39;s why when I first heard that CeleraOne had built a custom in-memory database, I got curious. As it turns out, it&#39;s even crazier than I thought — they even built their own programming language, to allow their customers to define programs that act as elaborate database requests which can customize the offers website visitors are being presented with.</p><p>But I&#39;m getting ahead of myself.<br>Let&#39;s start at the beginning.</p><h3>&quot;Fighting for every bit&quot;</h3><p>Christoph’s job can be summarised in one sentence: He’s fighting “for every bit” as he puts it, being the Lead Developer for the custom database technology at CeleraOne.</p><p>CeleraOne offers server-side rendered paywalls to news-websites which decide in realtime, whether a website visitor is a subscriber, and if not which offer is most likely going to make them a subscriber. <em>Server-side rendering</em> to avoid Ad-blockers from circumventing it, <em>realtime</em> because increased page-load times also increase the bounce-rates, and <em>custom offers</em> because newspapers desperately need every paying subscriber that they can get.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vtPhQnTYveaMjQre03BGiQ.png" /><figcaption>The CeleraOne architecture: It&#39;s essentially a middleware between website visitors (left) and the publisher&#39;s content (right)</figcaption></figure><p>The system is shipped in custom-fitted, physical machines that have hundreds of Gigabytes of RAM inside, running their proprietary in-memory streaming database. This puts Christoph and his team in an unusual situation for a web technology team: If they run out of RAM, that&#39;s it. They have no auto-scaling to save them.</p><p>So they fight for every bit. &quot;Database as a library&quot; as Christoph calls it — whenever new datatypes are needed to model rulesets around user behavior, the database is recompiled. A customer needs to define rules around certain website domains? Then those domains are baked into the database through a lookup table whose index has just as many bits as it needs. Only storing 3 URLs in that table? Then the index is going to have 4 bit addresses.</p><h3>COPL — the friendly, custom programming language</h3><p>Christoph has a doctorate in compiler construction and worked at the TU Berlin until 2017, so it&#39;s not too surprising that a custom programming language is hustling away inside CeleraOne&#39;s database (even though to be fair the custom language was already there when he joined).</p><p>He admits that the decision to develop a custom programming language for their custom database at first doesn&#39;t make much sense when you think about it from a business perspective. But that&#39;s only because it&#39;s a little hard to explain why a custom language is needed in this case.</p><p>With the database running in-memory to deliver realtime performance, any program that would want to interact with that data needs to run in the same process. That in turn means that any faulty program can not only corrupt data, but also crash the complete system with a memory error.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpXvu_Z1GiMV1oBPvzm1fA.png" /><figcaption>COPL in action — here it’s evaluating whether a customer has a “One Day Pass” or not</figcaption></figure><p>With the danger of a complete system crash, a custom programming language suddenly does make a whole lot of sense. It allows Christoph and his team to provide customers with just enough power to construct elusive rulesets (e.g. granting unsubscribed users 5 free articles per month, offering special soccer subscriptions for people who seem to like sports etc.) while being able to maintain the safety of the system — which is critical for newspapers to get paid.</p><p>The custom programming language is called COPL (CeleraOne Programming Language) and is a statically typed, functional programming language which compiles to machine code (for obvious performance reasons) and — since it’s a custom language running in the same process as the DB — can directly manipulate in-memory values of the CeleraOne database.</p><p>It&#39;s hard to tell at first glance that COPL is a custom programming language though. The language itself is very well readable, and is offered up to users in a clean looking online editor that features syntax highlighting and lets users test rules, before activating them for live traffic.</p><h3>What about Rust though?</h3><p><a href="https://insights.stackoverflow.com/survey/2020#most-loved-dreaded-and-wanted">As the most loved programming language of 2020</a>, that is both type-safe and compiles to machine code (the two requirements for the team) I had to ask though: Why not use Rust, instead of COPL —as their embedded programming language?</p><p>The answer dumbfounded me a bit.</p><p>If they were to use Rust, it would essentially create the reverse problem of what programming languages usually struggle with. If normally the typical complaint about a language might be that its standard library is too constrained (&quot;It would be so cool if language X had this feature I love from language Y&quot;), CeleraOne&#39;s COPL faces the opposite problem: If Christoph and the team can&#39;t control the standard library, they can&#39;t ensure the safety of the overall system.</p><p>Christoph explains it like this: They used to support calling C functions from COPL, but after a while realised that it&#39;s too risky and needed to be rolled back. With any other programming language (e.g. Rust) it would have been pretty difficult to <em>remove</em> parts of the language features. Since the team is dealing with their own language though, they simply had to change 30 lines of code and recompile. Pretty elegant.</p><p>Overall I went out of this interview, being incredibly impressed. With my background as a JavaScript developer, I&#39;m from the opposite side of the spectrum it seems. I don&#39;t even remember what byte-length the different variable types have in JavaScript, because generally I don&#39;t have to.</p><p>While Christoph and his team are fighting for every single bit, in my world I was more concerned with, for example, uploading gigantic MP4 video files reliably via a web uploader, making sure that even on a shaky wifi connection uploads of the individual file parts were retried in case there was a network problem. I wasn&#39;t &quot;fighting for bits&quot; — I was rather throwing bits at the problem, until it was solved.</p><p>And yet, Christoph&#39;s story is just such a cool reminder that at the end of the day, being a developer means you can build anything.</p><p>Literally anything — even a custom realtime in-memory streaming database for millions of requests with its own programming language, named COPL.</p><p>—</p><p><a href="https://github.com/choeger">Connect with Christoph on Github</a></p><p><strong>💼 Curious about working at CeleraOne?</strong><br><a href="https://celeraone.com/de/karriere/">Check out our open positions</a></p><p>— — — — — — — —</p><p>Hi, I’m Jonas and I’m currently building up a <strong><em>Global Axel Springer Developer Community</em></strong>. S<strong>ubscribe to our Weekly Tech Newsletter</strong> to get a fresh story like this <em>every Monday</em> and to receive details on how you can join our global developer community ✌🏻</p><p>Want me to help tell your story? Reach out to me 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-10-19">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-10-19">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*VX7Y4COFCbIR6oJRFvgeFw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20486fc9528" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/%EF%B8%8Fcant-find-the-right-db-just-build-one-c20486fc9528">⚡️Can&#39;t find the right DB? Just build one!</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ INNOVATE LIKE THE VALLEY]]></title>
            <link>https://medium.com/axel-springer-tech/innovate-like-the-valley-61b730aea216?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/61b730aea216</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[axel-springer]]></category>
            <category><![CDATA[ideation-council]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 08 Feb 2021 11:44:31 GMT</pubDate>
            <atom:updated>2021-02-08T11:44:31.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1eQbmOSIUGZYd0Nl-JIiDg.gif" /></figure><h4>Meet the Axel Springer Ideation Council</h4><p><a href="https://www.ideas-engineering.io/"><em>Ideas Engineering</em></a><em> is our version of Disney’s Imagineering division — a team highly specialised on bringing the future of Tech to Axel Springer through innovative prototypes. As a part of the Axel Springer Group, it’s also a member of the Global Axel Springer Developer Community.</em></p><p>When Alexandra &quot;Alex&quot; Nicolae arrived (Ideas Engineering, Berlin) in San Fransisco a year ago, she only wanted to find the answer to one simple question:</p><p>How does the Silicon Valley go from idea to finished-product?</p><p>About as hard as finding a tiny room in a shared apartment anywhere in San Fransisco, answers to her question were almost impossible to find at first. She had 2 months to get to the bottom of how the Valley does innovation, and so far it had been 2 weeks and nothing but closed doors.</p><p>Alex was desperate.</p><p>Until she caught a break through of the undercurrent of opportunities, seemingly favouring the determined, running below the startup mecca of the world — the mystical mix of perseverance and luck finally catching her adrift in a wave of follow-up referrals. She ended up with over 40 interviews at Google, Amazon, Facebook and Apple — picking the brains of the top tech companies in the Silicon Valley about how to do innovation at scale.</p><p>Armed with the knowledge of how the best in the world drive innovation, she returned home to Berlin — launching the <a href="https://www.ideationcouncil.axelspringer.de/">Axel Springer Ideation Council</a>.</p><h3>See your ideas realised at Axel Springer</h3><p>The Ideation Council, is the conceptual brainchild of years of experience in prototyping ideas into ready-to-use-products at Axel Springer Ideas Engineering mixed with Alex&#39; insights from the Silicon Valley.</p><p>The goal of the Ideation Council is simple: Allow anyone from the global family of companies that belong to Axel Springer to submit an idea and pitch them in front of panel that includes at least one board member.</p><p>Ideas can be submitted through a publicly available website by everyone at the Axel Springer Group: <a href="https://www.ideationcouncil.axelspringer.de/">ideationcouncil.axelspringer.com</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhUPFqxXGm-Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhUPFqxXGm-Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhUPFqxXGm-Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7f650806c58f7dcd9be97dca8b135588/href">https://medium.com/media/7f650806c58f7dcd9be97dca8b135588/href</a></iframe><p><a href="https://www.ideationcouncil.axelspringer.de/pitch-your-idea">To get an idea into the Ideation Council</a>, the submitter simply has to fill in <a href="https://www.quora.com/What-is-Amazons-approach-to-product-development-and-product-management?ref=http://www.product-frameworks.com/">Amazon&#39;s legendary press release template</a> — &quot;working backwards&quot; from what the final product might look like to potential users.</p><p>If anyone is unsure about the pitch, they can optionally also <a href="https://www.ideationcouncil.axelspringer.de/contact">get in touch with Alex</a> for a quick chat before submitting their idea.</p><h3>Inspiration, Information, Impediment, Impact — 4Is in 3 Minutes</h3><p>Once submitted, the idea is refined through conversations with Alex herself. What&#39;s interesting in this case is that the FAQ section of the Amazon Product Template is assembled in this step: Alex and another team mate from the Ideation Council Team ask the kind of questions that the jury members might ask, to help refine the concept and make the idea rock-solid.</p><p>Members of the Ideation Council Team includes a heavy-weight innovation lineup from the Axel Springer universe — next to <a href="https://www.linkedin.com/in/alexandrairinanicolae/"><strong>Alex</strong> (Product Owner at Ideas Engineering)</a>, <a href="https://www.linkedin.com/in/henrike-hedel"><strong>Henrike Hedel</strong> (Strategic Innovation Manager at Ideas Enginnering)</a>, <a href="https://www.linkedin.com/in/bente-z/"><strong>Bente Zerrahn</strong> (Innovation Catalyst at Axel Springer)</a> and <a href="https://www.linkedin.com/in/mcalber/"><strong>Michael Alber</strong> (COO of Ideas Engineering)</a> help bring the website submissions into a pitch-ready form.</p><p>Next, the refined product template is turned into a 3 minute pitch, covering 4Is — documenting what the inspiration for the idea was, which <em>information</em> the submitter can provide as research, what <em>impediment(s)</em> are currently stopping us from building it, and what the <em>impact</em> of the idea on Axel Springer would be:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WL6w1qUuPr8Gh7BCWEyeVg.png" /></figure><p>After that it&#39;s off to the next Ideation Council session, where votes are cast by the Ideation Council team members and by one of our board members.</p><h3>Launching the pitch into the stratosphere</h3><p>After a pitch has been chosen for implementation from the council meeting, two special teams at <a href="https://www.ideas-engineering.io/">Axel Springer Ideas Engineering</a> — Team X and Team POV (name is a WIP)— go into high-gear, building either a prototype (1 week) or even a proof of value (1 month), in order to validate the hypothesis that the pitch is based on.</p><p>A while ago, we talked to <a href="https://www.linkedin.com/in/martin-bild-96903619/">Martin Bild (Project Lead Innovation &amp; Strategy at Ideas Engineering)</a> about how Ideas Engineering does Innovation, and it turns out that the Ideation Council builds on a long legacy of prototype-driven innovation at Ideas Engineering. For years the teams that Martin Bild works with, have been part of an innovation process where everyone from the company was asked to rate ideas for prototypes on a scale of 1–10 in &quot;Awesomeness&quot;, which then lead to the funnel leaders being built into 1–week Proof of Concepts, or 1–month Proof of Value prototypes.</p><p>Building innovative prototypes has been part of the Ideas Engineering (the Axel Springer version of the legendary <a href="https://disneyimaginations.com/">Imagineering Division at Disney</a>) for years.</p><p>The only difference now is that the ideas funnel has been opened to everyone inside the Global Axel Springer Family through the Ideation Council.</p><h3>How to: Innovate like the Valley</h3><p>Simple things are hard to get right — the Ideation Council seems to have the recipe just right though— if you want to build up your own innovation process at your company / corporation, the following learnings from talking to Alex might help:</p><ol><li><strong>Get buy-in from the board / top-management</strong> — It&#39;s both a motivation and a challenge to pitch at that flight-level. Plus ideas stand a real chance at being seen through to completion with the right backing</li><li><strong>Find a team of volunteers who help refine pitches</strong> — In every team there&#39;s people who get excited by fresh ideas. Get these people to help refine the pitches with passion &amp; curiosity</li><li><strong>Make it as easy as possible to submit ideas </strong>— The website for the Axel Springer Ideation Council is publicly available so nobody has to go sifting through our various (non-connected) intranets to find it. It&#39;s a simple Squarespace site — anyone could set that up!</li><li><strong>Dedicate a team to implementing the ideas</strong> — The Ideation Council builds on top of the legacy and experience of Team X that has been specialised on building prototypes for years. Don&#39;t let good ideas die — dedicate people &amp; money to bring those ideas to life before you start accepting pitches</li><li><strong>Follow up with the ideas </strong>—Prototypes &amp; Proof of Values often die a premature death in corporations. Make sure the board-member-studded jury that evaluates pitches also follows-up with past implementations. Use the buy-in from step one to make sure your innovative prototypes get a fair chance at life!</li></ol><p>For Alex it has to feel like life has come full circle.</p><p>Years ago, she switched away from a path towards becoming a teacher to instead join the tech-sector. She believed that she could help bring about change faster through working at tech-companies than by trying to convince teenagers to do the right thing.</p><p>Now that change is right at her fingertips — and in everyone&#39;s reach at Axel Springer.</p><p><a href="https://www.ideationcouncil.axelspringer.de/"><strong>Pitch your idea to the Ideation Council, if you haven&#39;t already.</strong><br></a>Or <a href="https://www.linkedin.com/in/alexandrairinanicolae/">get in touch with Alex</a>, if you&#39;re looking for inspiration to setup your own Ideation Council.</p><p><a href="https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=national+media+and+tech&amp;id=65&amp;tx_kesearch_pi1%5Bpage%5D=1&amp;tx_kesearch_pi1%5BresetFilters%5D=0&amp;tx_kesearch_pi1%5BsortByField%5D=score&amp;tx_kesearch_pi1%5BsortByDir%5D=desc">Connect with Alex on LinkedIn</a></p><p><strong>💼 Curious about working at Ideas Engineering?<br></strong>👉🏻 <a href="https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=yad2&amp;id=65&amp;tx_kesearch_pi1%5Bpage%5D=1&amp;tx_kesearch_pi1%5BresetFilters%5D=0&amp;tx_kesearch_pi1%5BsortByField%5D=&amp;tx_kesearch_pi1%5BsortByDir%5D=asc&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B511%5D=taetigkeitsbereich_data-science&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B473%5D=taetigkeitsbereich_it&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B497%5D=taetigkeitsbereich_produktmanagement">Check out our open positions</a></p><p>— — —</p><p>Hi, I’m Jonas and I’m currently building up a <strong><em>Global Axel Springer Developer Community</em></strong>. S<strong>ubscribe to our Weekly Tech Newsletter</strong> to get a fresh story like this <em>every Monday</em> and to receive details on how you can join our global developer community ✌🏻</p><p>Want me to help tell your story? Reach out to me 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-10-19">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-10-19">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_NpOEoje2fBnSzMaoj_mQA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61b730aea216" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/innovate-like-the-valley-61b730aea216">🔥 INNOVATE LIKE THE VALLEY</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buddy-System for Developers]]></title>
            <link>https://medium.com/axel-springer-tech/buddy-system-for-developers-b97611a28435?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/b97611a28435</guid>
            <category><![CDATA[team-culture]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 07 Dec 2020 13:33:37 GMT</pubDate>
            <atom:updated>2020-12-15T11:31:52.666Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PUGaRCsqwcE9gi7jhq9m6w.jpeg" /><figcaption>Picture by <a href="https://unsplash.com/@kaleidico">Kaleidico</a> on <a href="https://unsplash.com/photos/3V8xo5Gbusk">Unsplash</a></figcaption></figure><h4>Team flexibility &amp; P2P training at Yad2 in TelAviv</h4><p><a href="https://www.yad2.co.il/"><em>Yad2</em></a><em> is one of Israel’s classifieds portal. As a part of the Axel Springer Group, it’s also a member of the Global Axel Springer Developer Community.</em></p><p>“I’m bored” Anna told her boss, Mati — straight up. No sugarcoating, no polite ways to make it less blunt, just a truth she was so honest with herself about, it seemed to be absolutely no problem to her to admit that to her team-lead as well.</p><p>I was shocked. But to Mati it was great that she was being so direct:<br>“Either she gets help with the boredom, or she leaves — so it’s good that she told me”. Alright that’s actually pretty smart. Still shockingly honest from what I’m used to.</p><p>And then the solution: They made a deal that Anna trained somebody else for 2 months to do her job, and then she could leave to do another project. Just like that.</p><p>Welcome to the Yad2 buddy system!</p><p>TelAviv seems to make for interesting biographies. While Mati and Anna both come from completely different backgrounds, today they’re one team working at Yad2 — Israel’s best place online to find good deals on electronics, cars, insurances, and most importantly: Apartments &amp; houses.</p><p>Anna actually grew up in Russia where earned a Masters degree in Political Science and worked as a market researcher, before moving to Israel and working at Yad2 after completing a 3 month / 10 hour per day coding bootcamp.<br>Mati grew up in Israel, where he was a commander during the mandatory military service, founded and sold a company after college, and eventually started at Yad2, where is now the team-lead of one of the biggest teams — the real-estate team.</p><h3>cp Anna/MapboxSkills TwoOther/Developers</h3><p>When Anna approached Mati about wanting to jump into new adventures one of the biggest hurdles was that Anna was the internal “map wizard”, having built their Vue based frontend around the Mapbox API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1J8h6n70sEu43Y93ETyzw.png" /><figcaption>Slides from Anna, explaining how the Map frontend works</figcaption></figure><p>Anna had a great idea about improving an aspect of the backend to better perform when queried by the UI. But before she could switch into the backend team for a while, acting more in a role of an architect, she first had to find a replacement. She was more or less the only person with in-depth knowledge about the implementation of the Maps in the frontend.</p><p>Three months ago, maps on Mobile were supposed to be launched as a feature — and the choice about who would implement it, could have been easy: Just give it to the person who already knows how to do this stuff — Anna. Instead, the buddy system of Mati’s team kicked in, and two other developers were trained by Anna instead.</p><blockquote>“When you’re doing new things, you usually take 3x as long — in this case we actually delivered 10 days early” (Anna)</blockquote><p>Usually you would think that putting new people in charge will cause you to miss all sorts of deadlines — in this case however it actually made them deliver 10 days ahead of schedule.</p><h3>A tough place to be flexible in — theoretically</h3><p>For Mati the buddy system is essential. And that’s a little surprising to hear, because his job doesn’t exactly sound stress-free as is: Their team helps build the tools for the real-estate division which makes up 2/3 of the company’s revenues. Their requirements and timetables are very sales-driven, with a lot of pressure to deliver &amp; perform — usually not the kind of place to be flexible in.</p><p>“The ability to reshuffle the team is much more agile”, Mati points out though. His developers will come to him and “want something else” as he puts it — and with the buddy system he can provide that flexibility.</p><p>On top of that, the team grew recently — with a lot of new Junior developers coming in. This can be a breaking point for some companies. Training juniors is hard work and takes a special kind of people. But if the whole organization routinely trains people on new skills &amp; technologies, training junior developers is something everybody’s used to.</p><p>As a wise colleague of mine once said: <br>Everybody’s a junior developer in something.</p><h3>Being a successful mentor</h3><p>So how do you become a successful mentor when teaching others your skills?</p><p><strong>#1 It starts with the team lead</strong>: Yes, training takes more time initially, and yet Yad2 was able to deliver 10 days ahead of schedule. Why? Because they put 2 developers into training, not just one. The initial slowdown was both expected and encouraged. There was a clear understanding of the benefits.<br>If that’s not the case with your team-lead, the model will break down.</p><p><strong>#2 Driver seat from Day 1:</strong> Another success factor is putting your trainees into the driver seat from day 1. Learning-by-Doing in its simplest form. Let the person doing the learning also do the coding. They will learn a lot faster when they’re responsible for delivering, not just forced to sit back and listen for hours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tGrltxrxItEvqJn8g0fNjQ.png" /><figcaption>Explaining a technical system like it’s a cast of protagonists in a storyline — Anna’s slides look like they definitely helped get the point across :)</figcaption></figure><p><strong>#3 Mentee needs to be interested:</strong> This so obvious, it has to be mentioned so nobody forgets to think about this. There’s no point in teaching someone who’s not interested. For this system to work, the trainee <em>really</em> has to be interested in what you’re teaching them.</p><p><strong>#4 Be ready to help at any time:</strong> Anna admits, it has been “kind of hard to make time” for her trainees sometimes. But that’s what it takes to successfully train someone new. Be ready to jump in and help at any time. And keep in mind proper training will take a few months to complete. Only when you put in the work, can you expect great results.</p><p>Lastly it might be worth pointing out that Mati of course did not invent this system. He says it’s actually pretty common in the Israeli tech scence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZ-XX8xdpD9oqDOpB5FH1Q.jpeg" /><figcaption><strong>From left to right: </strong>Amos Kasha (Fullstack Dev), Ben Golan (Product Manager), Yuval Gal (Fullstack Dev), Yuval Shafat (Product Manager), Assaf Farhan (Fullstack Dev), Mati Konen (Team Lead), Shir Yarden (Product Manager), Anna Weinmacher (Fullstack Dev)</figcaption></figure><p>It’s still very impressive to see how well the team(s) at Yad2 have used such a peer-to-peer system to train old and new developers for new skills &amp; technologies.</p><p>If you want to implement this system at your team as well, feel free to connect to the two 👇🏻</p><p><a href="https://www.linkedin.com/in/mati-konen-117416145/">Mati on LinkedIn</a><br><a href="https://www.linkedin.com/in/aweinmacher/">Anna on LinkedIn</a></p><p><strong>💼 Curious about working at Yad2?<br></strong>👉🏻 <a href="https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=yad2&amp;id=65&amp;tx_kesearch_pi1%5Bpage%5D=1&amp;tx_kesearch_pi1%5BresetFilters%5D=0&amp;tx_kesearch_pi1%5BsortByField%5D=&amp;tx_kesearch_pi1%5BsortByDir%5D=asc&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B511%5D=taetigkeitsbereich_data-science&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B473%5D=taetigkeitsbereich_it&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B497%5D=taetigkeitsbereich_produktmanagement">Check out our open positions</a></p><p>— — —</p><p>Hi, I’m Jonas and I’m currently building up a <strong><em>Global Axel Springer Developer Community</em></strong>. S<strong>ubscribe to our Weekly Tech Newsletter</strong> to get a fresh story like this <em>every Monday</em> and to receive details on how you can join our global developer community ✌🏻</p><p>Want me to help tell your story? Reach out to me 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-10-19">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-10-19">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_NpOEoje2fBnSzMaoj_mQA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b97611a28435" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/buddy-system-for-developers-b97611a28435">Buddy-System for Developers</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TechCon 2020 is here ]]></title>
            <link>https://medium.com/axel-springer-tech/techcon-2020-is-here-6e36392ef45c?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e36392ef45c</guid>
            <category><![CDATA[virtual]]></category>
            <category><![CDATA[axel-springer]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[2020]]></category>
            <category><![CDATA[tech-conference]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 09 Nov 2020 11:23:46 GMT</pubDate>
            <atom:updated>2020-11-09T15:47:45.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyKT5r8FUtsMNRt6Cd3Tyw.png" /></figure><h4>Our very own Axel Springer Tech Conference returns Nov 25/26 — virtually of course</h4><blockquote>TechCon 2020 is an internal Tech Conference where tech &amp; product people from all over the Axel Springer Group meet for presentations, discussions, and workshops.</blockquote><p><a href="https://event.axelspringer.com/techcon2020"><strong>Signup for TechCon 2020 now!</strong></a></p><p>TechCon 2019 was a huge success and a ton of fun. 600 tech &amp; product people from all over the Axel Springer Group under one roof.</p><p>600 people under one roof. Not having to wear masks. Being able to just mix &amp; mingle in each other’s company. The good old times of 12 months ago feel like a distant dream.</p><p>Luckily we can all get together again this year to escape the confines of our home-offices — meet the virtual TechCon 2020!</p><p>And yes, TechCon 2020 is an internal event, only for employees of Axel Springer Companies. But don’t fret — this is just <a href="https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=&amp;id=65&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B511%5D=taetigkeitsbereich_data-science&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B473%5D=taetigkeitsbereich_it&amp;tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B497%5D=taetigkeitsbereich_produktmanagement&amp;tx_kesearch_pi1%5Bpage%5D=1&amp;tx_kesearch_pi1%5BresetFilters%5D=0&amp;tx_kesearch_pi1%5BsortByField%5D=&amp;tx_kesearch_pi1%5BsortByDir%5D=">another great reason to join us :)</a> And it hopefully serves as an inspiration to other tech-companies that magical things happen when you create dedicated events for your tech-hoardes to mingle, meet and share their knowledge with each other.</p><h3>AI connecting attendees with each other</h3><p>Daniela Voss &amp; Madeline “Madi” Schalk of the <a href="https://medium.com/axel-springer-tech/virtual-events-scale-better-e271cfcde0d4">Knowledge Network Team</a> looked at roughly 30 different virtual conferencing tools, before settling on one that Daniela had experienced at a physical conference before — a conferencing platform with AI based attendee-matching, called <a href="https://grip.events/">grip</a>.</p><p>Both of them are incredibly excited about this. “In physical conferences you always had to stare at name tags in a really awkward way before finding out where people work” Daniela explains the usual conundrum of conferencing.</p><h3>Taking the awkwardness out of networking</h3><p>With <a href="https://grip.events/"><em>Grip</em></a> that’s a thing of the past.<br>Attendees of the TechCon 2020 initially specify their area of expertise and what they would like to learn about. The system then also considers which events everyone added to their schedules.</p><p>The awkwardness is completely taken out of networking — because the system makes the introductions based on what the AI thinks might make for interesting 1:1 conversations. If both attendees accept the match, they can exchange messages &amp; arrange a meeting. All from within the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HzS9v4m5sWyLhC0F-KGuLA.png" /><figcaption>Virtual Conferencing at its finest — a pre-render of what the grip UI will look like for the Axel Springer TechCon 2020</figcaption></figure><h3>A Conference for the People &amp; By the People</h3><p>One of the main goals of this virtual edition of the conference was to retain the human connections — usually one of the main benefits of attending physical conferences. New connections should be able to form, old aquaintances should be refreshed, and intros should be made.</p><p>All of that is handled by the AI this year.</p><p>What hasn’t changed though is the P2P learning as the main focus. <br><em>Data &amp; AI</em>, <em>Innovation</em>, <em>Development</em>, <em>DevOps</em>, <em>Product</em>, <em>Tech &amp; Stories</em> are among the topics for this year’s conference — and as always everybody is <a href="/service/mailto:7c2b5a00.moveoffice.com@emea.teams.ms%5BTechCon2020%20Talk%20Submission%5DTitle%20of%20talk%3A%20%3CPlease%20insert%20your%20talk%20title%20here%3E%0D%0ADescription%3A%20%3CPlease%20insert%20a%20description%20here%3E%0D%0APresenters%3A%20%3CPlease%20insert%20all%20presenters%20with%20their%20email%20addresses%20here%3E%0D%0ATopics%3A%20%3CPlease%20insert%201-3%20topics%20that%20best%20categorize%20your%20talk%3E%0D%0A%0D%0AFeel%20free%20to%20add%20any%20additional%20infos!">more than welcome to submit talks</a>.</p><h3>Our keynote speaker: Dr. Vivienne Ming</h3><p>Next to homegrown presentations, workshops &amp; talks, the lineup this year also includes our keynote speaker <a href="https://twitter.com/neuraltheory">Dr. Vivienne Ming </a>— theoretical neuroscientist, serial entrepreneur, <a href="https://www.youtube.com/watch?v=5-aIq4cRlss">TED speaker</a> and <a href="https://www.designindaba.com/articles/creative-work/how-two-researchers-hacked-software-create-functional-ai-their-diabetic-son">creator of an AI that tracks her son’s diabetes</a> whose work has been featured in <em>The Financial Times</em>, <em>The Atlantic</em>, <em>Quartz Magazine</em>, and the <em>New York Times</em>.</p><p>TechCon 2020 is here and it will be a blast — for the whole Axel Springer Tech Family.</p><p>If you work for an Axel Springer Company<strong>, Register now</strong> 👇🏻 and <a href="https://axelspringertech.com/newsletter"><strong>subscribe to the weekly TechNewsletter</strong></a> for updates!</p><ul><li><a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksRegisterTechConLink&amp;url=https://event.axelspringer.com/techcon2020&amp;sourceId=tech-blog-2020-11-09">Register for the Axel Springer TechCon 2020</a></li><li><a href="https://webhooks.axelspringertech.com/resolve?eventType=UserSubmitsTechConTalk&amp;url=mailto:7c2b5a00.moveoffice.com@emea.teams.ms?subject=%5BTechCon2020%20Talk%20Submission%5D%26body=Title%20of%20talk%3A%20%3CPlease%20insert%20your%20talk%20title%20here%3E%0D%0ADescription%3A%20%3CPlease%20insert%20a%20description%20here%3E%0D%0APresenters%3A%20%3CPlease%20insert%20all%20presenters%20with%20their%20email%20addresses%20here%3E%0D%0ATopics%3A%20%3CPlease%20insert%201-3%20topics%20that%20best%20categorize%20your%20talk%3E%0D%0A%0D%0AFeel%20free%20to%20add%20any%20additional%20infos%20that%20might%20be%20important%20here.&amp;sourceId=tech-blog-2020-11-09">Submit a talk</a></li><li><a href="https://axelspringertech.com/newsletter">Subscribe to the weekly Axel Springer TechNewsletter</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O36ybkxKV1i2msnaQyXJyQ.jpeg" /></figure><p>— — —</p><p>Hi, we’re <a href="https://www.linkedin.com/in/jonaspeeck/">Jonas</a> &amp; <a href="https://www.linkedin.com/in/anna-peeck-6745ab84/">Anna</a> and we’re currently building up a <strong><em>Global Axel Springer Developer Community</em></strong><em>.</em> <strong>Subscribe to our Weekly Tech Newsletter</strong> and reach out to us, if you like us to help tell your story 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-09-28">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-09-28">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Kr3KwsX8Igi7z8vXphseQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e36392ef45c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/techcon-2020-is-here-6e36392ef45c">TechCon 2020 is here 🙌🏻</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the man who helped bring the General Public License (GPL) into German Law]]></title>
            <link>https://medium.com/axel-springer-tech/meet-the-man-who-helped-bring-the-general-public-license-gpl-into-german-law-c984433221cd?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/c984433221cd</guid>
            <category><![CDATA[software-licensing]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[gplv3]]></category>
            <category><![CDATA[tech-history]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 19 Oct 2020 07:45:07 GMT</pubDate>
            <atom:updated>2020-10-19T09:56:01.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xXHPae3U2dg5he8-29eXqA.png" /><figcaption>Logo of the GPLv3 on top of the preamble of the popular Open Source License (<a href="https://de.wikipedia.org/wiki/GNU_General_Public_License#/media/Datei:GPLv3_Logo.svg">Logo source</a>, <a href="https://www.gnu.org/licenses/gpl-3.0.de.html">Text source</a>)</figcaption></figure><h4>Bringing Open Source licensing to Germany in the late 90s</h4><p><a href="https://www.upday.com/en/"><em>Upday</em></a><em> curates news for millions of Android users everyday and comes preinstalled on Samsung phones. As a part of the Axel Springer Group, it’s also a member of the Global Axel Springer Developer Community.</em></p><p>When Olaf Koglin and his comrades helped establish the <a href="https://de.wikipedia.org/wiki/Linux-Klausel">“Linux clause”</a> in German copyright law in the early 2000s, the rebels of the Open Source Movement still had a clear nemesis: The Microsoft Corporation.</p><p>It was the time when <a href="https://en.wikipedia.org/wiki/Pieing#Political_acts">Bill Gates was caked</a> and was generally regarded as the Devil — the head of the mighty Microsoft Goliath that was openly trying to crush the young Open Source David. The Open Source scene even had their own Jesus — the mocking nickname awarded to Richard Stallman for his important contributions to the Open Source Community and his eccentric personality including his long, flowing hair, paired with a propensity for wearing sandals (at times eccentric, but at other times inappropriate — Stallman <a href="https://en.wikipedia.org/wiki/Richard_Stallman#Resignation_from_MIT_and_FSF">resigned from MIT and the FSF in 2019</a> after strong criticism of remarks made by him, that were widely seen as highly insensitive).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*PvfeCgdbGUrr-8Qv9OTm1A.jpeg" /><figcaption>Richard Stallman, the creator of the GPL (mockingly referred to as the Jesus of the Open Source Community) <a href="http://www.softpanorama.org/People/Stallman/Images/saintignucius.jpg">Source</a></figcaption></figure><p>It’s kind of funny. At the time when Olaf and his comrades Till Jaeger, Axel Metzger, Carsten Schulz and Till Kreutzer put a stake in the ground in German law for the GPL, the little band of Open Source renegades was just a bunch of “greenhorns” as Olaf puts it — barely out of college. And yet they were able to make a dent for their Open Source champion, despite the rage coming from the giant in Seattle that employed thousands of people and had all the resources in the world.</p><h3>CCC Cologne &amp; How it all started</h3><p>When you first meet Olaf, you will notice this sparkle in his eyes that instantly tells you of his good natured, approachable charm, but also the kind of brain power that hides away behind his down-to-earth modesty.</p><p>He currently has two jobs side by side: One as the Director of Legal &amp; HR at upday, the other as an author, speaker, and lawyer in the context of startups &amp; IT. He has always been someone with a ton of energy it seems — so it’s no surprise he helped shape Open Source law in Germany in the early 2000s.</p><p>What might be surprising though is that unlike other Open Source enthusiasts he’s not a hacker — he’s a lawyer.</p><p>Olaf first came in contact with Open Source, when his best friend during his studies in Cologne helped found the local branch of the Chaos Computer Club. The Chaos Computer Club (short “CCC”) is Europe’s largest hacker-organization and has been active since the 1980s. When the Cologne Branch was finally founded, Olaf joined the club as the treasurer, taking care of the finances.</p><p>That’s when he first got in touch with the Open Source Licensing model and the GPL — and he was hooked.</p><h3>Drawn to the juris-prudence of Open Source</h3><p>Lawyers and programmers seem to have to have a weird thing in common: They both love well structured, logical text. Lawyers get this sense of beauty out of a legal text, while programmers get this joy out of the logic expressed in good source code.</p><p>I asked Olaf what he found so “fascinating” (his words) about Open Source licensing, and the way he described it made a lot of sense: There were (are) two kinds of licensing models — Proprietary and Open Source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpMCqClIr_ZT0vXwhbv6lQ.jpeg" /><figcaption>Olaf (left) and the gang getting together in the 2000s</figcaption></figure><p>The proprietary licenses were the ones legally protecting software like the Windows 95 OS from being copied, modified, or distributed by third parties other than Microsoft and their distributors. In a world where 80–90% of all computers were running on Windows, and Software-as-a-Service was non-existent, these licenses were the legal backbone to gigantic revenues from global software sales.</p><p>Open Source licensing on the other hand, offered the polar opposite. Not only did the GNU General Public License and its cousins grant anybody the rights to copy and modify software — it even allowed people to make money off of distributing the software or derivatives thereof.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcAnZMq7CF61U4Ow-M_NDg.jpeg" /><figcaption>Another picture of Olaf from the early days of ifrOSS — the Open Source law initiative Olaf joined in the early 2000s</figcaption></figure><p>It must have felt anarchistic to Microsoft executives — and to the Open Source community it did feel like a social movement, too. Far beyond code, they did see Open Source as a way to share access with as many people as possible, not just to software. Today the spirit of Open Source licensing actually far extends software, through concepts like Creative Commons and Open Access.</p><h3>Establishing the GPL in Germany</h3><p>After Olaf passed his official exam in law, he went on to write his dissertation about the GPL. That’s when his work of helping establish the famous license in German law started.</p><p>The way that law-suits in continental Europe work, is slightly different than the “Common Law” system in the US &amp; the UK. Instead of relying on the precedent of previous judgements (fans of the show <a href="https://www.netflix.com/de/title/70195800"><em>Suits</em></a> will know what I mean), law suits and arguments are instead based on legal opinions and interpretations that are published in legal literature &amp; journals.</p><p>Through his dissertation simply titled “Opensourcelaw” (German: “Opensourcerecht”), he got in touch with two other enthusiasts (Till Jaeger &amp; Axel Metzger) of matters of Open Source law in Germany. Together they joined forces as the <a href="https://www.ifross.org/">“ifrOSS”</a> — the “Institute for law (German: “Recht”) in Open Source”, in the early 2000s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/383/1*m5u5xjT4qFNsl8thPvs8IA.jpeg" /><figcaption>The ifOSS’ first publication: A 2005 interpretation of the GPL for the German copyright laws.</figcaption></figure><p>Through their institute, they gave talks, consulted companies and wrote books and legal opinions on Open Source Licensing. In the early 2000s they even created an addendum to a reform of copyright law in Germany, that specifically protected the free-of-charge provision of access to copyrighted work through Open Source licenses. It was dubbed the “Linux clause”.</p><p>Today, 20 years later things are more grown up.</p><p>Olaf has three kids by now and Microsoft has become an important part of the Open Source community through their work on Typescript, currently the <a href="https://stackoverflow.blog/2020/05/27/2020-stack-overflow-developer-survey-results/">second most beloved programming language</a> in the world, and owning <a href="https://news.microsoft.com/announcement/microsoft-acquires-github/">Github</a>, the largest code sharing platform.</p><p>Open Source has turned from being the rebellion to the front and center of modern software development. And at least in Germany, that’s thanks in part to the work of Olaf and a handful of other lawyers passionate about Open Source Licensing, including the GPL.</p><p><strong>Connect to Olaf:</strong><br><a href="https://www.linkedin.com/in/olaf-koglin-85001415/">Olaf on LinkedIn</a><br><a href="https://twitter.com/_cookiebar">Olaf on Twitter</a></p><p><strong>💼 Curious about working at Upday?<br></strong>👉🏻 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksJobsPage&amp;url=https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=upday%26id=65%26tx_kesearch_pi1%5Bpage%5D=1%26tx_kesearch_pi1%5BresetFilters%5D=0%26tx_kesearch_pi1%5BsortByField%5D=score%26tx_kesearch_pi1%5BsortByDir%5D=desc&amp;sourceId=tech-blog-2020-10-19">Check out our open positions</a></p><p>— — —</p><p>Hi, I’m Jonas and I’m currently building up a <strong><em>Global Axel Springer Developer Community</em></strong>. S<strong>ubscribe to our Weekly Tech Newsletter</strong> to get a fresh story like this <em>every Monday</em> and to receive details on how you can join our global developer community ✌🏻</p><p>Want me to help tell your story? Reach out to me 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-10-19">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-10-19">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*WhutmBsXTyffz3XYKTxi1A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c984433221cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/meet-the-man-who-helped-bring-the-general-public-license-gpl-into-german-law-c984433221cd">Meet the man who helped bring the General Public License (GPL) into German Law</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decades saved every month]]></title>
            <link>https://medium.com/axel-springer-tech/decades-saved-every-month-2f8948af6c67?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f8948af6c67</guid>
            <category><![CDATA[vanilla-javascript]]></category>
            <category><![CDATA[page-speed]]></category>
            <category><![CDATA[ad-technology]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 12 Oct 2020 07:56:17 GMT</pubDate>
            <atom:updated>2020-10-12T08:00:51.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3-I1B3sjuR71H2iJtvXXyA.png" /></figure><h4>How 500ms of page load speedups can ad(d) up</h4><p><em>NMT (“National Media Tech”) is the tech-division behind many of Axel Springer’s German News Media brands. As a part of the Axel Springer Group, it’s also a member of the Global Axel Springer Developer Community.</em></p><p>Carlos &amp; René of the Ad Technology team are a duo you will remember when you see them. They could also be the leading roles in a TV show about an unlikely duo fighting crime par excellence. Carlos, the native South American, is a charismatic presence, who always seems to be in a sunny mood, while René (Carlos’ “first developer”) is quite a bit shorter than Carlos, but equally energetic, ready to crack a huge grin at any time and according to Carlos “a genius”.</p><p>Earlier this year the team (which also includes Johannes, Steffen, Oliver &amp; Tobias) released a new version of their custom built, purely Vanilla JavaScript based ad-tech middleware to manage ad servers on 50+ websites from the Axel Springer universe. The 4.0 release of the “Adlib” (the name of their middleware) lead to page load speed ups of 500ms — 1000ms.</p><p>With around 11 billion ad impressions and 1.5 billion page impressions every month, 500ms of reduced page speeds add up to around 24 years (!!) of loading times saved every month.</p><p>With big impact comes big responsibility, but the trick the team used will surprise you…</p><h3>The Nerds inside the Ad Agency</h3><p>René, Carlos and the rest of the Ad Technology team used to be the nerds among a huge team of ad-specialists. <em>Media Impact</em> the inhouse ad company of Axel Springer is still responsible for directly selling digital advertisement space to companies for some of the biggest websites in Europe — and the team used to be right in the middle of that. As you can imagine, it’s a very sales-driven environment.</p><p>“We had to beg even for things like IntelliJ licenses or test devices” Carlos explains — he has been the team lead for 7 years now and was incredibly happy when his team was moved out of the inhouse ad agency into the very tech &amp; product oriented NMT division of Axel Springer.</p><p>The move made sense. The team builds technology to manage the programmatic ads on over 50 different websites (including BILD.de, Welt.de, Sport1, Transfermarkt, finanzen.net &amp; many more) — in a sense the polar opposite of the direct advertisement that the teams around them were selling at Media Impact.</p><h3>A quick primer on programmatic advertisement</h3><p>Programatic advertisement sounds complicated but is actually pretty simple (on a high level).</p><p>Remember when ads were still on large physical displays? (Pepperidge farm remembers!). You had these physical spaces, and when you paid money your advertisement poster was displayed there. If somebody else paid more money, you were probably kicked off and the more visible the billboard, the more expensive it was.</p><p>Online ads work in a similar, but in a highly automated way, called <em>programmatic advertisement.</em> If you run a website or an app, you can fill some of your screen space with ads. To offer this virtual space up to advertisers, you would usually use an ad server that you configure in a way that it knows what ads to display.</p><h3>Adlib — managing ad space for 11 Billion monthly ad impressions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*4qnecFAFRMxxLukbUkVC7g.png" /><figcaption>Logo of the “Adlib” library — the brain behind placing ads on 50+ websites throughout the Axel Springer universe</figcaption></figure><p>So what do you do when you manage the digital ad space for 50+ websites with billions of ad impressions? You naturally build a middlelayer to manage the complexity.</p><p>In the case of the Ad Technology team, that middlelayer is called <em>Adlib</em> and is a Vanilla JavaSript library that is loaded on every pageload — around 1.5 billion times every month.</p><p>With great traffic comes great responsibilities and as with anything in tech the question is never if it breaks, but when it breaks. René tells me that a few years ago the Adlib was serving a faulty ad that overwrote the brower’s document.write function. As a result all Axel Springer websites went blank for 2 hours. That’s millions of ad impressions missed.</p><p>The team obviously fixed the bug and made sure that in the worst case scenario faulty ads will only break the ads — not the entire site. But it’s a good example of how much responsiblity the team has.</p><h3>Adlib 4.0 — dramatic speedups through tiny modules</h3><p>The flip side of being able to cause a whiteout of Germany’s most popular websites is that any improvements to the Adlib directly benefits all of these big websites as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*SPRX_M_PGOLkSCl9YzlJvw.png" /><figcaption>Where’s the drop? (Obvious Deadmau5 reference) — Charts showing the drop in page loads after deploying the beta of the Adlib 4.0</figcaption></figure><p>Earlier this year René lead a refactor of the Adlib and the team released version 4.0 . This was the version that on average made the websites load 500ms to 1000ms faster. A huge improvement.</p><p>The secret sauce? Heavy modulization.</p><p>“It used to take 2 network requests to get the Adlib. Today it’s around 50 network requests” René explains. The strategy used to be minimize the number of round-trips to the server, while today it’s rather about consuming only the data that’s needed. The team ended up bundling each of their core-functions of the Adlib into a separate file.</p><p>On top of that the Adlib 4.0 release included a cache-buster scheme that allowed the team to additionally only replace files on the CDN that had actually changed and have the rest served from Cache.</p><p>High cache performance, and economically loading only the functionality that’s needed. The difference was clearly noticeable.</p><h3>A|B tests on the CDN &amp; W3C Committee work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ip9z3FTUzmOU_JvK4domxA.jpeg" /><figcaption>A team photo from pre-COVID-19 times: From left to right: Lars (in the back — close collaborator from another team), Tobias, Carlos, Johannes &amp; Oliver (on the picture), Steffen and René</figcaption></figure><p>It’s not just the Adlib 4.0 that’s impressive about this team — it’s also the way that they constantly improve performance. CDN level A|B tests, using the inhouse IP range as the beta testing group, or contributing directly to the W3C committee on ad-technology — the Ad Technology team does some very impressive work.</p><p>So you will hear more from this team in the future — be sure to subscribe to the TechNewsletter to not miss these future stories.</p><p><strong>Connect to Carlos &amp; René:</strong><br><a href="https://www.linkedin.com/in/cbracho">Carlos on LinkedIn</a><br><a href="https://www.linkedin.com/in/baudisch-rene-823460125">René on LinkedIn</a></p><p><strong>💼 Curious about working at Axel Springer?<br></strong>👉🏻 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksJobsPage&amp;url=https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=national+media+tech%26id=65%26tx_kesearch_pi1%5Bpage%5D=1%26tx_kesearch_pi1%5BresetFilters%5D=0%26tx_kesearch_pi1%5BsortByField%5D=score%26tx_kesearch_pi1%5BsortByDir%5D=desc&amp;sourceId=tech-blog-2020-10-12">Check out our open positions</a></p><p>— — —</p><p>Hi, I’m Jonas and I’m currently building up a <strong><em>Global Axel Springer Developer Community</em></strong>. S<strong>ubscribe to our Weekly Tech Newsletter</strong> to get a fresh story like this <em>every Monday</em> and to receive details on how you can join our global developer community ✌🏻</p><p>Want me to help tell your story? Reach out to me 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-10-12">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-10-12">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ysnkhmLah85b21u1.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f8948af6c67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/decades-saved-every-month-2f8948af6c67">Decades saved every month</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integration-Testing with a ]]></title>
            <link>https://medium.com/axel-springer-tech/integration-testing-with-a-5114668c8d01?source=rss-19f6e9305a42------2</link>
            <guid isPermaLink="false">https://medium.com/p/5114668c8d01</guid>
            <category><![CDATA[radar]]></category>
            <category><![CDATA[real-world-testing]]></category>
            <category><![CDATA[integration-testing]]></category>
            <category><![CDATA[mobile-development]]></category>
            <dc:creator><![CDATA[Jonas Peeck]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 07:26:33 GMT</pubDate>
            <atom:updated>2020-09-28T07:26:33.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77oesZ6eXf4C82H4pJoCjw.png" /></figure><h4>How Bonial built location-based services for millions of app users — and made sure it works properly</h4><p><a href="https://www.bonial.com/"><em>Bonial</em></a><em> builds apps and services that help physical retail stores attract and advertise to customers. As a part of the Axel Springer Family, the developers at Bonial are also members of the Global Axel Springer Developer Community.</em></p><p>Nikhil probably didn’t think sending his boss on repetitive bike-rides to a grocery store in Berlin would be part of his job, when he moved from Banagalore — “India’s Silicon Valley” — to Berlin two and a half years ago.<br>But here he was, 6 months into his job at Bonial, benchmarking the location-data generated by three different systems against each other. Location-data produced by the Notifications team riding their bikes through Berlin and by Lucas, the then Head of Engineering (Monetization) at Bonial, riding back and forth between the office and a local Aldi grocery store.</p><p>Our story starts at a hackathon-gone-right: Teams at Bonial had developed a prototype of a feature at a hackathon, which ended up being hugely successful with their customers. They had built a system to track customers entering and leaving physical retail stores, enabling a metric that is trivial to calculate for online stores, but hard to get for physical stores: Average visit duration.</p><h3>Bringing Web Metrics to Physical Retail Stores</h3><p>“Bonials’s mission is to replace paper-brochures that usually get thrown in the trash” Nikhil explained, helping me understand the kind of problem they were solving through a new tracking system. “Paper-brochures” in that case is something German households are very accustomed to. Free bundles of plastic-wrapped paper brochures touting the latest offers of local stores — most people, including myself, usually throw the complete bundle into the next trash can.</p><p>Bonial is disrupting that space through their digital alternatives to paper-brochures, including their apps “MeinProspekt” and “KaufDA” (which directly translated would be “MyBrochure” and “buyTHERE”). Users of the apps can mark local retail shops &amp; grocery stores as their favorites and will in turn receive digital brochures and offers from these shops through the apps.</p><p>It’s a common pattern by now: Replace broad, physical ads (displayed to everyone) with targeted, digital ads only delivered to those who likely have an interest in seeing the ad.</p><p>What was missing from Bonial’s offering for physical stores however was something Lucas refers to as “Attribution” — the kind of tracking that allows companies to know whether their money spent on marketing actually led to a customer visiting their stores.</p><h3>Hacking the “Average Visit Duration” problem for physical stores</h3><p>The solution came through a hackathon: A custom-built feature based on geo-fencing, helping Bonial show their business customers when users entered and exited a store and allowing businesses to understand how much time users of “MeinProspekt” and “KaufDA” were spending at their physical store locations. Additionally businesses could now send push-notifications to customers coming close to the locations of their physical stores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3AoJCaZm2N9KfLWXRA33Q.png" /><figcaption>Screenshot showing the currently active geofences</figcaption></figure><p>The prototype they had built at a hackathon ended up being incredibly popular with their business customers — but that turned out to be a problem: “I have a friend who works at Amazon — they have 150–200 people working on <em>Attribution</em> alone” Lucas explained.</p><p>They had a successful feature, but they knew that continuing its development would require a lot of additional people-power and moving pretty far away of their core-mission of replacing paper-brochures…</p><h3>🚲-rides &amp; Benchmarks to replace the prototype</h3><p>In the end, the decision on what to do was easy: Use an external service to manage the increasing number of geofences (130.000 in France &amp; Germany at this point) and handle “enter” and “exit” events of users walking in- and out of stores. They just had to pick the right tool.</p><p>The team ended up with two services that they wanted to test: Radar.io and Bitplaces. Benchmarking them against their custom-built solution, they wanted to compare the number of complete vs. incomplete event pairs (e.g. an “enter” event that has no corresponding “exit” event) and the delay between users entering a geo-fence and the service triggering an event.</p><p>While during development a “Fake GPS” service offered some help in testing out their two test-candidates, it quickly came down to real-world, pedal-on-the-ground testing: “Simulations are okay, but then you want to test that in the real-world”, Lucas explains.</p><p>And so Lucas went on bike rides to Aldi. A lot of bike rides, actually.</p><p>“First test was a disaster” Lucas explains — both of them laughing at what comes across as a fun time they both enjoy looking back to. The system stabilized through constant refinements over 2–3 weeks, with the help of 20 of their colleagues testing out the new systems*, sending back reports of something not working in a dedicated Slack channel . The negative reports became less and less — and eventually they were able to see that radar.io worked great for what they were trying to do, beating their prototype.</p><p>*(Lucas specifically asked me to include a special THANK YOU! to the whole Notifications team and Félix Boulanger for the hard work they put into this project)</p><h3>Learnings: Make Data Driven Decisions &amp; Test features with colleagues</h3><p>When I asked them what learnings they would share from this project, Nikhil tells me how impressed he is by the level at which Bonial uses data — both in the high-quality of the data and how they used data to inform their (integration) decisions.</p><p>“Be really clear on what you want to measure. For example: How do we know that radar is really performing better than our own solution?” Nikhil explains their approach of making a data-focused decision between the alternative geo-services they were testing out against each other.</p><p>Lucas on the other hand stressed how well it worked to recruit 20 of their colleagues as testers: “Teamwork is always a plus when you need to test integrations”, serving as an important reminder that often insights about the stuff we build can be around the corner — literally — when we just ask colleagues for hallway tests of our latest work.</p><p>The benchmarks they performed &amp; the rigorous testing with colleagues helped the team successfully implement radar.io as the new location-based service provider for 2.6 million app users in record time.</p><p>“Bonial was one of the fastest integrators of radar.io” Lucas proudly shares with me. Maybe — just maybe — all the fresh air during the testing phase played a small part in that.</p><p><strong>Connect to Nikhil:</strong><br><a href="https://www.linkedin.com/in/nikhilshambhu/">Nikhil on LinkedIn</a></p><p><strong>💼 Curious about working at Bonial?<br></strong>👉🏻 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksJobsPage&amp;url=https://career.axelspringer.com/de/jobangebote?tx_kesearch_pi1%5Bsword%5D=bonial%26id=65%26tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B511%5D=taetigkeitsbereich_data-science%26tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B473%5D=taetigkeitsbereich_it%26tx_kesearch_pi1%5Bfilter%5D%5B5%5D%5B497%5D=taetigkeitsbereich_produktmanagement%26tx_kesearch_pi1%5Bpage%5D=1%26tx_kesearch_pi1%5BresetFilters%5D=0%26tx_kesearch_pi1%5BsortByField%5D=%26tx_kesearch_pi1%5BsortByDir%5D=&amp;sourceId=tech-blog-2020-09-28">Check out our open positions</a></p><p>— — —</p><p>Hi, I’m Jonas and I’m currently building up a <strong><em>Global Axel Springer Developer Community</em></strong>. S<strong>ubscribe to our Weekly Tech Newsletter</strong> to get a fresh story like this <em>every Monday</em> and to receive details on how you can join our global developer community ✌🏻</p><p>Want me to help tell your story? Reach out to me 👇🏻</p><p>🚀 <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksNewsletterSignupLink&amp;url=https://axelspringertech.com/newsletter&amp;sourceId=tech-blog-2020-09-28">Subscribe to the Weekly Tech Newsletter</a></p><p>✉️ <a href="https://webhooks.axelspringertech.com/resolve?eventType=UserClicksTechAtAxelspringerEmailLink&amp;url=mailto:tech@axelspringer.com?subject=%5BYour%20TechBlog%20post%5D&amp;sourceId=tech-blog-2020-09-28">Get in touch with us</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*WhutmBsXTyffz3XYKTxi1A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5114668c8d01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axel-springer-tech/integration-testing-with-a-5114668c8d01">Integration-Testing with a 🚲</a> was originally published in <a href="https://medium.com/axel-springer-tech">Axel Springer Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>