<?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 Linoy Zaga on Medium]]></title>
        <description><![CDATA[Stories by Linoy Zaga on Medium]]></description>
        <link>https://medium.com/@linoyzaga?source=rss-57a55e350494------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*5ylQa1h5rawDi2zERIYIRA.jpeg</url>
            <title>Stories by Linoy Zaga on Medium</title>
            <link>https://medium.com/@linoyzaga?source=rss-57a55e350494------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:35:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@linoyzaga/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 one-Day delay that saved Melio $200K: a problem-solving journey]]></title>
            <link>https://medium.com/meliopayments/the-one-day-delay-that-saved-melio-200k-a-problem-solving-journey-af6644b94d2c?source=rss-57a55e350494------2</link>
            <guid isPermaLink="false">https://medium.com/p/af6644b94d2c</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[reconciliation]]></category>
            <dc:creator><![CDATA[Linoy Zaga]]></dc:creator>
            <pubDate>Tue, 23 Jul 2024 08:20:09 GMT</pubDate>
            <atom:updated>2025-05-14T12:27:34.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*xBdmnTo7fVPoHODdk9WhgQ.png" /></figure><p>As a software engineer with over a decade of experience, I’ve always thrived on finding creative solutions. This drive to innovate extends beyond writing clean code — it’s about making a real impact on the business I work for. At Melio, we recently discovered an opportunity to do just that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WmdIckoN16-Xql8M" /></figure><p>Melio allows businesses to pay and get paid quickly and easily. We charge a small fee for some transactions that cover the service and keep overall costs low.</p><p>Similar to how you incur fees for various actions in your bank account, Melio, a payment platform that uses banking partners to facilitate transactions and money movement, pays fees for each transfer in its accounts. For instance, when a customer requests to pay a vendor $10k using a paper check, Melio performs this action on behalf of the customer. Melio collects the funds from the customer, issues a check, and sends it by mail to the vendor. Additionally, Melio collects a $1.5 fee for service costs from the user. In addition, it also pays its banking partners a fee for each money transfer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sQLu0T4Rj2gx8nF1" /></figure><p>Through a thorough evaluation of the money movement protocols and how our processing engine works, we discovered that we can lower fees by adjusting the money movement speed.</p><p>In traditional businesses, fees are deposited into the merchant’s account. However, in Melio, we first collect funds into our operating account and then move them to our revenue account. We realized that if we adjust the transfer speed of the funds flowing into our revenue accounts, we can significantly reduce the fees Melio pays its banking partners for each transaction.</p><p>This seemingly small delay in processing payments translated to a significant reduction in costs. By offsetting these transfers in a single day, we saved Melio a staggering amount of around $200k annually.</p><p>In this blog post, I will explain how we did it, and provide some solutions that could be helpful to engineers working on similar strategies.</p><p><strong>Let’s save some money</strong></p><p>​​With our discovery in hand, the next step was bringing it to life. We needed to modify the code that generates the payment information and, eventually, the payment files sent to the bank.</p><p>We added a feature to these files that told the bank to hold onto the transaction for a day before processing it. This practice is called deferred days configuration. To implement this new feature, we seamlessly integrated the change into our payment settings. This means the daily files we send to the bank with payments that should be processed were automatically updated to reflect the one-day delay instruction. Also, the user experience wasn’t affected.</p><p>But when dealing with money, even the smallest misstep can have big consequences. So, after implementing the code changes, we conducted a rigorous end-to-end test in our production environment. We mimicked real-world scenarios with test data to ensure everything worked smoothly. Every step, from sending the modified file to receiving confirmation, was meticulously tested. This level of caution was crucial because we wanted to guarantee a smooth transition without impacting our customers.</p><p>Integrating the “deferred days’’ feature wasn’t entirely straightforward. Initially, there were compatibility issues with the banks’ systems. However, by closely collaborating across product, engineering, and banking partners, we were able to identify and implement a workaround that ensured seamless communication with the bank.</p><p><strong>Testing with care</strong></p><p>Next, we mapped out all the scenarios we needed to test to ensure a flawless implementation:</p><ul><li><strong>Every payment method:</strong> We tested the functionality with debit cards, credit cards, ACH transfers, and any other payment option Melio offers.</li><li><strong>Payment changes:</strong> We simulated scenarios like upgrading a customer to a faster payment method and verified the system processed the change correctly.</li><li><strong>Fee types:</strong> We tested how the delayed processing affected various fees Melio charges, ensuring accurate calculations.</li><li><strong>Bank compatibility:</strong> We rigorously tested the system with each bank and service provider Melio works with to guarantee seamless communication.</li></ul><p>In collaboration with Melio’s application team, we conducted these tests on Melio’s production account using real payments and real money. We monitored each transaction to ensure payments were transferred to their destination on time despite the one-day delay. This validation process, which took several weeks of rigorous testing, was crucial for the project’s success and to ensure we were carefully handling customer funds.</p><p>Once we were confident in the functionality of our code and the reliability of the project, we gradually rolled it out to users. To proactively address any potential concerns, we kept our customer success team informed about this new payment processing change. We established a communication channel with the customer success team, ensuring they would promptly notify us if any user issues related to the delayed processing arose.</p><p>We’re happy to report that users haven’t experienced any issues with the one-day delay — a testament to the smooth rollout. However, in close collaboration with our reconciliation analysts team, we addressed a reconciliation challenge related to the delayed processing: ensuring our internal records matched the bank’s statements.</p><p><strong>Ensuring smooth reconciliation</strong></p><p>What is reconciliation? Imagine you have two shopping lists: one for what you bought and one from your bank statement showing what you paid. Reconciliation is like double-checking these lists to ensure everything matches.</p><p>Reconciliation is a financial control process that allows Melio to compare and match cash-based bank transactions to what happened in Melio’s database. This is crucial for any organization handling money movement, and Melio has an in-house reconciliation tool that automates this process. You can read more about our reconciliation process <a href="https://medium.com/meliopayments/why-we-built-an-automated-reconciliation-tool-and-what-the-future-holds-for-it-9ac51ffef75f">here</a>.</p><p>With the new cost optimization feature, we added a twist to the process. We started sending payments to the bank on the same day, but instructed the bank to hold onto them for processing until the next day. This one-day delay introduced a new wrinkle in our reconciliation process. We needed to adjust our reconciliation tool to check the bank records from the bank statement with the previous day’s records in our database, ensuring it accurately matched the payments we sent.</p><p>Let’s take a closer look at the reconciliation process for delayed payments. Suppose we have a payment due on April 2nd, but it’s a service cost payment we collect from the user, and we want the bank to process it on April 3rd. Here, we would expect to see this payment in the bank statement of April 3rd, which would then be processed on April 4th.</p><p>Previously, our tool would look for a payment sent on April 2nd in the bank statement of April 2nd. However, with the delay, the bank statement of April 2nd won’t show the payment yet. We needed to adjust the tool to look for the payment of the <strong>bank statement of April 3rd with database records on April 2nd</strong>, even though it was originally sent (and recorded in our database) on April 2nd. This ensures our records match the bank’s activity, even with the one-day processing delay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PINNsuQp-5DL-gty" /></figure><p>After resolving the reconciliation issue and ensuring there are no further complaints, we fully rolled out the feature to 100% of the users and began monitoring the results. In collaboration with the analytics team, we confirmed that our initial predictions matched the actual savings.</p><h3>Conclusion</h3><p>Working on this project was immensely rewarding. As a tenacious engineer, I’m always looking for ways to improve efficiency, and this project perfectly exemplified that spirit. It involved close collaboration with various teams, including Finance, Analytics, Product, Engineering, and Customer Success, fostering a strong sense of teamwork and shared purpose. The project required innovative thinking and planning to ensure every detail was covered, ultimately leading to significant cost savings of about $200k annually.</p><p>Witnessing the positive impact this project had on Melio’s bottom line was incredibly motivating. It showed me the real-world value of innovative thinking and its ability to translate into tangible benefits for the company. This experience also highlighted the importance of cross-functional collaboration — the combined effort of various teams made this project a success.</p><p>So, if you’re a software engineer or simply someone passionate about problem-solving, I encourage you to embrace creative thinking and explore potential improvements in your work. You might be surprised by the impact you can make.</p><p>Here are a few additional tips we’ve compiled to help you get started:</p><ul><li><strong>Think outside the box:</strong> Challenge conventional methods and explore creative solutions.</li><li><strong>Investigate your money flow:</strong> Analyze how money moves through your organization to identify potential savings.</li><li><strong>Consult with experts:</strong> Seek advice from colleagues or financial advisors to uncover cost-saving opportunities.</li><li><strong>Never give up on your ideas:</strong> Persist with your innovative ideas and always consider the bigger picture.</li></ul><p>So, are you ready to unleash your inner problem-solver and make a positive impact? Start exploring creative solutions today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af6644b94d2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/meliopayments/the-one-day-delay-that-saved-melio-200k-a-problem-solving-journey-af6644b94d2c">The one-Day delay that saved Melio $200K: a problem-solving journey</a> was originally published in <a href="https://medium.com/meliopayments">Melio’s R&amp;D blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaling Applications with Constant Work Pattern]]></title>
            <link>https://medium.com/@linoyzaga/scaling-applications-with-constant-work-pattern-f253176b3146?source=rss-57a55e350494------2</link>
            <guid isPermaLink="false">https://medium.com/p/f253176b3146</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[kotlin-coroutines]]></category>
            <category><![CDATA[scale]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Linoy Zaga]]></dc:creator>
            <pubDate>Mon, 02 May 2022 10:50:12 GMT</pubDate>
            <atom:updated>2022-05-02T10:52:46.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfoa5yQLy2EyhimaVqVtsA.jpeg" /></figure><h3>Introduction</h3><p>In the life of a software engineer, there will always be a stage where we will have to handle scaling our application. Scalability usually ends in some commonly known solutions, such as scaling servers up and down, adding cache and database indexes, etc. <br>Until one day my manager came to me and said, “We have a scale problem, the constant work pattern may be a good fit for your use case!”. Well, that was not exactly the case, but you get the picture.</p><p>I started reading about it, and frankly, my first reaction was skeptical. I asked myself, “Wait, what?” But as I kept reading and studying, I thought about how interesting this solution is, and that is thinking outside the box. I would like to share with you why we chose to implement a constant load in our services. I hope it’ll help you in the future.</p><h3>What is a constant work pattern?</h3><p>For understanding what the constant work pattern is, we’ll start with a small analogy, taken from the Amazon AWS article “<a href="https://aws.amazon.com/builders-library/reliability-and-constant-work/">Reliability, constant work, and a good cup of coffee</a>”:</p><blockquote>If you make coffee one cup at time, like a trained barista does, you can focus on crafting each cup, but you’ll have a hard time scaling to make 100 cups. When a busy period comes, you’re going to have long lines of people waiting for their coffee. Coffee urns, up to a limit, don’t care how many people show up or when they do. They keep many cups of coffee warm no matter what. Whether there are just three late-night diners or a rush of busy commuters in the morning, there’ll be enough coffee.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OoFkKSZj1QVwVrlpCZuu2g.jpeg" /></figure><p>In the analogy I presented, the coffee house simulates our application. We would like that our application will always be ready to handle a massive amount of users, up to some limit of course. And for that solution we would need coffee urns, meaning we would like our application to work on its maximum load for 100% of the time.</p><h3>Isn’t it a waste of resources?</h3><p>That’s the first question that came to mind for me too. But if you’ll think about it a bit more, you’ll find the following advantages:</p><ol><li>Your application won’t have modes, which means it will do the same operations in all conditions and terms.</li><li>Your application won’t scale up or slow down with load or stress.</li><li>If your application has any variation, it will do less work in times of stress so it can perform better when you need it most. There’s anti-fragility in your application.</li></ol><p>The downside is indeed the use of additional resources, more than the actual customer needs.</p><p>As for our application, we expect, further down our roadmap, to handle a high amount of data, so we need to make sure our services can handle a large scale of incoming events. Implementing the constant load design in our services will help us find bottlenecks we expect to encounter soon. It was also a challenging engineering project that our team is enjoy working on.</p><h3>How did we implement it in our application?</h3><p>The main entity in our application is called <em>Workflow</em>. The customers can create, update and delete Workflow, as much as they want. Each workflow can be enabled or disabled, as the customer wishes.</p><p>Behind the scene, we have a Kafka queue, from which we consume events. Those events have a matching mechanism, which can trigger one or more <em>Workflows</em>. This flow has some complexity, including approaching other applications and reading from DB and Redis cache, making sure the workflow is indeed enabled and whether we want to handle the matched event to it or not, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*sbIKoCw-PUBXutr1CHAGtA.png" /><figcaption>Our Application</figcaption></figure><h4>How did we intend to apply the constant work pattern to our application?</h4><p>We created “dummy” Workflows entities for all of our customers. Each customer will have the maximum Workflows they can have. Each of these “dummy” workflows has default values, which are designed to be matched to all of the events we consume from the Kafka queue we have. This makes sure our application will always handle all of the events we have and will be at its maximum load at all times. Those “dummy” Workflows are not visible to the customers. They only can see the Workflows they created by themselves.</p><p>When customers create a new Workflow, we replace a “dummy” Workflow they have in the bucket of Workflows attached to their account. This replaced Workflow will now be visible to the customers and contain the data they choose. This also applies to a delete Workflow action: when a customer deletes a Workflow, the application will replace the deleted Workflow with a dummy one.</p><p>Each Workflow creation by users can only decrease the load on our application and never increase it because, by default, our services are handling the highest possible load level. This ensures we don’t need to worry about new Workflows creation and the load may be added to our servers with each new Workflow is added.</p><h3>Main milestones</h3><p>We had several main milestones while implementing this solution:</p><ol><li>Prepare our services to support this solution.</li><li>Migrate all existing customers to use this solution.</li><li>Monitor our services and adjust if needed: We added metrics in vital places in our code and created dedicated dashboards to monitor our services, collect information and investigate each step of the way.</li><li>Prepare our services to support automatic “dummy” workflows creation for new customers: Add “dummy” Workflows for a customer the first time he creates his first Workflow in our API.</li></ol><p>We had feature flags, which allow us to “jump” from the old code to the new code if we were facing a problem that affected our services.</p><p>Another important thing to remember is if you plan to implement this solution on your side. Our application makes requests to third-party services, which we don’t own. We had to consider that these services might not be able to handle this amount of load, so we had to mock the network load that happens if we had reached these services.</p><h3>The Problems we faced</h3><p>While migrating existing customers, we faced some problems which we had to solve.</p><p>First thing first, we had to add more hardware to our instances. We needed to support the maximum load our customers will ever create. We added more instances, more CPUs, and RAM for each instance. We also added more Kafka partitions and increase the number of Kafka polls.</p><p>Next, we realized that our DB does not work with connection pools. Every time we got to our DB, we made a new connection and then deleted it. Setting up our DB to work with the connection pool, allows behind-the-scenes caching of maintained database connections so that connections can be reused when future database requests are required.</p><p>Another DB aspect we came across is that we reached our maximum memory in our Redis. We managed to fix it by giving all of our Redis keys an expiration date (TTL), so they won’t stay there forever and will be deleted.</p><p>We also added an improvement for our Redis requests. We added coroutines to asynchronous requests to Redis, which, improves our processing time (see graph below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCIXagfRCxe3O_hOyX9XZg.png" /><figcaption>Coroutines optimization in Redis</figcaption></figure><p>Since we use Redis for cache and lock, the number of requests we made each time was very high, so we had to make it as slim as possible. We noticed that even though Redis requests are relatively fast, they still put a burden on our services and take substantial time being IO requests that run synchronously. Handling those requests asynchronously made it easier and faster.</p><h3>More Optimizations</h3><p>We also added some more optimization to reduce the load we had in our services:</p><ol><li>Add Redis cache to third-party queries: When handling Kafka events we need to get to a third-party API to enrich our data with a specific query. While handling a large number of Workflow we realized that we reach the same API with the same query many times with a difference of milliseconds and the returned answer is the same. We added a cache mechanism to the query, with a TTL of 60 seconds. This optimization decreased our processing time and optimize our requests to this API.</li><li>Change all Redis locks operations to be atomic: Each operation was split into several separate small operations which caused a problem if by chance something stops its activity. Instead, we configured our Redis so all actions are atomic and if something stops, we’ll roll back to the start point of the operation.</li><li>Optimize our DB requests: We realized we’re calling the DB multiple times and this significantly improved by adding some conditions to our code. We saw an 85% improvement in process time (see graph below).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VfB2JUCfBoOD9nJc" /><figcaption>The effect we saw after optimizing our DB requests</figcaption></figure><h3>Conclusion</h3><p>In this article, I introduced you to a new scaleability approach named constant work pattern. We learned how exactly it’s working, how we implemented it within our application, the problems we faced, and the optimizations we made.</p><p>I hope this article helped you and opened your mind to a different type of scalability. Thanks for reading! Until next time 😃</p><p>Note: the main source of information we used is from the Amazon AWS article “<a href="https://aws.amazon.com/builders-library/reliability-and-constant-work/">Reliability, constant work, and a good cup of coffee</a>”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f253176b3146" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empower Women Is Not A Bad Word]]></title>
            <link>https://medium.com/@linoyzaga/empower-women-is-not-a-bad-word-d7d549de14d3?source=rss-57a55e350494------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7d549de14d3</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[international-womens-day]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Linoy Zaga]]></dc:creator>
            <pubDate>Tue, 17 Mar 2020 21:35:37 GMT</pubDate>
            <atom:updated>2020-03-17T21:35:37.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*sBqKlGZuurFwbgdwf3awaQ.jpeg" /></figure><p>I know what it’s like being the woman in the room. I was the only woman student in Computer Science class in High School. I was the only woman programmer in my team when I joined the Navy. I was the only team lead in a room full of commanders who were only men. And I still am the only woman in the room, even today….</p><p>In the beginning, I didn’t really care about being the woman in the room. I wasn’t aware that I am the only woman, I was used to it. I didn’t know anything else. But today I understand it is a problem. It’s a problem which is still here, and we need to be aware of it, and try to change it.</p><h3>Introduction</h3><p>The gender gaps in the High-Tech industry are large and clear: Only about a quarter of high-tech workers are women (17%) in Israel, and high-tech men earn an average of 18% more than women.</p><p>In this article we’re going to talk about the gender gaps, and the gaps in the natural thoughts in all of us in the 21st century. Those gaps, which start at a young age, lead the women not to choose a career in engineering. I’ll describe in this article my way to fight this battle, which many of you might think doesn’t exist today.</p><h3>Where Gender Gap Begins</h3><p>High-Tech is not for women is a feeling seeping from a very young age. It could be from many reasons: the competitiveness or crazy work hours that people said might not be suitable for women. Or it may also be because men now have three times more role models in this industry, something that will take years to change.</p><p>I think the reason for that saying seeping from a young age is because there is a thought that women are less talented in engineering than men.</p><p>A study taken in University of Maryland in 2010 was trying to identify what, if anything, is occurring in Math classes in high schools that may negatively affect the continued study of mathematics by young women. In this study, the researchers examined teacher-student interactions fully in Math classes in several different techniques.</p><p>This study shows a consistent pattern for more teacher-initiated contacts with males, that certainly point to unequal treatment. The teachers in the sample treated females and males differently in response opportunities, cognitive level of questions, praise and criticism, encouragement and individual help. The differences found generally work in a positive way for males — they received more teacher attention, reinforcement, and affect. Females, traditionally the “lesser sex,” received less attention. Some tendency was noted for females to become quieter and more passive in response to less teacher attention to them.</p><p>The classroom environments on the whole reinforced traditional sex-typing of mathematics as male. Nothing was discerned, in teacher language and behavior or the physical environment, that could be considered as working in a positive way to stimulate young women to continue their study of mathematics.</p><p>If you find this interesting, you can read more about this study <a href="https://mathedseminar.pbworks.com/f/Differential_Treatment_Becker.pdf">here</a>.</p><p>Those women, who are our next generation, got the thought that they are not good enough in math, that math isn’t for them. That they should find another path in their career.</p><p>This study shows us how much the society’s natural thought is that men are better in math than girls are. Even teachers who are females, who should empower girls in their classroom, do behave according to this stigma.</p><p>There is an unwritten thought that people in the High-Tech industry are very modern and open minded, and therefore there is a misguided opinion and expectation that there is no prejudice in this environment. You need to experience it by yourself so you will be able to acknowledge that there is prejudice here, in the so-called “superior” High-Tech industry.</p><h3>Gender Gap In Work Environment</h3><p>Having already entered this world, it is now also difficult to stay and hold on to it. The sense of capability we have built in spite of everything can break any moment. Whether it’s in a job interview, you’ll usually find yourself interviewed by a man. Or if it’s sitting at work, you’re the only woman in the room who needs to make her voice, and it’s usually a little harder than you think.</p><p>Not once I found myself in an interview, together with another guy or two, who asked me questions that made me feel unworthy, incapable. The interviewer once told me “I do not understand how you were even employed in your first job”. Another interviewer asked me “Are you sure you don’t know this question? The guy that was here before solved it in much more time than you did.”</p><p>I sometimes ask myself, why am I doing it? Why did I choose this men’s world, that no matter what, I will always be worth less? Will I always have to prove I’m at least as good as your worst programmer? And why is that?</p><p>And once you get a job, you’ll be one of the few women in the room, in the team, in the group, in the company. And you’ll have to keep on, because you love programming.</p><p>It’s very important for me to mention that <strong>NOT</strong> all work places behave like this and there are lots of places who do whatever they can to avoid uncomfortable and offensive situations for women in work interviews and work environments.</p><h3>What Do I Do To Empower Women?</h3><p>I was first exposed to the fight against workplace discrimination in my first job after my service in the Navy, at Klarna Israel. The entire management at Klarna reacted seriously to this situation and took many steps to create a work environment that is equal for both men and women.</p><p>We talked about it all the time, we said it out loud, by that we created awareness of the situation. Our HR team took care that women CVs will streamline to the top of the list so they could get an equal opportunity to join our team. Also, we created a comfortable environment in interview for women by always making sure there will be at least one woman interviewer in the room.</p><p>You can hear more about the Klarna Israel hiring process <a href="https://www.youtube.com/watch?v=JWYNst72ucI&amp;t=54s">here</a>.</p><p>The society naturally thought that men are better in engineering than women created a feeling that we are not capable of doing that. So I asked myself what can I do to create more sense of capability in women in this industry? And how can I pull more women to it?</p><p>The first thing I did was joining <a href="https://extend-tech.com/baot">Baot</a> mentorship program. My job as a mentor is to guide and help women that are looking for a job in the High-Tech industry. It’s hard looking for a job, especially when it’s your first time and you’re not familiar with this world. Sometimes you just need someone that will believe in you and make you believe in yourself.</p><p>Women tend not to send their CVs to places that they aren’t fit to all requirements, unlike men. I help them fix their CVs and send it to every place that they might fit, just give it a shot.</p><p>The second thing I did, which is my special project, is bringing the Node Girls Workshops to Tel Aviv. Node Girls workshop are workshops that are designed for women with no programming background. In those one-day workshops every woman can learn how to write basic code, and see if she likes it. They sit in small groups with a mentor. There they get a sense of capability, that hopefully they like it and will want to actually work in it.</p><p>You can read more about my Node Girls workshops <a href="https://medium.com/@linoyzaga/node-girls-workshops-in-tel-aviv-92f4e641dceb">here</a>.</p><h3>Conclusion</h3><p>How can we create a more equal world, which women can be 50% of the people in the room? How can we avoid this automatic thought that men are better in engineering than women? we need to be <strong>aware</strong>. We need to know that this thought exists in each and every one of us, and we need to re-think every time it pops up.</p><p>It’s hard for a woman to get into the High-Tech world, especially because currently it’s mostly men. I hope my Node Girls workshops will expose this world to more women and give them the sense of being able to do it.</p><p>I hope this article gave you another point of view on the struggles women experiencing in the High-Tech world, thank you for reading! Until next time 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7d549de14d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node Girls Workshops In Tel Aviv]]></title>
            <link>https://medium.com/@linoyzaga/node-girls-workshops-in-tel-aviv-92f4e641dceb?source=rss-57a55e350494------2</link>
            <guid isPermaLink="false">https://medium.com/p/92f4e641dceb</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[node-girls]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Linoy Zaga]]></dc:creator>
            <pubDate>Tue, 17 Mar 2020 21:32:22 GMT</pubDate>
            <atom:updated>2020-03-17T21:38:11.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NW6o4DJ5Zt3jSKO3Qz6kcQ.png" /><figcaption>Node Girls Tel Aviv</figcaption></figure><h3>Introduction</h3><p><a href="https://nodegirls.com/">Node Girls</a> is an international initiative established in London in 2015 with the goal of trying to reduce the gap between women and men in the software world. The idea is to allow women a “glimpse” into the programming world, through a free workshop in which they experiment by building a web application.</p><p>The gender gap in the High-Tech industry is clear, there aren’t a lot of women. I’m used to being the woman in the room. That is why I’ve started the Node Girls workshops in Tel Aviv, and this is an initiative close to my heart.</p><h3>Node Girls in Tel Aviv</h3><p>In 2018 I discovered Node Girls workshops, and I was so excited about that. I reached the girls in London and asked them to run this in Tel Aviv. I thought it’s a great opportunity to attract more girls into this world in Israel.</p><p>There were two successful workshops in Tel Aviv so far, lots of girls came and learned, enjoyed and challenged themselves. Some of them even continued learning it afterwards. We’ll keep going towards more workshops in the future in order to make this world more accessible.</p><p>The overall goal of the program is to expose as many women as possible to the programming world. We create a feminine and supportive environment to women who want to know if programming is the right choice for them. They can ask as many questions as they want and they are being answered without being judged.</p><p>This workshop create a sense of capability for the participants, that this is not a “men’s world”.<strong> They can also do it</strong>, although they might have heard differently.</p><h3>How It Goes?</h3><p>The workshop lasts only one day (Friday), during which the participants sit in small groups of 3 women with an instructor, and together they are doing a tutorial and building their application step by step. All the instructors are programmers who volunteered for it, and it is so important and not taken for granted.</p><p>At the beginning, after we kicked off with a light breakfast, I give a brief intro of what programming is, and how it looks from the user’s point of view and from the programmer’s point of view. Also I explain what we are going to do in the workshop and then let them start learning in full power.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*bJtRZI75E8SDtrkW" /></figure><p>All the instructors take their participants through the same <a href="https://nodegirls.com/resources">tutorial</a>. There are two levels of tutorials — beginners and advanced. They are being split up into groups according to their knowledge level and according to their laptop’s operating system (Mac or Windows), so it will be easier to the instructors. The tutorials are in Hebrew and in English, so the participants can choose which language they prefer.</p><p>The tutorials are well structured and slowly explain the core concepts of programming, so the participants can get into it more smoothly. Being in a small group with a female instructor creates a very positive and comfortable environment so they can ask as many questions as they need, without feeling judged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BxQuPKNsYWHIM4_kc5ZOiQ.jpeg" /><figcaption>Node Girls Workshop — March 2019</figcaption></figure><p>After lunch, we have several lightning talks from women in this world — designers, product managers, QA’s and engineers, who explain about their careers. The participants can hear how is it like to be a woman in the High-Tech world, and how to get there. How a day in a life of a woman programmer looks like, and which challenges they ran into in their daily life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5lotTyhvc1ZNzWB8J_gInQ.jpeg" /><figcaption>Talya explains what Scrum is — November 2018</figcaption></figure><p>We continue the tutorials after the lighting talks and getting into complicated things, like publishing their app online or using databases. We encourage the girls to open their minds and see how wonderful programming can be.</p><p>At 3 PM we’d reached the end of a wonderful, inspiring day, filled with new things learned. We wrap-up with some thank you words — to our instructors, who gave up on their free day and came to help us. To the sponsors, who enabled this day to become a reality and of course to the participants who challenged themselves and came to this workshop.</p><p>We also give some advice to the girls about how to keep on from this point and what they can do to move forward with their dream to become a programmer.</p><h3>Why It’s Available Only For Women?</h3><p>Even today, in the 21st century, there is still a glass ceiling for girls who want to get into the programming world, you can read more about it <a href="https://medium.com/@linoyzaga/empower-women-is-not-a-bad-word-d7d549de14d3">here</a>.</p><p>As I said before, the female environment in the workshop is comfortable and the girls can ask any questions they want, They won’t get answers like “You are a woman, you won’t get it anyway”. This workshop is a place you don’t feel like you need to protect your right to try.</p><p>The workshop actually helped, you can see here a response from one of the participates in the workshop:</p><blockquote>I did not expect to be able to learn so much in 1 day. Everything was very clear and the help from our volunteer was amazing.</blockquote><h3>Conclusion</h3><p>Those events are my way to try to create a more equal world, in which there will be 50% of women inside each room, that we would believe that we can do everything and our society will let us do everything.</p><p>I hope this article has motivated you to work for a more equal world, thank you for reading! Until next time 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f4e641dceb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Streams and Brotli compression in Node.js]]></title>
            <link>https://medium.com/@linoyzaga/streams-and-brotli-compression-in-node-js-fc2507d4d177?source=rss-57a55e350494------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc2507d4d177</guid>
            <category><![CDATA[stream]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[brotli]]></category>
            <dc:creator><![CDATA[Linoy Zaga]]></dc:creator>
            <pubDate>Fri, 13 Dec 2019 19:39:12 GMT</pubDate>
            <atom:updated>2019-12-13T19:39:12.423Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oS9r0b21thegCBt4z2xhIA.jpeg" /></figure><h3>Introduction</h3><p>For a long time in my life as a software engineer, I knew that there is a programming concept named streams, and I knew what it means in general and what it’s used for, but I never really got deeply into it. Until one day my team leader came to me and said: “we have a problem, streams is the solution!”. Well, it’s wasn’t quite so, but you get the picture.</p><p>I’ve started digging, all over the place, just to figure out how it really works. And now I would like to share with you my knowledge, hope it’ll help you in the future.</p><h3>What are stream? And how they work?</h3><blockquote>A <strong>stream</strong> is a sequence of data elements made available over time. A stream can be thought of as items on a conveyor belt being processed one at a time rather than in large batches.</blockquote><p>Confused? me too. Let’s try to use an analogy from our daily life. Imagine you’re waiting to bus number 56 in the bus station. The bus comes, you and several other people going up on it and you go on your way to your destination. After the bus has left the station, some more people came and they’re waiting now for the next bus number 56 to come.</p><figure><img alt="Bus line number 56 picking you up." src="https://cdn-images-1.medium.com/max/1024/1*Jhs3oL7gqqsLq1wPu5dq2A.jpeg" /></figure><p>Streams in Node.js are objects that let you move data from one place (source) to other place (destination) over time. You and all the people that are waiting for the bus are the data, that is being transfer from one place to other. And the bus is the stream, that transfers that data.</p><p>The special thing about streams is that you don’t need to wait for the entire data right now. The data is being transfer in <strong>chunks</strong> in asynchronously way. The same way the bus picks up each time several people on board, and the next one will pick up several other people. Remember this special thing about streams, because we’re going to talk about it in a minute.</p><p>The <a href="https://nodejs.org/docs/latest-v12.x/api/stream.html">Stream module</a> in Node.js is a native module, meaning you don’t need to install a package to use it.</p><p>The question is how this data is actually being moved in streams? If we’ll look at the bus analogy again, we can see that the bus has fixed space to pick up people, and whom ever couldn’t go on it this time, will have to wait in the bus station to the next bus. This fixed space on the bus called <strong>Buffer </strong>in the programming world, and it has a fixed size.</p><p>The chunks of data is the number of people which go up the bus each time, and the fixed space on the bus is the buffer size (remember that we talked about it earlier?).</p><blockquote>The Buffer class in Node.js is designed to handle raw binary data. Each buffer corresponds to some raw memory allocated outside V8.</blockquote><p>The buffers module in Node.js provides a way of handling streams and store binary data. They store the data in the RAM in a binary way (0s and 1s) until they “arrive” their destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*wSxPtO6G9HBGvZaRnNiyEw.png" /><figcaption>Stream Object in Node.js</figcaption></figure><p>In the diagram above we can see an example of how data is being read in chunks from a file via the stream, being stored in a fixed space in the buffer over the stream, and after that being written to a file via the stream.</p><h3>Types of streams</h3><p>There are several types of streams:</p><ol><li>Readable stream — enables read operations via a stream from a specific source.</li><li>Writable stream — enables write operations via a stream to a specific destination.</li><li>Duplex stream — enables both, read and write operations, via two streams, from a source to a destination.</li><li>Transform stream — type of duplex stream, where the data can be modified inside one of the streams.</li></ol><h3>Stream events</h3><p>If we’ve created a readable stream, how would we know when new data was read? Or when is the file completely read? For that case, the stream has events that it can be emit and listen. In this way, on each event we can determine what we want to do on each event.</p><p>Readable stream example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/025d92d36c7e32e81e8caa9d4c040ba5/href">https://medium.com/media/025d92d36c7e32e81e8caa9d4c040ba5/href</a></iframe><p>Writable stream example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ea11b163d111ef31afe28ec716582384/href">https://medium.com/media/ea11b163d111ef31afe28ec716582384/href</a></iframe><p>Looking for duplex stream and transfer stream example? Keep on reading, we’ll get there.</p><h3>Piping in streams</h3><p>If you have two stream (or more) that you want that the output of the first one will be the input of the second one, pipe is the answer for you. Node.js stream module has a ‘pipeline’ function for that particular reason. Pipe enables create a duplex stream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*MpugobMrEA-hYt48Abj29A.png" /><figcaption>Pipe Streams in Node.js</figcaption></figure><p>As you can see in the diagram above, there are two streams with two separate buffers that communicate with each other via the pipe function.</p><p>Duplex stream example - piping readable and writable streams one to another:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/908376883d24134ca017ecca8e0f4e5e/href">https://medium.com/media/908376883d24134ca017ecca8e0f4e5e/href</a></iframe><h3>Where should we use streams?</h3><p>Streams are being used in several operations, mostly when there is a huge amount of data to transfer, or when you need to use chunks of data:</p><ol><li>Read and write to files.</li><li>HTTP requests and response.</li><li>I/O operations.</li></ol><p>Now, when we understand how streams work and we can write streams in our code, let’s understand better how we can transform the data that is being streamed a process of compression via Brotli.</p><h3>What is Brotli?</h3><p>We all know and love Gzip as a compression algorithm, but today we are going to get to know better the new player in town — Brotli.</p><blockquote>Brotli is a generic-purpose lossless compression algorithm that compresses data using a combination of a modern variant of the LZ77 algorithm, Huffman coding and 2nd order context modeling.</blockquote><p><a href="https://github.com/google/brotli">Brotli</a> is developed by Google, it uses a dictionary of common keywords and phrases on the client side and the server side, and it gives a better compression ratio.</p><p>Those are my compression results for <strong>124MB</strong> file with two different compression algorithms: <em>Gzip</em> vs. <em>Brotli</em>.</p><pre>╔═══════════════════╦════════════════════╗<br>║        Gzip       ║       Brotli       ║<br>╠═══════════════════╬════════════════════╣<br>║ Compression Time: ║ Compression Time:  ║<br>║ <strong>1569.767ms</strong>        ║ <strong>142.939ms</strong>          ║<br>║ Compression Size: ║ Compression Size:  ║<br>║ <strong>9MB</strong>               ║ <strong>52KB </strong>              ║<br>╚═══════════════════╩════════════════════╝</pre><p>I won’t going to expend more about the differences between Gzip and Brotli, but if you want to know more you are more than welcome to check out <a href="https://medium.com/oyotech/how-brotli-compression-gave-us-37-latency-improvement-14d41e50fee4">this great article</a> about it.</p><p>The <a href="https://nodejs.org/docs/latest-v12.x/api/zlib.html#zlib_for_brotli_based_streams">Zlib module</a> in Node.js supports brotli stream.</p><h3>Streams and Brotli all combined together</h3><p>For using brotli we need to create a <em>transform</em> stream, as I mentioned earlier, a transfer stream is used to modified data inside the stream. The modification we are going to do with Brotli is compression of the data.</p><p>To create a transfer stream with brotli compression, we’ll have to create two streams — readable and writable. Then, we’ll create a Brotli object (for compression or decompression, as needed). Then, we need to declare with pipe between the stream, that Brotli is our transform.</p><p>Compress stream with Brotli example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c31784e1916129e7ef611021c83e80b6/href">https://medium.com/media/c31784e1916129e7ef611021c83e80b6/href</a></iframe><p>Decompress stream with Brotli example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6bbec921e5f1a2b0fc9f09a03e99fec9/href">https://medium.com/media/6bbec921e5f1a2b0fc9f09a03e99fec9/href</a></iframe><h3>How I used streams with Brotli?</h3><p>As I said before, the main reason to use streams is when there is a huge amount of data to transfer. The use in Brotli compression is to create eventually a compressed file that will contain all of this data.</p><p>My experience with streams and Brotli was when I needed to collect a huge amount of data to the in-memory on my server, and to stream it to a cloud as a compressed file. This compressed file was dowloaded by mobile clients, who saved this data locally on the mobile device.</p><h3>Conclusion</h3><p>In this article we understood how streams work deeply, which types of streams there are and when to use them. We also learn about the compression algorithm Google developed named Brotli and how to create a transform stream with it.</p><p>This is a link to my <a href="https://github.com/linoyzaga/streams-brotli-node">git repository</a> with all of the code you saw here today.</p><p>I hope this article helped you, thanks for reading! Until next time 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc2507d4d177" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>