<?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 Femke Buijs on Medium]]></title>
        <description><![CDATA[Stories by Femke Buijs on Medium]]></description>
        <link>https://medium.com/@femkebuijs?source=rss-827d21345814------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*185c7QltmrpsSeXBcTQ4-Q.png</url>
            <title>Stories by Femke Buijs on Medium</title>
            <link>https://medium.com/@femkebuijs?source=rss-827d21345814------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:24:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@femkebuijs/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[Developers: The Next Generation]]></title>
            <link>https://medium.com/mollie-payments/developers-the-next-generation-5249af92be81?source=rss-827d21345814------2</link>
            <guid isPermaLink="false">https://medium.com/p/5249af92be81</guid>
            <category><![CDATA[coding-for-kids]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Femke Buijs]]></dc:creator>
            <pubDate>Thu, 03 Nov 2022 10:28:48 GMT</pubDate>
            <atom:updated>2022-11-09T13:38:53.509Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*cjz71E3aTTawjNH0ADoRaQ@2x.png" /></figure><p>Ever since I started programming I have had this dream: to organise a coding camp, free of charge, for high school kids, and especially for girls. A camp I would have liked to exist during my high school years. So I wouldn’t have had to wait 10 years to figure out where my passion lies, just because I didn’t know something like programming existed.</p><p>I shared this dream with our CTO at the time and wrote a business case about how I envisioned it to be, and to my own shock I got a very short answer back:</p><p>“Sounds great, let’s do it.”</p><p>Whoops, now I actually needed to organise it! And I had no idea how!</p><p>With a small group of colleagues we started planning. A website for the camp, location, what we wanted to teach, and most importantly: the kids who would attend! Through an acquaintance I was able to get contact numbers of some high schools in Amsterdam, and together with the schools we decided to focus on only one school, to prevent any disappointments should we receive more than our limit of 10 sign ups for this first trial.</p><p>This, unfortunately, turned out to be a mistake. Relying fully on the promise of this school to fill the camp was something we had to learn the hard way: 5 days before the camp we only had one sign up. We had to make a decision, what were we going to do? Even opening the camp up immediately to our Mollies’ kids and posting it on LinkedIn didn’t make a difference: we had to postpone the camp.</p><p>Even though the camp was postponed and not cancelled, I felt like I had failed. We shared with everyone that we were going to organise a summer camp, and now it wasn’t happening.</p><p>However, as turned out later, postponing the camp was one of the best decisions we made. We had way more time to create the programme, acquire awesome merchandise, and most importantly, get more kids in! I approached more schools, opened it to our Mollies again, and suddenly the sign ups flooded in. Within 5 days the camp was full and we even had to close the application process. I couldn’t believe it, it was actually going to happen!</p><p>D-day arrived, the 18th of October, the first day of the coding camp. Faces suddenly appeared to the names I had been in contact with for weeks. Kids from ages between 12–15 years old, different cultural backgrounds, even different languages, all came in one by one, too shy to talk to anyone. They sat awkwardly side by side while we started with the basics. What happens in a browser? What is HTML? What does code look like? Soon they could open their laptops and the excitement on their faces grew. Every time they accomplished creating something as simple as a title, or a background colour, we could hear “Wow!” and “Look what I created!”.</p><p>As the days went by they learned more HTML, CSS to add styling, and JavaScript to add some interactivity. Especially the latter turned out to be a brain breaker, and not all could understand the logic behind it. But with the days going by they got to know each other better as well, and they started to help each other out, working in teams.</p><p>Before they knew it they could start working on their final assignment, which consisted of amongst other things, taking pictures during our donut pit stop walk along the canals of Amsterdam. The photos would show up on their own webpage, which also consisted of a hero page and a page of their favourite songs. The week ended with each group presenting their webpages to the other groups, where even the shyest of them all got up on stage.</p><p>Besides seeing them learning to code, we noticed they got more and more comfortable with each other and the office environment, with the peak being them playing hide and seek in and around the Founders club, hijacking the ping pong table from our Mollies, and wanting to walk into the Marketing event to go play with the massive tumble tower.</p><p>At the start of the event, someone asked me: what is the most important thing you would like to achieve with this camp? The answer was clear: to have at least a few kids walk out excited to learn more about programming, and for that few to consist of at least one girl. Having the camp concluded with 8 girls and 3 boys, and for a couple of girls to ask me how they can continue learning to program after the camp, I’d say Codeo has turned out to be exactly what I envisioned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GT6IPPnM_pEl-MnJ" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5249af92be81" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mollie-payments/developers-the-next-generation-5249af92be81">Developers: The Next Generation</a> was originally published in <a href="https://medium.com/mollie-payments">Mollie</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stories from a career dropout]]></title>
            <link>https://medium.com/mollie-payments/stories-from-a-career-dropout-978cd1ef150b?source=rss-827d21345814------2</link>
            <guid isPermaLink="false">https://medium.com/p/978cd1ef150b</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Femke Buijs]]></dc:creator>
            <pubDate>Wed, 08 Jun 2022 11:31:46 GMT</pubDate>
            <atom:updated>2022-11-03T15:54:12.481Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine that your current career is a mountain you climb, this might even be a very difficult one. There are lots of rocks on the road, it’s very steep, the weather is horrible. So while you are walking up, there is no way you’re going back down. You’ve come all this way, why would you? However, there might be another mountain that is better suited to your skillset. So choosing to go back down and climb another may make the journey a whole lot easier and more rewarding. Finding the right career can feel like that as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EOyWSZjC-Ct8Ny4gQu9fOg.jpeg" /></figure><p>About five years ago I changed my career, and ever since then I have been approached by many (many!) people who would like to do the same. From friends to random people on LinkedIn, I always hear myself give the same advice. So here it is, my story.</p><p>My personal heavy mountain was my previous career in Finance. That felt like walking Mount Everest on a bad day. I had just finished my master’s in International Financial Management, and I worked at a bank in London. Everything seemed great, I had a good job, a great salary, and a nice apartment in a popular neighbourhood. But there was one thing missing: I was not happy. It was like walking up that mountain with a heavy backpack and flip-flops on my feet. With every passing day, the backpack felt heavier, and heavier. Both my study and my career were successful, but it took all the energy and happiness that I had.</p><p>So one morning, I was sitting at my desk, doing exactly the same thing as I did every single day, and I thought to myself: <em>Is this what I am going to do for the rest of my life? Am I going to keep listening to that voice in the back of my head that tells me I need to persevere just a little while longer?</em> I decided that I couldn’t do it anymore. I needed to walk back down that mountain.</p><p>I quit my job, moved out of my house, and back to my mum’s in the Netherlands. There I was, standing in the middle of many mountains. I often lay awake at night thinking: I have no job, no income, no house. What am I going to do next? Even worse, what will people think about me not working? Because opinions were voiced by many around me. Why would she stop working? Only because she is not happy? I felt like I needed to know what my next steps would be, but I didn’t. I had no idea which mountain I needed to climb. And on top of that, I knew that with any new career I would have to start over as a junior, and with that would come a significant pay cut. But for me, those reasons did not outweigh the struggle of the climb.</p><h4><strong>So, how did I get into software engineering?</strong></h4><p>I had never learned anything about programming, heck I didn’t even know what HTML was (I know, I still don’t). But a few years earlier a little seed was planted during an internship, and every time I met someone who told me they were a software engineer, I thought to myself: <em>Damn that’s cool.. I wish I could do that.</em> Eventually, it took my therapist to ask me why I didn’t give that a try.</p><p>Why not, I thought, and very slowly I started to climb a second mountain. I signed up for a programming boot camp, and step by step the path became brighter, sunnier, clearer and easier. The amount of energy I felt while growing in engineering was something I hadn’t felt before.</p><p>Suddenly, the path up the mountain was much easier to climb. I had lost my heavy backpack and was finally wearing those comfortable hiking boots. That is when I realised: fast growth comes with doing something you like. Fast growth comes with <em>passion</em>.</p><p>A couple of weeks ago I read a sentence in a book that said:</p><blockquote>“Studies have shown that people who attack their work with passion experience flow, a euphoric, effortless state of mind that is five times more productive than the norm.”</blockquote><blockquote><em>The Bullseye Principle, 2018, David Lewis &amp; G. Riley Mills</em></blockquote><p>Take that in for a second. <em>Five</em> times more productive, and all while doing something you like!</p><p>Okay, so this almost starts to read like a motivational text, right? Find your perfect mountain and get huge piles of productivity, yaay! *<em>Insert jazz hands</em>*</p><p>But how do you know which mountain is the right one? Very simple. You don’t. Because it’s not about finding the optimum mountain to climb. It’s about trying a few. Be curious about the things you’re interested in, and try them out.</p><p>I listened to a podcast the other day where someone said: “<em>Specialisation is for insects</em>”. Now, that might be a bit too strongly formulated, but it does have a point: don’t try to specialise too early, don’t try to grow as fast as possible in one profession so you will earn lots of money and get a high position as soon as possible, only to realise you don’t even really like what you’re doing! This is not that uncommon, there is even a name for it: Quarterly Life Crisis. It basically means every person approaching 30 goes through this. But this feeling can of course occur at any time in your life, even when you’ve passed your thirties a long time ago, and there are kids and a mortgage to think about, which make it even scarier to lose any form of stability:</p><p><em>Diversify, be curious and try different paths. And sometimes, have the courage to walk back down a path.</em></p><h4><strong>The wonders of PowerPoints and Excel</strong></h4><p>So what can we do to help others try out different paths? Unfortunately, engineering is still not taught in most high schools, so many kids don’t get any introduction to this field. I don’t know what your high school IT class was about, but mine taught me the wonders of PowerPoint and Excel. So for a long time, I had this dream to excite more kids about choosing a study and career in engineering, especially girls. This summer, that dream is finally coming true. Together with Mollie I will organise Codeo, a 4-day summer camp for high school kids to introduce them into the basic principles of programming.</p><p>To plant that little seed I had years ago, and maybe for some, this will be their first step on their sunny mountain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=978cd1ef150b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mollie-payments/stories-from-a-career-dropout-978cd1ef150b">Stories from a career dropout</a> was originally published in <a href="https://medium.com/mollie-payments">Mollie</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineers vs The Business: How to settle the battle of technical debt]]></title>
            <link>https://medium.com/mollie-payments/engineers-vs-the-business-how-to-settle-the-battle-of-technical-debt-109b822a0bb0?source=rss-827d21345814------2</link>
            <guid isPermaLink="false">https://medium.com/p/109b822a0bb0</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Femke Buijs]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 08:40:14 GMT</pubDate>
            <atom:updated>2021-08-30T14:05:32.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLZKprzWyRDLXj1t3uoYDw.png" /></figure><p>A couple of weeks ago during the first product engineering all-hands meeting of 2021, my heart, along with that of many other developers, leaped. We learned that one of our main priorities for 2021 is to pay down technical debt. YAY! Often this subject is hard to promote because for non-engineers the value this adds to the business can be difficult to measure. There is no fancy new feature or product you can show, and you can’t expect applause when you say ‘Hey, we worked on some technical debt in the past few months!’. However, continuously working on getting rid of and preventing technical debt is as important, or even more important as some would argue, than adding new features. But how can this be demonstrated to the management team, sales, and the wider business?</p><p>Recently I watched a presentation by <a href="https://www.linkedin.com/in/corinnewaltersopdyke">Corinne Walters Opdyke</a> (Director, Technical Program Management at Mastercard) where the concept of technical debt was explained in such a clear and understandable way, I would like to share it with you.</p><h3>Technical debt and the dirty kitchen example</h3><p>Technical debt can be explained by comparing it to a dirty kitchen and can be divided into two types: intentional and unintentional technical debt.</p><p><strong>Intentional technical debt<br></strong>Imagine a group of guests are coming over to your house to have dinner. You cook them a great meal, but because you would like to enjoy their company instead of doing the dishes, you decide to clean the kitchen at a later point. The next morning, you get out of bed to make some breakfast, but the kitchen is still dirty. You can choose to take some time to clean the kitchen first and then make your breakfast, or you can choose to prioritize your next meal rather than dealing with your last. However, in the latter case you need to work around the mess because you’ll have less counter space, a full sink, or not the right utensils because they are still dirty. This, as you can imagine, will slow down the process of creating your next meal (<em>feature</em>).</p><p>The time it takes to clean the kitchen or the extra time it takes to work around the mess is your intentional technical debt. The <em>intentional</em> decision not to clean the kitchen on the day you were cooking might have been efficient at the time but has eventually cost you or the next person using your kitchen (<em>codebase</em>) sometime in the future.</p><p>According to <a href="http://www.iceaaonline.com/ready/wp-content/uploads/2015/06/SW11-Paper-Minkiewicz-Technical-Debt.pdf">Arlene Minkiewicz</a> (Chief Scientist at Price), it can be explained as follows:</p><blockquote><em>Technical debt, the metaphor: Borrowing from the future to satisfy the now</em></blockquote><p>Alright great, so what does that mean? While creating technical debt you are buying time at the expense of stability, quality, scalability, and functionality. In the back of your mind, you’re thinking you’re going to get rid of this debt (<em>the dishes</em>) at some point. It’s all those quick and dirty feature implementations, code duplications, lack of modularisation, code that works but nobody understands how, lack of tests or documentation, and all other things developers know aren’t a good idea but do them anyway because they don’t have the time to fix these contributions to technical debt. For all the engineers reading this: just for fun, try a total search in your codebase for ‘@todo’. Your editor will probably give you a ‘100+ matches’ because it doesn’t even bother you with the total amount.</p><p><strong>Unintentional technical debt</strong></p><blockquote><em>Technical debt, the measurement: Anything that’s causing drag, even unintentionally</em></blockquote><p>In other words, something you did or implemented that had an unforeseen or unknown consequence has resulted in unintentional technical debt. This can be explained as ‘all current violations of good coding practices’. Good coding practices change over time, so whatever you wrote a couple of years ago might have been adhering to the greatest coding practices at the time, but now just sits there in your codebase violating current coding practices. You didn’t choose for this to happen, just like you didn’t choose for your packages to need updating or the browser version you based your web application on to go out of date. Furthermore, business requirements change all the time. I don’t believe there is a developer in the world who hasn’t bashed on other peoples’ code, but wasn’t that code probably following business requirements at the time it was written?</p><p>In the kitchen example, this doesn’t just result in a couple of dirty dishes. Imagine you’re a great chef and you often host some great dinner parties with your friends. However, at some point, you realize the kitchen utensils you have been using and which were the brightest new thing on the market at the time, have now been improved. The knives you have been using all along are now outdated compared to the new self-sharpening knives on the market, and not adapting means you can’t cook as dynamically or as efficiently as you could (<em>outdated packages, improved coding practices</em>). Additionally, your favorite pot has a broken handle and the blender you carefully chose to buy a while ago is not a good fit for your needs after all (<em>non-optimal supplier/package</em>). Oh, and that pasta machine you have because your guests just looove pasta? Well, they prefer rice now, and people are wondering why on earth you bought a pasta machine in the first place (<em>changing business requirements</em>).</p><p>These kitchen utensils that require maintenance are your unintentional technical debt. None of it was planned, it happened <em>unintentionally</em>, but it requires updating nevertheless.</p><h3>Settle the battle</h3><p>Now that we have clarified the types of technical debt, what can we do to get engineers and the business more aligned? The key here is to find a shared understanding and a balance between short-term wins (new features and quick fixes) and long-term goals (product stability, scalability, and functionality).</p><p>For the business, it is key to understand what technical debt <em>is</em>, but also to understand the consequences of leaving it unattended. These consequences are not just faced by engineers, they harm the business as a whole as it can impede the ability to launch new features (product velocity) or eventually even touch customers when technical debt turns into product debt: slow and/or buggy products.</p><p>For engineers, it can be useful to bridge the communication gap by trying to describe technical debt without ever using the words ‘technical debt’. For example, ‘<em>there are some great new features in this package that we would like to use because it could add value to our business in this and that way, but we need to update it in order to get them</em>’. Or ‘<em>we chose to build this feature quickly so we could sell it to our customers, but some of the code is written a bit awkwardly because of this and could lead to some stability issues in the future, so we would like to take some time to fix that now</em>.</p><p>Either way, it’s important to keep in mind that technical debt in itself is not necessarily bad. Every developer knows software doesn’t come out perfect on the first try, it’s continuously evolving. Even if it is perfected at some point, it will not stay that way for long. Technical debt arises with change, and change is inevitable. However, the longer the technical debt stays untouched, the higher the cost will be to fix it.</p><p>So back to our kitchen example, where did we leave? The question is simple. Do you want to make it a habit to gradually improve the dirty or out-of-date kitchen, or leave it so messy that the cost of adding a new feature or fixing a bug becomes so complicated that a single code change breaks everything?</p><p><strong>Interested in getting to know more about our current engineering challenges? Get in touch </strong><a href="https://jobs.mollie.com/"><strong>HERE</strong></a>, <strong>we&#39;ll be happy to have a chat and tell you more! 🙌</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=109b822a0bb0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mollie-payments/engineers-vs-the-business-how-to-settle-the-battle-of-technical-debt-109b822a0bb0">Engineers vs The Business: How to settle the battle of technical debt</a> was originally published in <a href="https://medium.com/mollie-payments">Mollie</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>