<?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 Sergi Juanola on Medium]]></title>
        <description><![CDATA[Stories by Sergi Juanola on Medium]]></description>
        <link>https://medium.com/@sergi.juanola.c?source=rss-e7bce92c16b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*MhDoxCNAW-RanKbj</url>
            <title>Stories by Sergi Juanola on Medium</title>
            <link>https://medium.com/@sergi.juanola.c?source=rss-e7bce92c16b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:42:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sergi.juanola.c/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 most important questions to ask before accepting your next tech role]]></title>
            <link>https://medium.com/bumble-tech/the-most-important-questions-to-ask-before-accepting-your-next-tech-role-ebc0830842b9?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebc0830842b9</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[tech-interview]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Wed, 29 Mar 2023 09:11:36 GMT</pubDate>
            <atom:updated>2023-03-31T16:09:25.318Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYkFzV3fRBdxw1go7Zudgg.png" /></figure><blockquote>Disclaimer: The contents of this blog are not a commitment of Bumble’s employment conditions.</blockquote><p>Getting the answers you want to hear from a prospective employer has a big impact on whether or not you’ll choose to work there. We’re talking about going beyond the obvious: “what’s the salary”, and finding out vital information that could save you from a role that isn’t the best fit for you.</p><p>Of course, most companies won’t provide everything on your wish list, but this should help you understand what’s most important for you.</p><h3>Ethics and principles</h3><p>When considering a new tech role, it’s really important to find out whether the heart of the company aligns with your ethics and principles.</p><ul><li><strong>How do you offset your environmental impact?</strong> With climate change becoming more and more of an urgent concern, what steps are they taking to reduce their carbon footprint? A large company with a comprehensive sustainability initiative, or small company making small efforts like reusable cups and minimal air conditioning could be a good indicator.</li><li><strong>What’s your data protection policy?</strong> Would you entrust your own data to this company? If not, this could be a red flag.</li><li><strong>How much parental leave do you provide?</strong> If you’re thinking of having a baby (or already in the process: congratulations!), it will be really important for you in the short term. It’s also a good indicator of their approach to gender equity in tech.</li><li><strong>What’s your overall approach to diversity, equality, inclusion, and belonging?</strong> Equity for all is beneficial for everyone, not just underrepresented communities, although support for those groups should always be a priority in an ethical organization.</li><li><strong>What do you do with old devices?</strong> Some companies will simply store them until they rot. This is e-waste. If they’re still usable, some companies sell them at a discount or give them away to people who need them.</li><li><strong>How does the company protect my health?</strong> This goes beyond physical health coverage, to mental health support. It might also include HR policies that protect you against any employee behavior that is not desirable!</li></ul><h3>Perks and freedom</h3><p>Of course, a competitive salary is important, but if the difference between different tech roles isn’t too significant, dive deeper.</p><ul><li><strong>What’s your pension offering? </strong>The flexibility of this could be as important as the contributions when thinking about your future.</li><li><strong>What are your offices like?</strong> With workforces becoming more and more distributed, it’s worth asking this if office life is important to your happiness and productivity.</li><li><strong>What’s your approach to flexible/remote working?</strong> If your personal circumstances mean that flexible and/or remote working is best for you, understand their policy and how it plays out day-to-day.</li><li><strong>Do you allow working from other countries?</strong> Many companies now offer the option of spending some time working abroad, which could be beneficial for you if you’re from overseas or have family you’d like to visit.</li><li><strong>Which well-being perks do you offer?</strong> It’s now more and more common for companies to support the costs of exercising and well-being in general.</li><li><strong>Do you organise team-building activities?</strong> Find out what they are!</li></ul><h3>Continuity and growth</h3><p>Just like a broadband provider, an employer might bamboozle you with offers at the beginning, but make sure they’re going to be able to help you stay motivated in the long run.</p><ul><li><strong>What will my first month look like?</strong> Understand your onboarding process, and whether that will suit your learning.</li><li><strong>How do you encourage writing articles and speaking at conferences?</strong> Companies that embrace this kind of mentality might be more open and transparent generally, and means that they want to engage in your community. They may even compensate you.</li><li><strong>What are my possible career paths?</strong> You may like your position today, but at some point, you may ask yourself if this is the end of the road, or how you can climb the ladder. Coaching others, leading a team, being the expert in a specific topic, or deciding the future of a product are important aspects of understanding where your path is heading.</li><li><strong>Do you offer paid courses?</strong> Will the company support you financially as you wish to grow your knowledge? And is there a minimum term you need to meet to be eligible?</li><li><strong>How do you do performance reviews? </strong>Find out how you’ll realistically achieve your career plan. You may only be eligible for promotions or salary increases at certain times. You might also want to find out whether 360 reviews are in place, where you’re also able to give feedback to your peers and managers.</li></ul><h3>Ways of working</h3><p>Knowing the basics of what you will end up doing is pretty important, but you’d be surprised how many times we skip the most important questions.</p><ul><li><strong>What’s your release policy?</strong> Whether you’ll be doing this yourself or not, knowing the release policy (For example, They never release on Friday, everything’s automatic by default, or nothing untested goes to the next release) can give you peace of mind.</li><li><strong>What is your policy on open (or closed) source projects?</strong> Many times, personal growth also means that you want to expand your knowledge and abilities outside of company time. It’s important to find out whether you’ll be able to use company time and resources on open source projects, and understand their open source policy.</li><li><strong>What happens when a bug is detected?</strong> If a spotless product is priority number one, workloads could change frequently as bugs need to be fixed, which can make for a bit of a hectic culture. That might be right for you, but it’s good to know in advance.</li><li><strong>How do you determine when a task is done?</strong> If the terms ‘Definition of Done’, ‘Test Coverage’ or ‘Peer Review’ bring a smile to your face, make sure you find out which of these are part of your potential employer’s process.</li></ul><h3>To wrap up</h3><p>I hope these questions serve as a good start for you to think about what’s important to you when choosing your next employer. And naturally, you’ll probably want to add some that are more specific to your circumstances. We can also hope that it’ll give tech companies an idea of what’s important to attracting awesome talent like you!</p><blockquote>Have questions or feedback? Let me know in the comments or reach out to me on <a href="https://es.linkedin.com/in/sergijuanola">LinkedIn</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebc0830842b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bumble-tech/the-most-important-questions-to-ask-before-accepting-your-next-tech-role-ebc0830842b9">The most important questions to ask before accepting your next tech role</a> was originally published in <a href="https://medium.com/bumble-tech">Bumble Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You’re worth more than your Impostor Syndrome wants you to believe]]></title>
            <link>https://medium.com/bumble-tech/youre-worth-more-than-your-impostor-syndrome-wants-you-to-believe-8b6c0efda80e?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b6c0efda80e</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[impostor-syndrome]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 11:11:39 GMT</pubDate>
            <atom:updated>2023-01-20T11:11:39.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A picture of the author" src="https://cdn-images-1.medium.com/max/1024/1*z6NzsGVKWVTlVN_LOJCSeg.png" /></figure><p><strong>Disclaimer: The information in this article is not intended to be a source of medical advice or analysis and does not constitute medical advice.</strong></p><p><em>You stare at your task, and ask yourself how they let you into the office in the first place. Other people seem to be busy, they’re probably smarter and more experienced than you. They’d finish in time, yet here you are, wishing you were at home because, clearly — you’re not qualified. “What was the Recruiter thinking? I’m in over my head”.</em></p><p>We’ve all been there, and even if you’re consistently delivering your tasks, this feeling returns. It’s important to remember that this voice is your Impostor Syndrome speaking. But when did it start? And how can you challenge it? Here are some findings of my own personal experience with Impostor Syndrome.</p><h3>Where can Impostor Syndrome come from?</h3><p><a href="https://impostorsyndrome.com/">Impostor Syndrome</a> is that diminishing feeling of incompetence towards a goal, and the sensation that you aren’t qualified to meet the requirements. <a href="https://www.verywellmind.com/imposter-syndrome-and-social-anxiety-disorder-4156469">Even with past success, you’re convinced that you don’t deserve the position you have</a>. The good news is: You’re not alone! Let’s explore its potential origins.</p><h4>Others</h4><p>Somebody tells you that you can’t do something. Whether their intentions are pure or not, don’t assume that they know more about something than you do.</p><blockquote>An example from my personal experience, is when at a previous company, I suggested a project change which would involve my switching roles. I was well-prepared, ready for any challenges. When my manager said “no.”, and offered no explanation. I felt that my ideas were worthless, and that kept me captive for years. I was really unhappy, but didn’t think I deserved better.</blockquote><p>After some time, and at a new company, I went ahead with this role change, and proposed the same change with great success. My past self would have been really proud!</p><h4>Yourself</h4><p>You keep repeating to yourself: <em>I’m not good enough</em>. One day, a task that you’ve done many times seems totally unfamiliar. The more you look at it, the less achievable it appears. Enter: The flight feeling.</p><p><em>I was wrong, they’ve mistaken me for somebody else, I shouldn’t be here.</em></p><p>What you need to know though, is that instead of fighting this feeling, you need to get to know it. This way, you can take advantage of it. We’ll explore that later.</p><h4>Knowledge gaps</h4><p>There might be times when you feel you’re not up to a challenge, and sometimes, you might be right!</p><p><strong>No one has all the knowledge</strong>. We’re all learning, all the time. We can thank books, mentors, successes and failures for that. Little by little, our experience grows, and it’s normal to find ourselves in front of a problem we’ve never faced before. This, however, doesn’t mean it’s the end of your path, it’s just something you’re yet to learn!</p><h3>How do I challenge my Impostor Syndrome?</h3><p>Understanding why your Impostor Syndrome is kicking in can help you to manage it.</p><h4>Stay away from external triggers</h4><p>Triggers can take many forms: words or even body language from others. Once you can identify them, you can manage your exposure to them.</p><p>Professional relationships, whether it’s with co-workers or clients. The individual may not have anything against you personally and their triggering you could be down to their communication style, or lack of understanding that there’s a human being behind the task. Speak to someone you trust, like a line manager, mentor or your HR representative, so that you can manage the relationship with minimal impact on your self-esteem. You might also want to think about whether this is just part of your company’s culture, in which case, it could be time to move on.</p><p>Friends and family members. Hopefully, you feel able to open up to that person about your triggers. You might need to ask them to put some extra trust in you. If they choose not to, you’ll want to think about implementing boundaries in that relationship.</p><h4>Remember that there’s always more to learn</h4><p>You’ll always have new challenges to face, and that will inevitably bring times when you feel puzzled. Remember that the feeling of discomfort is a positive thing, and it’s helped you to get where you are today. The road ahead might be steep and long, but it’s doable — you’ve done it before!</p><p>At times when you feel totally capable of solving a problem, it might be because you don’t know what you don’t know! This is the <a href="https://www.britannica.com/science/Dunning-Kruger-effect">Dunning-Kruger effect</a>.</p><p>Realizing that you don’t know everything, means you’ve deepened your understanding. Keep learning and working. <a href="https://youtu.be/RVmMeMcGc0Y">Fake it till you become it</a> — everyone does!</p><h4>Know that someone has placed trust in you</h4><p>Somebody has noticed that you’re capable.</p><p>Sometimes, feeling like an impostor just means that someone has more faith in your ability than you do, based on what they’ve seen from you. Give yourself a pat on the back!</p><h4>It means you care</h4><p>Would you worry about not being capable of something if you didn’t care? Impostor Syndrome is closely linked to fear of failure.</p><p>We want to impress others, get the best out of ourselves and get that dopamine hit when we successfully complete a task. Knowing that we may not succeed is scary but is just a small pebble in the path.</p><h4>Learn from your mistakes</h4><p>You slipped and something went south. <strong>Don’t worry, mistakes happen every now and then</strong>, even to the most experienced people. What can you learn from it? You won’t make the same mistake again.</p><p>If something’s still not clicking, read a book, take a course, or meet an expert.</p><h4>You don’t need to know everything</h4><p>When you’re past the downwards curve in the Dunning-Kruger chart and are already an expert, your Impostor Syndrome won’t disappear!</p><p>That’s because there’s always something new to learn, but you don’t need to know everything. Embrace the joy of missing out on learning, accepting that you cannot know everything and your time isn’t limitless. One day you’ll notice that your Impostor Syndrome is a little quieter. And when it inevitably returns, refer back to this guide or other resources!</p><h3><a href="https://www.phoenixperform.com/single-post/18-famous-imposters#:~:text=Tennis%20phenom%20Serena%20Williams%20said,become%20the%20person%20I%20am.%E2%80%9D&amp;text=We%20(Brad%20%26%20Tom)%20each,with%20imposter%20syndrome%20for%20years.">You’re not alone</a></h3><p>Here are just a few examples from some successful ‘Impostors’! Serena Williams would often copy her sister.</p><blockquote>There were two Venus Williamses in our family. It was crazy… my parents would make me order first, but once she ordered, I’d change my mind. It was tough for me to stop being Venus and become the person I am.</blockquote><p>Tom Hanks.</p><blockquote>No matter what we’ve done, there comes a point where you think, ‘How did I get here? When are they going to discover that I am, in fact, a fraud and take everything away from me?’</blockquote><p>Tina Fey understands that you need to embrace Impostor Syndrome in all of its phases.</p><blockquote>The beauty of the impostor syndrome is you vacillate between extreme egomania, and a complete feeling of: ‘I’m a fraud! Oh god, they’re on to me! I’m a fraud!’ So you just try to ride the egomania when it comes and enjoy it, and then slide through the idea of fraud.</blockquote><h4>It happens to the best</h4><p>Joana Estafanell, a talented Android Engineer I have the pleasure of working with, has also gone through this.</p><blockquote>I’m very demanding with myself and realizing the huge quantity of knowledge I don’t know is really challenging. I try to remember that I would never place these demands on my colleagues, and then try to treat myself equally.</blockquote><blockquote>I’ve learnt to make two exercises:</blockquote><blockquote>- Be actively aware of the things I don’t know and that I choose not to know. It helps me realize that it’s not all worth my attention, and makes me feel freer.</blockquote><blockquote>- Be actively aware in what areas I’m better than others, in a healthy, self-rewarding way. It helps me realize that I add value to the team.</blockquote><h4>I’ve been there (and I still am!)</h4><p>I love that I’m not the best at everything on my team. I still have so much to learn. But Impostor Syndrome still gets the best of me at times. For some context, I started my professional career as a Backend Developer. When something about this wasn’t feeling quite right, I decided to become a Full Stack web Developer. I still didn’t feel I was pushing myself to my limits, so I decided to shift to Android. At this point, someone told me I wouldn’t be able to make such a leap in my career, and that had a massive impact on me for the next couple of years.</p><p>After some really negative interview experiences, I realized that I needed to trust in myself and my abilities, whilst acknowledging that I’m not perfect. That did the trick and helped me land my first Android developer position.</p><p>I’m still working as an Android Developer, learning more and doing something I can do well, because I’ve also been there: telling new joiners that having Impostor Syndrome is okay if they can benefit from it, just to remember that they deserve to be here.</p><p>Working as a mentor and buddy has welcomed a new Impostor Syndrome into my life (<em>am I making sure this person is safe here? Maybe somebody else should be doing this!</em>). But I have a beautiful path in front of me, an opportunity to learn.</p><h4>Ask for help</h4><p>Hopefully you now know a few things, now; Impostor Syndrome is something that persists in our everyday, it can be used as something positive, but symptoms should always be under control to some degree.</p><p>If this feeling is causing you more than spare moments of doubt in yourself, it might be time to seek further help in the form of counseling or therapy.</p><h3>Let’s wrap it up</h3><p>Impostor Syndrome can be a threat to your development and mental health. Whether it comes from others or ourselves, it may affect us in the deepest parts of our mind, and it’s very difficult to manage. If we can consciously control the negative feelings and take advantage of the positive ones, it can be a powerful tool for personal improvement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b6c0efda80e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bumble-tech/youre-worth-more-than-your-impostor-syndrome-wants-you-to-believe-8b6c0efda80e">You’re worth more than your Impostor Syndrome wants you to believe</a> was originally published in <a href="https://medium.com/bumble-tech">Bumble Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Take over your job position before it’s too late]]></title>
            <link>https://medium.com/@sergi.juanola.c/take-over-your-job-position-before-its-too-late-8bd925409dd0?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bd925409dd0</guid>
            <category><![CDATA[quitting]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 17:07:07 GMT</pubDate>
            <atom:updated>2022-11-17T17:07:07.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6Aw7qWqwlGyH8hBa" /><figcaption>Photo by <a href="https://unsplash.com/@villxsmil?utm_source=medium&amp;utm_medium=referral">Luis Villasmil</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A job position at a new company is pretty much like any other relationship: you fall in love with the company and see nothing but perfection. Then you become aware of the very few traits that make that company special, either good or bad, but still, they make it look “cute”. After that moment, you may start feeling that those traits are in fact problems which make you consider if that’s what you really want, so you are willing to make changes in the ones that it’s possible to improve the situation and change your mindset in those that it’s not possible, but you may feel relationships with other people might be a good thing to think about. Finally, the issues outnumber the benefits and you decide it’s better to cut connections and move on.</p><p>It’s always better that these final steps never happen, but it’s also better that, if they ever happen, you catch it on time and end it yourself before it ends you. However, there is one way you can follow to avoid your position rots and turn it into a wonderful growing being. Let’s delve into a wonderfully weird term I call “the quittometer”.</p><h3>The quittometer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*45uvGJzHb3j-EopR" /><figcaption>Photo by <a href="https://unsplash.com/@justusmenke?utm_source=medium&amp;utm_medium=referral">Justus Menke</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever seen a pressure gauge? They range from zero to the maximum they can measure -and not the maximum they can withstand. They tend to have some “safe zones” (where there’s enough pressure to sustain their purpose) and some “danger zones” (where if you add some extra workload, it could blow the whole machine). Now, imagine a gauge that could measure how well you feel at your job position.</p><p>What does <em>well </em>mean? It depends on each person. It might be money, safety, teammates, ability to make decisions, career projection, extra holidays, work from anywhere, informal Fridays, or a mix of some. You name it. The important thing here is that the definition of well is yours only, and impossible to compare to anybody else’s. So even if somebody in your same position is living their dream, something could still not click for you, and that would be perfectly normal.</p><p>Imagine this gauge ranging from 0 to 3, where 0 is “I can stay here forever” and 3 is “I need to leave now”, and they seem to look like stages in your job position -although not necessarily. Let’s dig a bit into these numbers:</p><p><strong>Stage 0: I can stay forever</strong>. Congratulations. Your position is fantastic, you feel great and calm and it meets all your requirements. The people are enthusiastic and knowledgeable. It even has extra benefits you didn’t consider in the first place! Your teammates are awesome and your manager is understanding and cares about you and your future at the company, and your company and its goals are in line with yours. This is the ideal position, the one we all want to stick to for our whole life.</p><p><strong>Stage 1: I see it’s not perfect, but I’m okay with it.</strong> Even the greatest companies have some sharp corners you don’t quite align with or like. The same list you can do to define “well” has its counterpart. If something on that list is not met, you may see that as something negative. It’s not necessarily <em>that</em> negative, but it’s undeniably on the table, now that you noticed it. Sure, you can still navigate your way into the company, and enjoy your job position and all the people around you and the advantages it brings, but to put it simply, the company has its lights and shades.</p><p><strong>Stage 2: I don’t feel comfortable, so I want to change.</strong> Is some new gig not in line with you? Some bad habits from others crawling you? Are some expectations unfulfilled? Okay, let’s be honest. Not all companies are perfect, and some of them will let us down after a few years down the road. Sure, some of the perks are awesome and still there, but overall, the vibes that made you feel butterflies in your stomach when you started are long gone –and seem never to come back. You may believe at this point that it’s over, and there’s no way to come back to some peace in your situation. You may start thinking of a change -either the company’s bad habits, yourself or your job position- and that’s normal and healthy.</p><p><strong>Moment 3: I need to leave now.</strong> Something (expected or unexpected) happened, and yes, that was the last straw. You are working here against your will, and some of these feelings point you towards the closest door and move your feet as fast as they can. Just like in a pressure gauge, this moment is a split second of the pointer moving past the scale maximum, past the “danger” area, just a split second before the whole machine explodes. At this point, there is no way back. It’s like you’re on the river and can see the waterfall in front of you. Your only escape is pulling that liana, even if it ends up being the tail of a tiger. Better that than falling down the cascade -at least for now, you can fix that issue when there’s not a 100m fall in front of you anymore. Sadly this is the moment you even consider quitting before having a plan B, another company waiting for you after your off boarding.</p><p>Turns out that during your career, you’ll be jumping between these numbers all the time, and oftentimes they will change because you are actually switching jobs, but other times they will tip towards other numbers while you haven’t changed yet. In many cases, you’ll see yourself going from 0 up to 3 in a single position, like that’s the norm. This shouldn’t be.</p><p>Being on stage 0 is fantastic, but unrealistic for a long period -unless you found the holy grail!-, and you’d normally find yourself on stage 1: you can’t check all the items in your wishlist, but admittedly, you’re in a pretty darn good situation. Stage 2 gets risky, and being there for quite a long time might mean you want to leave, and if you don’t try to revert it, in most cases it will organically evolve into moment 3, too late to recover from that. It’s a blink of an eye, a moment so short: you’re way past the burnout, and for your health, if you can leave you must do it now.</p><p>If you’re already into moment 3, time to move on, but if not, nobody told you there was no way back. See, when the pressure in the machine is above normal levels, you do anything you can to pull it down. Your professional life should be no different than this, and you can recover from feeling burned out to understanding some problems are out of your control, and others are manageable.</p><h3>Back from stage 2.9 to 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*haWcTv7qsDen7vDB" /><figcaption>Photo by <a href="https://unsplash.com/es/@lucati?utm_source=medium&amp;utm_medium=referral">Amanda Lucati</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Like many things in your life, nothing goes from green to red in a second, this tends to be a long way between feeling great and feeling lost. In the same way here, there are 4 remarkable milestones, but there are gaps in between those numbers, filled with shades of those two colors, hinting that you’re way too close to feeling bad. Or, rather, consider them as warnings to put you back on track with a healthy relationship with your company.</p><p>Feeling burned out at a company is detrimental for everyone: you don’t like working there so you start having your mind at another place, and the company is not getting as much work done from you as before. This means <strong>the company wants you to be happy there in the first place</strong>. A selfish reason, but still, a reason nonetheless. This means that if something can be solved, both parties should work their way to turn this relationship into a healthy one back like in the beginning.</p><p>What’s making these professional relationship’s gears not spin at full speed? Something that happened in the past, something happening right now, something about to happen. Something you feel, something other people feel. Only you know it, meaning you need to focus on understanding the problems, and later on gather up the courage to solve the solvable ones, and analyze the unfixable ones to see if they’re as important as they felt before.</p><p><strong>Become self-aware of what you can or not do.</strong> Not focused on knowing your skill limits, but rather understanding that you cannot take control of all that happens in the company. Do you feel you can control what others do? Surely if you’re their boss, you can pretend it, but let’s be honest, if you feel like so, chances are the problems come from above or from peers (although subordinates can make you feel like this too, of course). If you can’t control what they do, you could at least control how you feel about that. Take your time to make this your motto. Maybe that harsh move of your teammate to get a promotion you were fighting to get for such a long time was not an attack against you, but just your teammate willing to promote as well. Maybe that boss holding you responsible for a problem is just a reflection of themselves being unable to handle the problem in the first place.</p><p><strong>Work your way to demonstrate you’re good, even with the help of others</strong>. Did your peer get a promotion? Don’t be mad, ask them how they did it, more often than not, they’ll happily tell you (if the promotion was honorable). Take their advice as a guide on how to achieve it yourself. That was an example, but if you feel stuck and you know about something that could make the wheels turn at full speed again, go for it: ask about it to the people that can make this happen, look for advice from those who made it, learn about it, work as much as it feels okay and doesn’t worsen other aspects in your life…, just go for it.</p><p><strong>Put limits. Agree on them with the company</strong>. Did you work overtime? Did it bring any value to you? It surely brought value to the company, so they’ll ask you again. Did the company ask you to do something you felt was not right? Surely you’re now also responsible, and you know it. If this is such a big reason for you to feel like so (trust me, it can be), it’s better to talk about it to the company. Sometimes they can cover your position “requirements” with somebody else and switch you to that other’s spot. Don’t take it as a demotion, as I’m speaking about swapping some responsibilities between peers.</p><p><strong>It’s not that you stop caring</strong>. Everything said, it may feel like you should be a selfish person behind an uncaring shield. Far from it. You’re doing this because you still see good in this company. Make every moment in this company count, but also make it count for yourself.</p><p><strong>Talk to People and Culture (or to HR)</strong>. Maybe it’s not a situation, but a person, that makes you feel bad. Bad words, mistreatment, anything like that should be reported to the people’s department in your company. Maybe that person will be fired or warned with enough severity to make them stop. And most importantly, you need to speak up for those who don’t dare to.</p><p><strong>Understand that sometimes, there’s no choice but to leave</strong>. You did all you could, but something broke. Were those that could help you simply not willing to? Are your bosses or colleagues bullying you and HR doesn’t care? Was that project that you really wanted assigned to somebody else, just because they go get some beers with that manager? Maybe it’s time to leave before you need to.</p><h3>We’re on the same (patchy) boat</h3><p>I have, myself, been working for quite a while already, which means I have been in several companies and gone through these numbers a few times. Here’s what I had to live in my professional life so far, and how I tried to solve it (whenever it was possible).</p><p><strong>A company has suggested doing something I find against my principles.</strong> I was trained to do quite the opposite and what the company requested felt like it was going against the law. I didn’t really know how to handle that, but I tried pushing toward my principles, even to the point that I said that couldn’t be done -even though you could. 2 years later, some new rules were approved that would have turned this project down, unless it was made following the rules because of my confrontation. Being dishonest is not the best, but doing the correct thing seems to be the best option. Turns out that after some time, another fellow employee was tasked with something against his principles, and he swiftly said he wouldn’t do that because it seemed shady and he wouldn’t want to be prosecuted. Seemed so easy when he said so!</p><p><strong>A company has neglected any of my suggestions to improve a product in my experience niche.</strong> Long story short, a huge change would put one of the company projects in a very good position against its competition. The reasons seemed obvious to me, but management decided not to follow those suggestions and call them bad ideas over and over. This looked at the moment like the final nail in the coffin. The company didn’t want to negotiate any alternative, and this caused a lot of exasperation on my side. Since I was held responsible for the success of that project, I felt my boss just wanted a scapegoat to disassemble the project, and this burned me a whole lot. I decided that the best thing I could do would be to simply not care a lot about this topic, and trust the managers in their decisions to not progress on that. I cannot be held more responsible than I am if I cannot take decisions anyway. When this thought lit up, it was such a relief for me. Turns out that when I left the company, that project was archived, so, probably a decision my boss made years before that day.</p><p><strong>A company has decided to not approve a pay raise, despite there being money on the table and having been in talks since I was hired.</strong> During my hiring process, a company I wanted to work for said that they didn’t have much money at the moment, so the salary would be relatively lower than my previous job. I didn’t care at that time, since during my recruitment process, they promised the salary would be revisited in 6 months and raised to an agreed amount that was more favorable. This never happened, despite being promised several times, continuously mentioning that there was not enough cash flow yet. Time passed and it turns out there were loads of money going back and forth in the company. This got me thinking. You need to understand if that amount of money is enough to sustain your life and if that company is still good enough for you to continue working there. In my case, after I discovered this, I decided to start peacefully looking for other better options, just because a boss not telling the truth about that, might also be hiding other corpses behind the walls.</p><p><strong>A company rejected remote work, reasons unclear.</strong> I am a huge fan of working from home: I can work from my garden or my office, I have enough peace to work, and all the tools I need to use are available in a single laptop. My boss didn’t see it that way, though, so I wasn’t allowed to work remotely. I live pretty far from places with enough jobs, and I prefer it that way: cheaper rents, larger houses, gardens. Obviously, this is not an excuse for a company that is office centered, so this was rejected several times. This made me think about leaving the company, to the edge of being at stage 2.5. I decided to change their mind, so I used a good opportunity to work from home: some servers needed to be restarted and reinstalled, and to avoid bothering clients I suggested that it happened at night, at some time past 3 am (the valley hour with less active users). Since I couldn’t come to the office at 3 am, I suggested working from home that night and the following morning and calling it a day. It worked, and they saw enough value to consider it as a valid situation sporadically, enough for me to be granted remote work once a week.</p><p><strong>A company’s boss has called in on weekends, holidays and out of working time with urgent work to be finished by Monday.</strong> This was single-handedly something dangerous, as this becomes the norm after a short time. At a company I worked for, my boss started making decisions that went south several times, and called me on my personal phone to fix them on the weekends. I was even forced to go to the office on one occasion on Saturday. This, when you’re underpaid, feels very bad. I had to do something or else I wouldn’t be able to cope with that and would prefer to leave that day, so the same day that I had to go to the office, I met with him/her and had an honest conversation where I stated that, despite I went that Saturday, this wouldn’t happen again, as I value my and other people’s free time, and that something like that can be treated the following week without a big deal. Of course, this may not be valid for many cases, but if you work somewhere where the product can go off the rails even at night and this could cause a severe threat to the benefits, companies can decide to organize (and pay) night turns across employees.</p><p><strong>A company has dismissed any warning about some toxic environment in the team.</strong> At some point, a company I worked with had a person who didn’t collaborate to have a lovely and caring environment. Instead, the environment brought several people to have panic attacks and depression. When I saw this, I warned the company, but nothing happened. Everybody affected by any sickness caused by this person (and those around) was committed to telling the truth, but the company continually dismissed these comments and defended that the situation was not “that important” and that we could navigate through it. This led to one day when this person threatened me, so I reported this person, but still, nothing happened and it was treated like a “playground argument” and made both of us talk in private (which was not a great idea, as this person called me anything but pretty). At some point, during my offboarding, I was told that I was being selfish and ungrateful, as the company helped me with the situation, acting as a mediator with this toxic person. There are some moments in life when, whatever you do to solve an issue, might not be helpful or effective, because the problem is too rooted in that company. Better leave soon and in terms as good as possible (you never know) than too late.</p><p><strong>A company colleague that promised some help has decided to ignore me</strong>. This happened at a company where everything was awesome with everyone, but I asked a colleague how to begin collaborating on a project I really liked. This went okayish for a while, until all of a sudden, that person decided to ignore any communication from me. No bullying at all besides this absolute silence on their side. I tried to push this project forward as much as I could, asking for updates on their side, thinking that it became stalled for an external reason, until I began to see that other people were actually bringing this up and showing that they were part of this project after I asked to join it. Sadly, I asked about it one more time -still silent-, and then decided to move on. It brought me to a point where I was incapable of understanding why I wasn’t able to join this team, whereas others were happily joining it. As a suggestion, in these cases, if you’re the person accepting new people at a project you manage and somebody wants to join but you feel they’re not the right person or it’s not the right time for them, just tell them. At least they know.</p><h3>Conclusion</h3><p>It’s not always possible, but always strive to solve your differences with your current job. It’s pretty complicated in many cases, and simply impossible in a few of them. Speak to colleagues, ex-colleagues, friends and family about your issues. You may find out that others have been in the same situation as you are now, and this may help you find a peaceful state again. Or best of all, you may find out somebody’s going through the same problems you had in the past, and you may be able to share how to solve them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bd925409dd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A shield under the skin]]></title>
            <link>https://medium.com/@sergi.juanola.c/a-shield-under-the-skin-eba5bf1a9419?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/eba5bf1a9419</guid>
            <category><![CDATA[vaccines]]></category>
            <category><![CDATA[short-story]]></category>
            <category><![CDATA[science-fiction]]></category>
            <category><![CDATA[nanotechnology]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Sat, 22 Oct 2022 18:21:16 GMT</pubDate>
            <atom:updated>2022-10-22T18:21:16.164Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Disclaimer: This is a science-fiction story. Seriously, don’t get too crazy.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wmaLlQuHfjlq97Qf" /><figcaption>Photo by <a href="https://unsplash.com/@mufidpwt?utm_source=medium&amp;utm_medium=referral">Mufid Majnun</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A screen at the back of the room was maybe too loud:</p><blockquote>… with the fusion between Global Pharma and Aspen Robotics, the multinational has positioned ahead of its competition in the race of the so-called Last Vaccine. After Vizion’s clinical trials failed during stage 2, the only two companies that seem to continue to their last clinical stage are Global Pharma and Jacobson Medical. Now, Tom, I guess the weather tonight will not be as convoluted, right?…</blockquote><p>“Did you know?”, a grave voice asked, angrily.</p><p>“How could I know that? We’ve been here for 3 weeks straight”, another one replied, less grave and angry, while turning off the screen.</p><p>“Come on Lex, you know this is important” –he grunted as he was typing on one of the 2 wide screens he had on his desk– “Global buying AR gives them at least a 3 months advantage”</p><p>“And much more horsepower, Joe. AR has at least 2 automated known factories”, said Lex</p><p>Joe sighed, “Okay, let’s go talk to Jacobson”</p><p>Normally, in a 5000-employee company, being a regular employee and talking directly to the CEO is fairly impossible, but Lex and Joe rushed through the corridors, passing by dozens of labs with people in white coats smashing keyboards and checking large screens filled with small, incredibly similar windows. Those labs were named after diseases. The people in the Diphtheria lab were probably having a bad time, as their screens were all blinking in red.</p><p>When they reached the elevator, they hit the 55, the last floor. Joe was clearly more nervous than Lex. Joe is the leader of the pancreatic cancer team, and Lex is from another team but was moved to Joe’s after the rest of the team went to work for Global. She is also worried, of course, but she knows pretty well that their product will be better than Global’s. A friend of hers works for the Global team and they still need to solve a lot of issues.</p><p>When the elevator dinged and the doors opened, Mr. Jacobson’s secretary asked them if they had scheduled any meeting. Lex stopped by the counter, but Joe went through and opened the door, without knocking. The secretary had to fight between deciding whether stopping him or warning the boss. Finally warning the boss’ won in her internal fight and rang the phone, but a voice replied almost instantaneously:</p><p>“No need Cynthia, thank you”. He hung the phone and said, staring at his tablet: “What can I do for you, Mr…”</p><p>“Joe…” –and quickly corrected himself– “Dr. Joseph Derrick, Pancreas cancer lab, sir”. A few seconds later, Lex came in. “This is Dr. Alexandra Chang, temporarily Pancreas cancer lab too”. That <em>temporarily</em> hurt Lex a little bit. She had been there for 4 months already.</p><p>“Dr. Derrick, how could I help you?”, said Jacobson.</p><p>Joe explained what they saw in the news. Jacobson seemed to understand him, nodding while he was signing documents on his tablet. Lex explained her point of view and how Global was still behind them, even knowing that Joe wouldn’t trust that gossip. Jacobson then looked at them.</p><p>“Dr. Derrick, Dr. Chang, I am afraid I already took a decision”</p><p>Alison Rodriguez was peacefully doing her job, typing on the computer in front of her. Some counter was quickly rising. <em>Suite 91/91, 2884/19712 rules passed</em>. She was pretty happy with that output. For the last 6 hours, that number had been stuck on 2883. At last, she found out that the problem was not in the rule she wrote months ago, but rather in the code that the Core generated to pass it. “It happens from time to time”, she repeated to herself, “in the end, AI also makes mistakes”. all of a sudden, a knock on the door woke her up from the illusion of a solved enigma.</p><p>“Rody, do you have a couple of minutes?”</p><p>“Sure, Preston, let me first check it passes all the rules”, said Alison</p><p>“It’s about that. Please, come with me”, said Preston, this time with a trembling on his voice.</p><p>Alison quickly stood up and went with him to a meeting room. There were 3 people already there. Preston, who was another instructor like her, sat next to Alison. In front of them, Bill and Eddie Ougadou, the chiefs of security and quality and internally called by the employees as <em>The Twins</em>, as well as a woman in a black suit which, by the way she was behaving, was there as a listener.</p><p>“So, Rody, how is your day?”, said Eddie peacefully.</p><p>“Cut the crap Eddie” –quickly said Bill– “we’re in a rush Alison. You’re doing a great job and so, but we’re in a rush. Did you start the security rule suite?”</p><p>“Well, uhm” –Alison never liked Bill’s directness– “I–I was just finishing the parasites suite, security was the next one”</p><p>“Great. Is there a chance you can stay until late this week?”, Bill said, “We’d need to tackle the security part by the end of the month. The code’s already in the repository. We’re in a rush”, Bill kept repeating.</p><p>“Uhm”, said Alison, staring at Eddie. Eddie was evading her eyes. “I guess I could, but what do you mean the code’s already in the repository? Aren’t the rules meant to be the instructions for the Core to do it?”</p><p>“We have no time. I’ve tasked some developers to work on the security code, and then you can test it”, Eddie said, trying to look calm. Preston didn’t say anything, but his eyes were also evading Alison’s.</p><p>“Cause we release the product in 3 weeks”, Bill dropped.</p><p>Alison shocked, eyes wide open. “We what?”</p><p>The screen was on the news channel:</p><blockquote>Today is the 4th anniversary of the Last Vaccine, with which Jacobson Medical became the top pharmaceutical company. After the absorption of Global Pharma, the company has had to go through the anti-monopolistic tribunal and pay an astronomical fee of $25M, an apparently small amount compared to the price paid for the purchase of GP and the benefits the Last Vaccine has reported back. The Vaccine has reached 100% of the global registered population, thanks to the last campaign sent to third world countries during the past summer.</blockquote><p>Joe was rushing to Jacobson’s office. He got a call from his secretary, something about “the next vaccine’s update”. Joe knew nothing about that. He had been promoted a few months ago to Chief Investigation Officer. He was no longer in the lab, checking screens or preparing samples, but he still liked wearing the white coat. He was moved up to the 55th floor so, after the years, rushing to Jacobson’s office was no longer a challenge of any kind. Once he arrived, he greeted the secretary, like he had been doing since he moved up in the company.</p><p>“Good morning Cynthia, did Mr. Jacobson want to see me?”, he asked in his most well-mannered tone.</p><p>“Good morning Dr. Derrick. Yes, he is waiting for you”, also in a well-mannered, but also more natural, tone.</p><p>Once Joe came in, Jacobson was checking the surroundings through the only window. Despite the amount of money he earned, he still liked his shadowy office. “Ah, Joe. Have you ever wondered how I started in pharmacology?”</p><p>Joe was confused. “Good morning Mr. Jacobson. I don’t know”.</p><p>“Call me Alan, Joe. We’re on the same level, in the eyes of the committee.”</p><p>“Okay, Alan”, Joe knew he’d never get used to that. “I don’t know how you started”.</p><p>“I wanted to make money”</p><p>“Oh”</p><p>“Yes. Over the last decade, with the progress we had and the goals we met, I felt I’d like dealing with medicines”. He did a long pause. A dove was grooming its feathers while peeking inside the office. “But no.”</p><p>Joe was feeling uncomfortable in the office. He didn’t even sit down. He didn’t know what to expect from that backstory.</p><p>“I’ve had a lot of troubles with too many people over the past 4 years. The acquisition of Global Pharma was the last straw, but all the hospitals and health insurance companies wanting my head… it was not pleasant either.”</p><p>Joe’s heart was beating furiously.</p><p>“Have our nanobots discovered any new disease?”, Jacobson said.</p><p>Joe’s heart stopped beating for a second. “Uh, yeah, a few. Most of them viral.”</p><p>“Good, good”, Jacobson said as he turned to look at Joe. “We reached the two-year period for version 2, and I want the next vaccine update to be different.”</p><p>Joe didn’t say a thing.</p><p>“I will be locking down the social discovery feature.”</p><p>“WHAT? That’s by far the BEST feature of the Vaccine!” Joe’s heart went crazy. He knew that the vaccine itself wasn’t good enough, and the only thing that made it work in the first place was social discovery. With this, as long as you were close to people, all the vaccines would collaborate to analyze any strange behavior detected in the host’s body. According to Nature, it was <em>Evolution without the burden of eons</em>.</p><p>“Yes. We created such a perfect product that we can no longer monetize it”, Jacobson let out. “Didn’t you hear the news, Joe? We reached 100% of the world’s population. We can’t sell it to anybody else.”</p><p>“But babies are born every day! And… that’s no excuse to stop treating the people!”, Joe was feeling anxious. He was a doctor, after all. He studied to cure people.</p><p>“They will still be treated by the nanos. It’s just… it won’t work for future diseases”, Jacobson said that and stared back at the dove outside the window. It flew as soon as Jacobson looked at it.</p><p>“And how’s that gonna make money?”. Joe didn’t understand the purpose of a Last Vaccine that didn’t cure everything. “Do you plan on selling them a new vaccine?”</p><p>“Kind of. You know… during those long, exhausting conversations with the lawyers of many, many health insurances, yelling that I jeopardized their business model… it struck me.”</p><p>Joe was shaking. He didn’t know what to expect from that. Sweat drops were going through his forehead.</p><p>“What if each insurance company was selling our vaccine, but with a few modifications? Maybe one could sell the vaccine with social discovery again, maybe one could sell this with extra labs working on this… Nobody knows.”</p><p>“But that’s crazy! If other companies are modifying and selling our product, then what control do we have? Are we going to update the vaccine every two years as we’ve done?”</p><p>“That’s not something you should worry about. The technical team has stalled all changes planned for version 3 to focus on white labeling the vaccine.</p><p>Joe found out, all of a sudden. “What should I worry about?”</p><p>A screen was showing headlines of the latest hours:</p><blockquote>JACOBSON MEDICAL disassembles R&amp;D departments after employment regulatory order. Technical department preparing to white label LV.</blockquote><p>Lex quickly turned the screen off before Joe saw that.</p><p>“Don’t worry Lex. Nothing I didn’t know”, said Joe. He took a sip from his coffee. It was cold already.</p><p>“I can still try fitting you in my laboratory”. Said Lex, trying to sound caring.</p><p>“Lex, I’m fed up with labs for a while”, Said Joe while he was reaching for an apple. It was too ripe, but he took a bite anyway. It felt gritty as he was chewing it. “I’ll probably try teaching”.</p><p>“I don’t know hun, I believe you are a better investigator than a teacher”</p><p>Joe turned to look at his wife as he was taking a second bite of that apple. It was brown on the inside. He frowned, “What does that mean?”</p><p>“Well… patience is not your greatest trait”, said Lex, as loving as one could sound saying such a thing.</p><p>Suddenly, Joe’s phone rang. <em>Unknown</em> showed up on the screen.</p><p>“Who’s this?”, said Joe, with composure.</p><p>A robotic voice sounded through the earpiece.</p><p>“Ī ₭₦Ōฬ ĦŌฬ ŦŌ ǤĪ∀Ē JĀĊŌ乃ƧŌ₦ Ā ĿĒƧƧŌ₦”.</p><p>Somebody turned the volume up:</p><blockquote>… the closing price of today for JCBM was $5202.90, which saw an increase of +1.6. During the past 6 months, the trend has been steadily positive since the white labeling of Last Vaccine and the acquisition of 2 more pharmacological industries that were declared bankrupt.</blockquote><blockquote>After the purchase, Miranda Jacobson, the representative of Jacobson Medical, spoke about the dismissal of the technical department.</blockquote><blockquote>“Since version 3 of the Last Vaccine is technically an OEM from now on, and it will be health insurances taking care of future updates, we decided to focus on the fabrication part, which we still handle in favor of our third parties with all the safety measures required.”</blockquote><blockquote>“Do you think after purchasing 2 more competitors”<em>, somebody in the crowd said,</em> “Jacobson is closer to monopoly?”</blockquote><blockquote>“With the latest agreement of 2 major health insurance companies entering the LVOEM program, we decided to increase our staff. Even with that in mind, we acquired 2 companies that were filing insolvency not only to get more hands to work on our product, but also to save 200 jobs from being lost.”</blockquote><blockquote><em>Somebody with a phone in front of Miranda said</em> “What would you tell to the groups that said that they don’t want to pay another private company for a service they already got and was taken?”</blockquote><blockquote>“Rest assured that the work our third parties are doing with their own implementations is magnificent and superior to what we could have done ourselves.”</blockquote><blockquote>“The majority of them are literally applying the social discovery the company took from version 3, thereby giving no advantage but to recover the same features v2 had. Anything you could say about this?”<em>, tackled the same person with the phone.</em></blockquote><blockquote>“… no more questions. Thank you for coming.”</blockquote><p>“Good morning, Cynthia”, said Joe on the phone, “This is Joe Derrick. May I speak to Mr. Jacobson?”. Lex was lip-syncing every word.</p><p>“Good morning Dr. Derrick”, said gracefully, like when you run into a great friend from your past that, for one thing or another, didn’t find the time to call for over 3 years, “I am afraid Mr. Jacobson isn’t in his office now”.</p><p>“Come on Cynthia, we both know he almost lives there. I’m pretty sure he has a futon hidden somewhere. Just forward the call”, his eyes moved to Lex, “please.”</p><p>Cynthia hesitated, “Hold on.”</p><p>A click sounded. Then nothing. Then another click.</p><p>“Joe, how’s life?”</p><p>“As good as an unemployed man can be, Alan.”</p><p>“Don’t call yourself unemployed. I’m pretty sure the finance department is still sending you a retirement pension every month”, said Jacobson, and proceeded, “I’d like to be retired at 41 like you, but I’m late already.”</p><p>“I’m not calling to cry on your shoulder Alan, I have some serious questions to ask. It’s about the vaccine.”</p><p>“Come on Joe, I thought we closed that chapter years ago.”</p><p>“Just tell me, did the security team manage to patch v3?”</p><p>“The vaccine is safe. Don’t worry about it”, Jacobson said, visibly tired of the conversation.</p><p>“You didn’t answer. Did they ever manage to patch v3?”</p><p>“You should be thinking of living a peaceful, disease-free life with Dr. Chang instead of messing with something that you no longer have to manage. Look, do you want to go on holidays? How about Bali? First two weeks are on me.”</p><p>“Alan, just tell me social discovery was removed and not just disabled…”, Joe’s heart started beating faster. It ached a couple times.</p><p>“Joe, stop it right there. I’m starting to get sick of it, and you know it’s impossible, with the vaccine”, Jacobson tried to tell a joke, but it didn’t go well.</p><p>Joe couldn’t keep it to himself anymore, “Alan, they showed it to me.”</p><p>“They? Who are they? What did they show?”</p><p>“They showed a video of a young man dying on the street.”</p><p>“Well, sometimes social discovery isn’t fast enough to process and eliminate a disease…”</p><p>“He collapsed after they pushed a button.”</p><p>A lot of people were sitting around a table. The glass door was labeled as JM Meeting room 1.</p><p>“I’m sure many of you already know him”, Jacobson started saying out loud, “for those who don’t, Dr. Joseph Derrick, ex CIO of Jacobson Medical. Sorry for the short notice, but he has some serious news to tell.”</p><p>Everyone turned to Joe.</p><p>“I was contacted a few years ago by a group of people. They never told me their real names, just that they were called <em>The community.</em>”</p><p>Everyone nodded, as if it was a name they heard before.</p><p>“They kept saying they had tools to bring humanity to a purer state, and all that gibberish you’d hear from any sect. I honestly didn’t like what they told, but I kept listening, out of curiosity. They said they were close to breach the vaccine security but they couldn’t, because every new version was built with different security codes and they had to start over every time. Their real problem was that they didn’t have enough power to break the security codes that keep the social discovery and communications safe. Since there were no more version upgrades… they had enough time to break it this time. And it seems that since Jacobson is the only manufacturer, there’s just one security code for all the clients.”</p><p>People still looked relaxed. A fat man was looking at his tablet, checking the sports results.</p><p>“They sent me a video of a man dying after they pushed a button.”</p><p>They were stiff, barely showing any emotion. An old bald man at the back of the room shouted “Alan, what’s this all about? My dinner might be cold already.”</p><p>“What Dr. Derrick is trying to explain”, Jacobson said, “is that the LV has been compromised. And we have to do something to fix that or more people will die.”</p><p>People nodded again, and then stared at Joe again.</p><p>“Thanks Dr. Derrick”, said Jacobson, calmly.</p><p>Joe suddenly felt he was not needed there anymore, and looked at Jacobson, but he was already looking at a screen. Joe left, and slammed the door to ensure everybody noticed he was not pleased with that behavior.</p><p>After a reasonable amount of time, when Joe’s footsteps were no longer heard in the distance, echoing the then empty corridors, a voice said “so, can we trust him?”</p><p>“That fairytale about the community… I think we could pass”, another voice said.</p><p>“… definitely”, Jacobson said, and proceeded with “… but if I don’t schedule a meeting like this, Dr. Derrick wouldn’t have stopped and could have been dangerous. Everyone, have dinner with your families, I am so sorry for forcing you to come.”</p><p>Cynthia, who was there, waited for everyone to leave, and turned off the lights.</p><blockquote>After two weeks of investigation, it is still unclear how the 2537 people that were visiting the Central Mall on the first Saturday of May suddenly perished. Family and friends gather around the improvised monument at the entrance of the Mall in memory of the now known as the Silent Mall. Jacobson Medical specialists have concluded the vaccine wasn’t the cause, and instead seems to have treated the same affection to everyone at the same time, as if an external agent affected everyone in the zone. The decontamination team of the city is heading right now to the epicenter of the tragedy, in search of the possible toxic source.</blockquote><p>Alison turned the screen off. She was drinking some cheap alcohol, but it was not causing any effect on her. One of the secondary effects of the Last Vaccine is that you no longer get alcohol poisoning. It was bitter, and she didn’t actually like alcohol, but some friend brought it for a party years ago, and she decided to give it a go.</p><p>She opened her laptop. It already showed a lot of code on the screen. She started typing very fast. “Heh, like in the movies”, she thought, and deleted all that nonsense. After that, she typed at her regular pace, looking at everything around the code she was debugging. She had been fired years ago from Jacobson Medical, and she was no longer an instructor. The new company that hired her was a small startup that couldn’t afford a good instructor, but she had to eat and pay the bills, so she went back to what her father taught her when she was 7, when programming was the only way.</p><p>She was happy with the result of that project, so she sent the code to the startup servers, and closed everything on the laptop. Then she quickly typed a few keys, and the screen went black, then bright again, with another background and a few opened apps. Among them, the one on the foreground was another code editor.</p><p>She was familiar with that code. She instructed many of those disease requirements a few years ago. That one entry point was called <strong>disassembleRun()</strong>, and the definition of it couldn’t have been easier. She had some lines commented, so that they wouldn’t be executed, with code like <strong>priority = HIGH</strong>, <strong>socialDiscoveryRange = ALL</strong>, and <strong>diseaseType = AUTOIMMUNE</strong>. There was a clarification above the lines, <em>DO NOT UNCOMMENT UNTIL RELEASE DAY</em>. She uncommented all those lines.</p><p>Somebody knocked the door. When she opened, nobody was there, just a small package labeled with <em>USE BEFORE DISASSEMBLY</em>. She grabbed it, closed the door, and went next to the computer. She carefully opened the package, which revealed a box with some words scratched until they were illegible. When she opened that box, there was an old price scanner with a huge battery attached to it, and a note next to it, <em>USE TWICE ON WHOLE BODY. BURNING CLEANSES.</em></p><p>She undressed, checked her watch, 11:50 pm, “Shit, I better hurry up”, turned on the scanner, and started moving it around her arms and legs. A rash quickly appeared, and a blazing feeling started piling up everywhere the scanner touched. Tears were going down her cheeks. All of a sudden, when the scanner was close enough, the watch screen went off and a bit of smoke came out of it like steam. The wristband didn’t melt, but the watch was clearly no longer usable. When she finished, all her skin red and clearly burned from the inside, ran to check the clock on the computer. 11:59 pm. She stared those pixels for the longest 35 seconds left of that day. 0:00 pm…</p><p>Click.</p><p>Suddenly, a ton muffled screams, dinnerware breaking and heavy weight falling on floors crowded her ears. Cars crashing to each other on the street became less and less noticeable as the sound was getting farther and farther.</p><p>Then, the silence. Only some distant screens tuning the news channel were heard, unaware of what happened seconds ago, until the anchors and meteorologists suddenly died almost without agony.</p><p>Her phone started ringing.</p><p>“Disassembly… completed?”, she said.</p><p>“₮Ⱨ₳₦₭₴, ɎØɄ ĐłĐ ₩ɆⱠⱠ.</p><p>₮ⱧɆ ₵Ø₥₥Ʉ₦ł₮Ɏ ₩ɆⱠ₵Ø₥Ɇ₴ ɎØɄ.”</p><p>She hung her phone, sat on the couch, and started crying.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eba5bf1a9419" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kotlin ❤ #2: firstNotNullOfOrNull, or how to merge 3 methods in one]]></title>
            <link>https://medium.com/@sergi.juanola.c/kotlin-2-firstnotnullofornull-or-how-to-merge-3-methods-in-one-743914e6f75c?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/743914e6f75c</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Wed, 17 Nov 2021 17:57:10 GMT</pubDate>
            <atom:updated>2021-11-17T17:57:10.055Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVcMXy5JTKTRyASqbPF5pw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mpetrucho?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Petr Magera</a> on <a href="https://unsplash.com/s/photos/factory-line?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Imagine you have a list of items. Now, imagine you want to transform them into another type of item. Now, imagine you want to get the first item you properly transformed, or null if none of that list was transformed correctly.</p><p>Did I mention you want to do that efficiently?</p><p>The classic go to would be convert it into a sequence (to make transformations more efficiently), map them with the transformation function of your choice, and then you’d pick the first one available, or null otherwise. Something like this:</p><pre>this<br>        .asSequence()<br>        .mapNotNull { transform(it) }<br>        .firstOrNull()</pre><p>Or, starting at Kotlin 1.5, you could use a single call to do the same thing instead with <a href="https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.collections/first-not-null-of-or-null.html">firstNotNullOfOrNull</a>:</p><pre>this.firstNotNullOfOrNull<em> </em>{ transform(it) }</pre><p>Kind of a gimmick, and hardly memorable, but hey, it cleans up two lines of code!</p><p>What could be a better name for that method?</p><p>That’s why I ❤ Kotlin</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=743914e6f75c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A career switch is the scariest best thing you could do]]></title>
            <link>https://medium.com/swlh/a-career-switch-is-the-scariest-best-thing-you-could-do-1d7895637eb8?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d7895637eb8</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Fri, 11 Sep 2020 12:48:47 GMT</pubDate>
            <atom:updated>2020-09-11T14:37:21.726Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfyP-rnhEsuItj6Zs9l01A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@garri?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Vladislav Babienko</a> on <a href="https://unsplash.com/s/photos/options?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Let’s see if this rings a bell.</p><blockquote>You are in a position that’s okay. Nice pay, flexible time, good colleagues, no extra hours, no rushes… A dream job that you hate to do. You always wanted to be <em>[dream job]</em>, but you stepped into this role, and it worked so far. Yet, you feel it’s not perfect, but finding another job is like the most stupid thing you could do… or is it?</blockquote><p>I, myself, found 9 years ago with a job. Not perfect, but not bad at all for a starter. Good pay for a graduate, interesting, and in my niche. Or at least, the niche I <em>decided</em> to take when I finished my studies. It was easy, there were lots of vacancies, I did it before –it was the <strong>safest call</strong>.</p><p>Fast forward to a couple more jobs later, all for the same role. I noticed one day something was wrong. Something didn’t completely work in my dreamed life. I was doing something I really didn’t like. Name the reason: not enough freedom, a neverending feeling that you are not contributing to improving anybody’s life (not even mine), seeing others get higher pay, or basically, you simply were mistaken, and that role you chose when you were 18 (and we all know we’re really mature at 18), is probably not a great fit for you. Oops! <strong>Now you’re stuck. Except you aren’t</strong>.</p><h3>How can I switch careers? I’ve done a long way already</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*OnhSuo2_yT8tqiMFVsNv7g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ivalex?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ivan Aleksic</a> on <a href="https://unsplash.com/s/photos/options?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>One of the biggest obstacles you’ll find in your path (many times from other people, most of the time coming from yourself) is that, come on, let’s face it, you’ve been in this role for so long that it doesn’t make sense to switch anymore.</p><p>I’ve been there. You try convincing yourself, but you know it won’t last long.</p><p>There’s nothing wrong with switching careers. <strong>Think of it the other way. The fastest you switch, the shorter you’d have been in your <em>previous</em> position!</strong></p><p>Don’t pay attention to those that don’t let you fly. Even if it’s your current boss, trying to undermine you (so that you have to be there forever).</p><h3>But I will start as a rookie again! I won’t earn that much anymore</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*0-mZfF7tJu8DAK5Xs8lOjw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@maxvdo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Max van den Oetelaar</a> on <a href="https://unsplash.com/s/photos/options?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A lot of people forget that not everything is having experience in the role, but there exist certain abilities that are required for every job, and they need to be learned in a real job. You’re already one step ahead of others. Congratulations!</p><p>For sure, you won’t earn the same as before, but switching to a better job will be much easier, and you’ll be able to raise your pay faster than before. You’ll be as you were in no time. In my case, when I switched, it took me 7 months to earn even a little more than before.</p><p><strong>Even if you earn less in this new job, you’d be happier, so you may not need to cope with expensive stuff to keep you happy.</strong></p><h3>Okay, let’s switch!</h3><p>Great! The most difficult decision is done. Now, how should you switch? Fast, so that the pain goes away quickly, or slow, so that you can switch without any danger for your personal economy?</p><h4>Quick! Like removing a bandaid</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*nxxsSQQHPNKFF_L1zKfTPA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@harleydavidson?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Harley-Davidson</a> on <a href="https://unsplash.com/s/photos/fast?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The best you can do to switch jobs is finding out the requirements for that job. Then, when you know that, go for it! Quit your current job, and focus 100% of your time on achieving that. Keep studying, keep applying for jobs, and at some point, earlier than what you expect, you’ll be able to switch to your first new-life role!</p><p>Since this is quite adventurous, you may need to have at least a few savings to cover your expenses ahead. Maybe you can even ask for help from your partner or family. Being in good company is great to do a quick, great, painless career switch.</p><h4>Slow! I prefer to stay safe</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3yPpB7Q_5XHrt6WQtkCx7Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lucambro?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Luca Ambrosi</a> on <a href="https://unsplash.com/s/photos/turtle?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Maybe you’re worried that the change will be too much. Maybe it’s not a simple role change, maybe it’s a complete life change, like switching from being an electrical engineer to a carpenter. You’ve done some work as a hobbyist before, but nothing more. Maybe completely switching at once, studying and finding your new company or clients might take too long. Maybe you’re not ready.</p><p>Maybe, maybe, maybe! <strong>Enough of saying maybe, start saying willbe! </strong>Take your free time, study, apply for positions… Do the same thing you’d be doing the fast way, but during your free time! You’ll have to spend quite a lot more time on that.</p><p>What’s the difference, you ask? It’ll take longer, but you’ll be in a better position if you find out that the requirements are too many to be accomplished in a short span.</p><p>This is the path I followed, and boy, it took me 3 years to switch. You’re safe and sound, you still pay your bills, but you spend all your free time learning. It may take a toll on your life, so make sure to balance professional improvement with personal maintenance! After some time, I check back, and I truly believe that quick and dirty would have been a better option for me, but life is like this: you can’t know if you did better, because you can’t go back and check.</p><h4>Shine and change in your current job!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ZrMUERn7z8InX41gMG0d4A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@chrislawton?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Chris Lawton</a> on <a href="https://unsplash.com/s/photos/change?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Did you think there were only 2 ways? Nu-huh. If your position is only a tad different from what you really want to do, then maybe the best option is to negotiate with your current boss. Maybe there’s a chance that your employer needs a role you’d prefer the most, and you can convince them to give you a chance. You’re safe, you can (probably) switch back if anything goes wrong, and in any case, you’ll have a good experience pack to add to your resume.</p><h3>Conclusion</h3><p>Ah, the beloved conclusion. Does switching roles sound scary? <strong>I’d be scared to stay forever in a hated job!</strong> Irresponsible? <strong>Irresponsible would be if you weren’t switching!</strong> Crazy? <strong>You’re crazy if you stay in a job you hate!</strong> Great? <strong>Oh yeah, changing roles would be great!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yAiGbqqVAZPXxhFBfnpC6g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kylejglenn?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kyle Glenn</a> on <a href="https://unsplash.com/s/photos/encouraging?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d7895637eb8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/a-career-switch-is-the-scariest-best-thing-you-could-do-1d7895637eb8">A career switch is the scariest best thing you could do</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If It Breaks, Then We’re Good]]></title>
            <link>https://medium.com/swlh/if-it-breaks-then-were-good-2092cf054123?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2092cf054123</guid>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Sun, 06 Sep 2020 10:54:51 GMT</pubDate>
            <atom:updated>2020-09-08T12:16:01.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wTpE7j_XPcA8qgYRyj5Mw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jilburr?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jilbert Ebrahimi</a> on <a href="https://unsplash.com/s/photos/broken?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Let me tell you a story.</p><blockquote>Once upon a time, there was a brave warrior named Devel Oper. This brave warrior had seen enough corruption in the kingdom he was serving, and decided to burn it to ashes (with the collaboration of his fellowship Cod’er and Tec Hlead) and start over. It wouldn’t be pretty, it would take them time, but this new kingdom would be more respectful, safe and… modular?</blockquote><p>A handful of us (sadly, not everyone can take company time for such an endeavour) have found ourselves improving the codebase. And probably not a single one of these refactors was blissful and without any trouble. Classes, that break? Sure. Are arguments no longer available? Uh-huh. Are dependencies no longer satisfiable? Tell me more.</p><p>Is it bad? Well, yes. Is it good? Also yes.</p><h3>If it broke, then better sooner than later</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tq3cCMHDxnnkVTxtFSJ6jA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@icons8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Icons8 Team</a> on <a href="https://unsplash.com/s/photos/customer-angry?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It is okay to break a thing in a controlled way (that is, during a refactor), rather than finding it out via your customers. When something breaks, there’s a reason underneath, but you haven’t seen it yet. Have two classes vaguely named the same way, with roughly the same fields. Require it as an argument for one class, pass it as an untyped object to another class, let this other class cast again, but mistype the dependency. In most cases, it could work flawlessly… until you ask for the field that’s not there.</p><p>When you refactored that (maybe moving it into a different module, maybe renaming a few classes, simplifying them who knows), something could break out of the blue, and it would be catastrophic, except that you found it in your own computer, and not on an error log worth millions.</p><h3>If it broke, it was too coupled</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*htmTUcCjRpOX7cXW2R3r-A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@yogidan2012?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daniele Levis Pelusi</a> on <a href="https://unsplash.com/s/photos/fusion?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Why do some things break? Because some code requires too much of another. It is a classic that you notice during a refactor, that a business logic class depends on a UI data transfer object. We can imagine it the other way at some point, but why should the domain logic furiously need something from the UI, without even processing it in any single way?</p><p>The same happens when two code blocks with very different goals (for instance, authentication code and data visualization code) communicate way too much with each other. Do they need to? According to the pre-refactor code, yes. Move the authentication code to its own place, and now you can’t see those cute graphs.</p><h3>If it broke, it is not SOLID enough</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CN8bgnbZtfXpAWNiTsG2JA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mishaalzahed?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mishaal Zahed</a> on <a href="https://unsplash.com/s/photos/mud?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Let’s say you refactored the code to a seamless, perfect module. Except that… you have had to compromise a few situations of code repetition among different modules, to make it work. And also, right after you commit the module, you notice that it’s actually 2 different modules! Or maybe, all of a sudden you have to extend some classes and change their behavior on this module because otherwise, it wouldn’t work.</p><p>Well, if you have all that stuff, count the days before it breaks on its own. This seems very cheap, but <a href="https://en.wikipedia.org/wiki/SOLID">SOLID</a> code tends to break less (and be easier to extend).</p><h3>If it didn’t break, did you cover all the cases?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Rdykm_Pg8rhjQF1T2ScdA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@svklimkin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">svklimkin</a> on <a href="https://unsplash.com/s/photos/leaking-tap?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Imagine it the other way around. You do a refactor worth 2 weeks of your time. And <em>nothing</em> broke? What’s wrong with that then? If nothing breaks, it should be a reason to be happy.</p><p>Check your tests again, because either your code was already pristine, or somebody’s about to work late next week (and it’s not me).</p><h3>If it didn’t break, are you really using that?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hbVDVmplVTcaSoLoXnoqrg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jeremy0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jeremy Zero</a> on <a href="https://unsplash.com/s/photos/mummy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Believe it or not, we, developers, like to keep code around. Yes, even in the age of version control, we believe that having a plethora of old code around is worth the bytes it weights and the reading time it needs. If you moved something and your code didn’t change, either I really want to see that perfection or that code is simply not used. It’s not bad to discover that, it’s maybe disappointing that you spent the last 4 hours refactoring that class and it’s worth nothing, and you’ll probably want to keep it in case somebody did that on purpose (they never do).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2092cf054123" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/if-it-breaks-then-were-good-2092cf054123">If It Breaks, Then We’re Good</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is QA Everyone’s Job?]]></title>
            <link>https://medium.com/@sergi.juanola.c/is-qa-everyones-job-95920accd495?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/95920accd495</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Fri, 31 Jul 2020 07:40:14 GMT</pubDate>
            <atom:updated>2020-07-31T07:40:14.316Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Csu21wSk8xQuJqgRc-tPyA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ekamelev?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Егор Камелев</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>Before starting. I’d like to mention that the article has a few <a href="https://en.wikipedia.org/wiki/Reductio_ad_absurdum">reductio ad absurdum</a> examples. Keep that in mind when you read through it.</blockquote><p>So you wake up, go to your office, turn on the computer and start coding. Then you keep coding. Lunchtime. Code a little more, go home, go to sleep. Rinse and repeat.</p><p>When’s the time to test? It’s just easy: Always. But then… what’s the purpose of having a QA team on board?</p><h3>If I’m a tester, then what does the QA do?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GuOXRSEWOxxVDPMDT8Qf7A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jeshoots?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">JESHOOTS.COM</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Just in the same way cooking a canned soup doesn’t turn you into a chef, testing yourself doesn’t let you add the <em>Quality Assurance</em> title to your resume.</p><p>Your trusted QA will probably have a lot more work to do besides testing the code you just wrote. Smoke and regression tests, keeping a plethora of test cases up to date. That, specifically, could be done by developers, sure. Many QAs will ask that to happen on the developer side and praise the value of everyone having the same responsibilities and product knowledge.</p><h4>Let’s test our own stuff</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYcFOfbeTcHtVS%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcat-tail-chasing-YcFOfbeTcHtVS&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2FYcFOfbeTcHtVS%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/0008e51e022d44aaf539882659115037/href">https://medium.com/media/0008e51e022d44aaf539882659115037/href</a></iframe><p>Now, the problem I see in this is <strong>the bias of testing your own code</strong>. If you are a decent developer, and your team has settled a good DoD (Definition of Done) for every feature or bugfix you have in your pool, rest assured you, as a developer, are testing every case there. <strong>This means you are already creating your own test case</strong> (made out of code). You go through all the steps to reproduce each case from the DoD. It works. If you’re even more into this, you probably have good Unit Tests and good coverage for all the stuff you just finished.</p><p>But probably each one of us with a QA in our team has lived the situation of a ticket coming back to our list. A new bug arose <em>because</em> of your changes. Not even related to what you were doing.</p><p>Testers are great at finding this kind of stuff. Why? Because that’s their specialty. They wouldn’t just test your feature, they’d test it and any tangential feature or scenario that at some point would collide with what you wrote. And developers won’t see that because they’re focused on testing what they just coded, because they already code and test. Nobody that I know would ever code a whole feature and only minutes before they pass the feature to the QA, make sure everything works as it was expected.</p><p>Worse than that. Developers will probably follow their <em>happy path</em>; when it’s time to implement the feature, the happy path is that the feature works. When it’s time to implement the error handling, the happy path is that the error shows up. You don’t worry about testing what you wrote 5 minutes ago. Why would you? It was working the last time…</p><h4>Okay then, let’s test other developers’ stuff</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qavz0GS2GogzgFsOb9HwfA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kaip?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kai Pilger</a> on <a href="https://unsplash.com/s/photos/wait?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>If the great problem is that you test your own code, then why not testing your colleagues’ code instead? Okay then. Let’s imagine we have features that are big enough (one or two weeks long) and bugfixes that are either short or hard to estimate. Let’s also imagine that, for the sake of this example, the QA has become more like a Testing Consultant, and is not willing to take any testing task, but instead investigates smarter ways to assure quality and coaches others.</p><p>Now for simplicity, imagine there are two Devs, a deadline, and some tickets, each one of them has development time (in orange) and testing time (in blue). In green, stuff that’s completed, in red, bugs out of the ticket:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*3fWq_NwtuykwTSGy-6srng.png" /></figure><p>All the tickets have some inherent testing that happens along with the development (hence the mix of blue and orange). It’s also very likely that somebody starts with the big feature, and somebody else would start with bugs that, despite being critical, are fast to fix.</p><p>Now, Dev1 is able to manage all the bugs in the backlog, as well as a larger ticket, while Dev2 is still working on the feature. When Dev2 is able to start testing Dev1’s tickets, everything’s almost done and the deadline is close to finishing, but alas, one of the tickets from Dev1 was buggy and is put back into the Dev1 backlog.</p><p>We could have captured that bug almost at the beginning of the sprint, yet it was detected at the end of it. Now we can’t fix it and is left for the next sprint, with any problem that arises from that (pending pull requests that need to be continuously rebased until it is fixed, etc).</p><p>Having a person that, not only is good and more focused on testing, can test right away or soon enough, is definitely a much better thing to get things done.</p><h4>Okay, let’s strip the labels</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pItSQ5heXN0Ip7D8Jt6E2Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@claybanks?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Clay Banks</a> on <a href="https://unsplash.com/s/photos/equality?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’m a huge defender of professional labels. They define us, and sadly, what we earn. If we stripped all the labels, why would I earn less than the once called CEO?</p><p>Also sadly, experience has shown me that developers <em>tend</em> to earn a little bit more than testers, despite all being necessary for a product to succeed. Why would somebody task a developer with QA if somebody that earns less can do it? And then, why would the one that pays (to remove all the labels) pay everyone the same if the former developers now also test and the testers don’t develop?</p><h4>Okay, then Development is Everyone’s Job</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3cCEduBPwft0PEFwYNXcw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@adigold1?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Adi Goldstein</a> on <a href="https://unsplash.com/s/photos/everyone?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Let’s do it the other way. Let’s make the QA develop as well. Depending on how severely the QA team reads the premise that “QA is Everyone’s Job”, testers should be able to either point to the line that’s failing, fix the issues themselves or write complete features and have a word on architecture.</p><p>Some will be able. Few will say they would be able, a lot would complain that’s not the same. Quality assurance starts way before QA, way before even the devs have a word there. QA starts higher up in the ladder.</p><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c6VtGT80cu9N0OZ2S0W5Hg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@verstuyftj?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jonas Verstuyft</a> on <a href="https://unsplash.com/s/photos/lights?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We all have job requirements. We all do what we can with the toolset we have. <strong>If you already prepare easy to understand and thorough unit tests or make sure your tickets do what they’re expected to do, you’re already taking quality into consideration.</strong> Definitely not at the same level as somebody that spent the last 5 years learning tools and ways to test a product. But most testers I’ve worked with won’t care of code specifics (even if that’s the first bug barrier), so they won’t test at the same level as you either.</p><p>Sure, quality assurance <em>is</em> everyone’s job. If it wasn’t already, the tester’s life would be incredibly worse.</p><p>Maybe, and only maybe, <strong>should QA have more visibility? </strong>When you plan for the next sprint, you should consider QA time and Dev time separately. That way you can ensure everyone can commit to the sprint. And for the sake of everyone, leave some tasks that don’t require testing (POCs, refactors, investigations) for the end of the sprint, so that Testers can catch up and even send you some bugs back!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95920accd495" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kotlin ❤ #1: Chunked, or how to split huge amounts of data]]></title>
            <link>https://medium.com/@sergi.juanola.c/kotlin-1-chunked-or-how-to-split-huge-amounts-of-data-ab7febb6fedf?source=rss-e7bce92c16b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab7febb6fedf</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Sergi Juanola]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 12:51:17 GMT</pubDate>
            <atom:updated>2020-07-29T14:09:14.953Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3uZwCFR_WnEwXVB0QjkiTQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@alschim?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alexander Schimmeck</a> on <a href="https://unsplash.com/s/photos/chop?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Kotlin ❤ #1: Chunked, or how to split huge amounts of data in one line</h3><p>If you ever had to handle a huge amount of data, you may have developed something like this algorithm before:</p><ol><li>Take the whole amount of data</li><li>Get a portion of it</li><li>Process the data</li><li>Get the next portion, repeat 3 and 4 until you finish</li></ol><p>In many cases we, as developers, tend to look for overcomplicated ways to make it work, like recursion:</p><pre><em>const val </em>PROCESSABLE_DATA_AMOUNT = 3<br><br><em>// ...<br><br>fun </em>processData(list: List&lt;Int&gt;) {<br>    <em>if </em>(list.isNotEmpty()) {<br>        <em>val </em>processableData = list.subList(0, min(list.size, PROCESSABLE_DATA_AMOUNT))<br><br>        <em>// Here&#39;s where you&#39;d truly process the data<br>        </em>println(processableData)<br>        <br>        <em>if </em>(PROCESSABLE_DATA_AMOUNT &lt; list.size) {<br>            processData(list.subList(PROCESSABLE_DATA_AMOUNT, list.size))<br>        }<br>    }<br>}<br><br>processData((1..20).toList())</pre><p>In the example, processing the data just means printing it, but picture it with a few more lines (like sending the data to a server, or saving it to the DB). Now imagine having to read through this logic after months. It surely is understandable, but having to find out there’s recursion in there, complicates the code. Let alone an example without recursion.</p><pre><em>const val </em>PROCESSABLE_DATA_AMOUNT = 3<br><br><em>// ...<br><br>fun </em>processData(list: List&lt;Int&gt;) {<br><br>    <em>for </em>(windowPosition <em>in </em>0..list.size step PROCESSABLE_DATA_AMOUNT) {<br>        <em>val </em>processableData = list.subList(windowPosition, min(windowPosition + PROCESSABLE_DATA_AMOUNT, list.size))<br><br>        <em>// Here&#39;s where you truly process the data<br>        </em>println(processableData)<br>    }<br>}<br><br>processData((1..20).toList())</pre><p>You end up introducing many calculations that don’t belong to your business logic, but more likely to the processing limitations of whatever system you use.</p><p>Here’s where <a href="https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.collections/chunked.html">chunked</a> comes in:</p><pre><em>const val </em>PROCESSABLE_DATA_AMOUNT = 3<br><br><em>// ...</em></pre><pre><em>fun </em>processData(list: List&lt;Int&gt;) {<br>    list.chunked(PROCESSABLE_DATA_AMOUNT) <strong>{<br>        </strong>println(<strong>it</strong>)<br>    <strong>}<br></strong>}<br><br>processData((1..20).toList())</pre><p>All the logic is reduced to a simple line, which accepts a mapping method (which we just use for processing it), but if you don’t pass any lambda, it becomes a list of lists. This means you can traverse it with forEach, for instance.</p><p>That’s why I ❤ Kotlin</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab7febb6fedf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>