<?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 Daniel Jürges on Medium]]></title>
        <description><![CDATA[Stories by Daniel Jürges on Medium]]></description>
        <link>https://medium.com/@daniel.juerges?source=rss-a5a5090e916------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*pnlnSobhOQ2nkmyhNpoyag.jpeg</url>
            <title>Stories by Daniel Jürges on Medium</title>
            <link>https://medium.com/@daniel.juerges?source=rss-a5a5090e916------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:56:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daniel.juerges/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[The paradox of slowing down while growing]]></title>
            <link>https://medium.com/coyo-tech/the-paradox-of-slowing-down-while-growing-bcfd10a11055?source=rss-a5a5090e916------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcfd10a11055</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Daniel Jürges]]></dc:creator>
            <pubDate>Tue, 23 Feb 2021 13:44:31 GMT</pubDate>
            <atom:updated>2021-02-23T15:35:32.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p-miWW6FGuUryRxuDuZi2A.jpeg" /><figcaption><a href="https://www.pexels.com/es-es/foto/sano-mujer-nina-curva-4473608/">https://www.pexels.com/es-es/foto/sano-mujer-nina-curva-4473608/</a></figcaption></figure><p>You might have been there yourself.</p><p>You start out in a small company and that very company has grown into a very big one over time. Things start to feel slow. And you wonder why. Or you are late with a project and need to add more workpower to it, so you get one or two people in. You think, can I still make it in time? Well, that depends.</p><p>Chances are, you will not be as fast as you think. And that’s barely news, in fact this has been observed as early as <a href="https://en.wikipedia.org/wiki/The_Mythical_Man-Month">1975 in software projects</a> and been called <em>Brooks’ Law</em>:</p><blockquote>Adding manpower to a late software project will make it later</blockquote><p>The more people there are, the more complicated it gets. It’s that easy.</p><h3>Why do we get slow, when we grow?</h3><p>Whatever you work on, you won’t do it alone in most modern day working environments. And splitting work means more communication to be able to do it, no matter what fancy tools 2021 gave you at hand.</p><p>Have you ever thought about how many possible connections there are in a group of four people? Six. Now make that grow to six people and you already have fifteen possible connections. Okay. When I think about how many developers there were when I joined the company versus how many our Engineering department has now, we go from 190 to a 1225 possible interactions. Wow. That’s just <em>the devs</em>.</p><p>And the bad news is, is just doesn’t stop there. There will be more legacy code, there will be higher expectations of customers, you name it.</p><h3>What can we do about it?</h3><p>Unfortunately there is not much that can be done about it. The per head productivity will decrease in any growing company, so we simply have to accept that as a fact. But the good news is, you can learn to live with it.</p><p><em>Expose the hidden complexity</em>, for example when sales is asking for a new feature explain the string of requirements and technical changes that would be necessary to deliver it.</p><p><em>Show the progress</em> to remind everyone of the actual work that is being done and how it brings to the code base and business forward.</p><p><em>Develop software pragramatically</em> by making pragmatic decisions and focusing on only adding value for the user and living boyscout principles to prevent or at least slow down technical debt.</p><h3>We want it all</h3><p><em>Sales people want it now! Product managers want all of the features! The engineers want to build it right!</em></p><p>In an ideal world, we would be able to satisfy all. But there is no such thing (yet?) and that’s where the tension starts to rise and decisions have to be made.</p><p><strong>Scope</strong> <br>What are we going to do and how are we going to do it? This would typically entail to break the product or feature into smaller work packages like epics and stories that deliver value to the application and then prioritize them.</p><p><strong>Resources<br></strong>How many people do we need to get the work done? This is about the people that are interested to get involved and how many it would require to deliver this in…</p><p><strong>Time<br></strong>There will always be a deadline. One cannot change the time, but the magic trick is to work it with good prioritization, milestones, minimum viable products and the likes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/234/1*uf95mtW1O3HwhjeyCPFXgQ.gif" /></figure><h3>Current challenges at COYO</h3><p>One of the biggest challenges we experience right now at COYO is the alignment of our product and technical roadmaps.</p><p>I personally imagine it like a good zipper. There comes a product epic from the left, here a technical one from the right. And <em>swoosh!</em> goes the zipper, creating seemless alignment between them and a strong bond. Ladies and gentleman, we now have a picture perfect roadmap, providing great new features to the users but also addressing necessary changes like migrations, updates and refactorings, essentially removing technical debt.</p><p>But the reality is more complex. Of course there are also needs from customer support and sales, we have an ever-growing QA team and increased focus on delivering a high quality product to an ever growing amount of customers.</p><p>We are victims of our own success, so to say.</p><p>But that will only motivate us even more to work on the current technical stand-out topics. Just to name a few, these are for example:</p><ul><li>Angular migration</li><li>Modularization of our backend</li><li>Moving to a different cloud provider</li><li>Test automatisation</li></ul><p>And referring back to the three boundaries I mentioned earlier:</p><p>We are somewhat flexible about the required time for these long-running topics. But we will <em>never</em> compromise on vision, execution and delivering the highest quality product possible.</p><p>That’s all, folks, thanks for your interest!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcfd10a11055" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coyo-tech/the-paradox-of-slowing-down-while-growing-bcfd10a11055">The paradox of slowing down while growing</a> was originally published in <a href="https://medium.com/coyo-tech">Haiilo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you a cathedral builder or a bazaar browser?]]></title>
            <link>https://medium.com/coyo-tech/are-you-a-cathedral-builder-or-a-bazaar-browser-b78072138121?source=rss-a5a5090e916------2</link>
            <guid isPermaLink="false">https://medium.com/p/b78072138121</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Daniel Jürges]]></dc:creator>
            <pubDate>Tue, 18 Aug 2020 15:29:18 GMT</pubDate>
            <atom:updated>2020-08-18T15:29:18.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSwjXhD9UsfGxY2wTcLvPQ.jpeg" /></figure><p>Have you ever heard of this classical joke?</p><blockquote>There are 10 types of people: Those who understand binary and those who don’t.</blockquote><p>Today, I want to talk about yet another separation into two groups of people.</p><p>In the past week, I’ve come across a theory to distinguish between developers that a) like to deep-dive into a given topic and dedicate themselves to the absolute technically best and eternally valid solution and b) those that are happily trying to surround themselves with new stuff and try things out a lot, even not worrying about building stuff and then to have it to throw away eventually. <a href="https://pragprog.com/titles/jsengman/become-an-effective-software-engineering-manager/">[1]</a></p><p>The previous ones are called <strong><em>cathedral builders</em></strong>, while the latter are dubbed <strong><em>bazaar browsers</em></strong>.</p><p>The observation was originally made for open source software projects, which were either developed by a small number of tech wizards, closely guarding every change made to the project. On the contrary, a different style evolved, with open, massive scale development in the public. <a href="https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar">[2]</a></p><p><em>So which type are you? Are you motivated by change or crave stability?</em></p><h4>Cathedral builder</h4><p>As a constructor of a building of this magnitude, you yearn for focus, stability, purism and craftsmanship.</p><p>You want to be a <em>subject-matter expert</em>, being able to contribute to core areas of the technology stack and taking ownership to be the most knowledgable person within the company for a certain topic.</p><p>You are a <em>cornerstone</em> of the team, being the individual that everyone seeks advice from when they encounter something new.</p><p>You go <em>deep, not wide. </em>To obtain thorough knowledge, you might choose to practice deep mastery over newness and contribute to open source projects to contribute back to the community.</p><p>You <em>show others their own ways.</em> Being an expert makes you a good teacher, transferring the knowledge and being able to mentor others.</p><p>You <em>revel in the details</em>. Staying away from company politics and incomplete knowledge so you can focus on the small details that others might not see.</p><h4>Bazaar browsers</h4><p>As someone seeking excitement, variety, chaos and change to grow, you wish to sample as many sights and new experiences as possible.</p><p>You want <em>as much newness as possible</em>. Oh, is there a new project coming up? To have new challenges, domains and products, you’ll try to get in front of whatever new thing there is in the engineering department.</p><p>You <em>build and throw away</em> if necessary. So you are rapid-prototyping and it didn’t work out? Well, better luck next time, so let’s do it again. And maybe try some other new technology while being at it.</p><p>You <em>avoid stagnation</em>. The idea of working in the same area for a long time is rather a sign of stagnation for you than true mastery.</p><p>You might even <em>like to switch teams</em>. Maybe your team is a bit different than yourself, so you can totally imagine to stay with another one for a while to check out what they got up their sleeves, try something new and fun and take in the knowledge to then return with newly injected energy for your old team.</p><p>There’s a good chance that you probably talked with someone about your career perspectives, for instance whether to change into management at some point or not, but never touched on this topic before.</p><p>So take this as a food for thought and where you see yourself, not just leading to a <strong><em>better understanding of your needs</em></strong> but also how it <strong><em>shapes the interactions with others</em></strong>, be it in your team or department.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b78072138121" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coyo-tech/are-you-a-cathedral-builder-or-a-bazaar-browser-b78072138121">Are you a cathedral builder or a bazaar browser?</a> was originally published in <a href="https://medium.com/coyo-tech">Haiilo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The first COYO Hackathon]]></title>
            <link>https://medium.com/coyo-tech/the-first-coyo-hackathon-21bc86ca968d?source=rss-a5a5090e916------2</link>
            <guid isPermaLink="false">https://medium.com/p/21bc86ca968d</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Daniel Jürges]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 11:48:26 GMT</pubDate>
            <atom:updated>2020-06-12T11:48:26.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*8JiwskoUB0yMIXwcszsAuQ.png" /></figure><p>It all starts with an idea. And in our case, we just had to remember COYOs roots and where we are coming from as a company, to get inspired for the present.</p><p>Here at COYO we have a world of many freedoms. And for the software engineering department, one of the arguably biggest freedoms is the free coding day. On any bi-weekly Friday, it is completely left up to the imagination of the developer what to do with her or his time and what happens. Some decide to simply carry on with their daily work, others use it to further educate themselves on new technologies and then there is a group of people who use it to actively develop improvements for our product.</p><p>We’ve seen in the past that this is a great way to drive technological change and come up with absolutely unexpected yet marvellous additions to our product. But we have also witnessed its limitations. Ideally, you would want to be able to continuously progress on a topic not just every other week. That also poses a challenge to team up with a couple of developers. The product management or the design team do not run on the same schedule, so grabbing a share of their attention might be tough when you need it.</p><p>So as we really like the overall outcome of these free coding days, we asked ourselves what we could do to streamline the work that is being done there, how to put a better support system in place and make it transparent to the whole company what is being developed.</p><p>With some of our core values being agile, collaborative, uncomplicated, having a positive mindset and always thriving to be better, we turned to something that we did before and remembered from our earlier days. Going back a few years in our minds, we still felt this very hands-on, rapid-prototyping kind of atmosphere, which was also a bit hacky, that was a trademark of our company “youth”. And we then connected it with the experience of previous COYO summits, where we invited customers to our office to talk about the future of our product and roadmap, but also gave them the possibility to join in and brainstorm improvements that could then be put into practice by our developers in a one day <strong>Hackathon</strong>. And there it was. <strong>Our idea of agility meeting a well thought out product.</strong></p><p>We came up with a timetable, some basic requirements and people and departments who would need to get involved for what we had in mind, but eventually it was just acting out that very idea.</p><p>The schedule was as follows:</p><p><strong>until 29th of May: Call for Ideas<br>until 29th of May: Registration of developers<br>2nd of June: Jury evaluation of ideas<br>3rd — 5th of June: Hackathon<br>8th of June: Company-wide presentation and vote</strong></p><p>It was important to us that the event as well as the process were as transparent and open as possible, so we started by collecting ideas from anyone. No matter your job or department in COYO, all ideas were warmly welcomed. And there were plenty. In the end, we counted <strong>44 transmittals</strong>, detailing the feature request and the use cases for it. WOAH! And <strong>18 developers</strong> wanted to participate in the Hackathon, which was huge as well.</p><p>A <strong>jury</strong> representing the software engineering team, product management, product design and key account management, then proceeded to <strong>evaluate the sent-in proposals</strong>. Instead of valuing and pre-judging them for the team, we committed to keep the selection as broad as possible by just eliminating those that were no suitable candidates for the Hackathon because of either missing product fit, they were already on our road map or being too small or too big of a topic to be worked on for three days. So we started into the Hackathon with <strong>20 ideas being left</strong>. And of course it was all remote work, so we did video calls to organise it. Easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8WzgQ5mms4PIGYeUTYr-WQ.png" /></figure><p>In the kick-off call (9:30 am, which explains all the faces 😀), every author had to do a 1 minute pitch for her or his idea. If the idea was to be chosen by one or more developers, the person — again, no matter the actual job or department — would then have to companion the team as their respective product owner during those three days. After all pitches, the developers made their choices and handed in their first and second picks, so we could form a total of six teams.</p><p>These came out as the chosen few:</p><p><strong>Low Quality Image Placeholders</strong></p><p><strong>Content discovery</strong></p><p><strong>Read confirmation for blog posts</strong></p><p><strong>Audio messages</strong></p><p><strong>Mark timeline posts for later</strong></p><p><strong>Broadcast feature</strong></p><p>And to keep up the tension, we will close with this giant cliffhanger.</p><p>If you ask yourself what stands behind the somewhat cryptic names and what our team was able to accomplish in those three following days, watch out for the next instalment of our blog series as it will detail the journey of some of the features and their actual outcome. See you after the break. 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21bc86ca968d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coyo-tech/the-first-coyo-hackathon-21bc86ca968d">The first COYO Hackathon</a> was originally published in <a href="https://medium.com/coyo-tech">Haiilo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your code is your legacy]]></title>
            <link>https://medium.com/coyo-tech/your-code-is-your-legacy-d8e92f7663?source=rss-a5a5090e916------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8e92f7663</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Daniel Jürges]]></dc:creator>
            <pubDate>Fri, 22 May 2020 13:59:58 GMT</pubDate>
            <atom:updated>2020-05-26T11:14:25.281Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0jyPktU-xz54qqQ-ncnzg.jpeg" /></figure><p>Why every developer is writing code that immediately becomes legacy and how to think software development, maintainability and technical debt in the long-term.</p><p>Do you still remember what you wrote yesterday? It is old. Not as old as your grandma, and not as old as in outdated, but old as it already is not the best you could do anymore.</p><p>Once you completed a task, not the code you created is the valuable thing, but that knowledge you gained while doing so. And if you were to do it again, right now, the decisions you’d make and the paths you’d take would already be dramatically different.</p><p>And thinking this a bit further, you will ultimately end at one of the basic laws of software engineering. You either go about your daily work and just add new features and fix bugs, or you change the architecture and rewrite your code base to keep it maintainable and reduce technical debt. Both ways, you’ll end up producing stuff that will not live up to the expectations in the near future, for any reasons.</p><p>That is why all your written code will eventually turn out to be legacy code and immediately is, actually. And to add another inconvenient truth: your software is in the constant process of dying.</p><p>Well, how do we deal with it? You can be very sad about it and deny everything I just wrote (you might want to google the five stages of grief now) or you can stare this evil rabbit directly into the eyes and confront it in an epic battle, going head first. I opt for the latter.</p><p>Here at COYO, we made a bold decision to complete rewrite our application anew and then migrate all customers to it in 2016. After some development pains and delays, this eventually worked out like a charm. It was a gutsy and smart one-time move to jump into the future by doing something from the past. But it is my heart-felt belief, that in times of cloud computing, we see that versions cease to exist, at least from a user’s point of view, and continuous deployments and feature delivery make gradual rewrites and architectural changes the only way to go.</p><p>So what does this mean for COYO? With our software reaching a more mature point in its life, as core components are now some three to four years old, we start so see an increasingly amount of libraries with end of lifetime on the horizon. That is something we have already dealt with in the past (AngularJS to Angular migration) but also leads us to taking precautionary measures for a technical more apt and sound platform, that is well-suited for all the latest technology rage yet to be invented.</p><p>So we are currently well underway to modularize our backend, upgrade ElasticSearch, finish the Angular migration and so on. But we have also taken a different approach introducing new features or add-ons. Why not have a micro service for it, written in a then to be determined language with a then to be determined technology stack, if there is a strong case for it?</p><p>Because once you have realised that your code can only be at its best in the very minute you wrote it, you will also start to think software development, maintainability and technical debt in the long-term and come to the conclusion, that even during the development of just tiny parts of the software, there are the ever more greater decisions looming in the backend.</p><p>Don’t make them lighthearted, because they can eventually affect the overall lifetime of your product. But at the same time, be curious, adventurous and bold about it, because the only future-proof direction is forward.</p><p>COYO has understood this well and gotten better and better over time to live this by example, and you will continue to hear from us about that journey in future articles. So long and thanks for your time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8e92f7663" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coyo-tech/your-code-is-your-legacy-d8e92f7663">Your code is your legacy</a> was originally published in <a href="https://medium.com/coyo-tech">Haiilo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>