<?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 Or Seidman on Medium]]></title>
        <description><![CDATA[Stories by Or Seidman on Medium]]></description>
        <link>https://medium.com/@or.seidman?source=rss-75181139df89------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*faxiQLbXsizSooaf</url>
            <title>Stories by Or Seidman on Medium</title>
            <link>https://medium.com/@or.seidman?source=rss-75181139df89------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:15:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@or.seidman/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[Why and How I Became a Full Stack Software Developer]]></title>
            <link>https://medium.com/fiverr-engineering/why-and-how-i-became-a-full-stack-software-developer-863b71afd303?source=rss-75181139df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/863b71afd303</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[fiverr]]></category>
            <category><![CDATA[full-stack]]></category>
            <dc:creator><![CDATA[Or Seidman]]></dc:creator>
            <pubDate>Wed, 22 Dec 2021 08:25:23 GMT</pubDate>
            <atom:updated>2022-03-15T12:34:16.159Z</atom:updated>
            <content:encoded><![CDATA[<p>According to <a href="https://skillcrush.com/blog/what-is-a-full-stack-developer/">Skillcrush</a> A full stack developer<strong><em> </em></strong><em>is “a web developer or engineer , who works with both the frontend and backend</em> <em>of a website — meaning </em>they can tackle projects that involve databases and APIs, build user-facing websites, or even work with clients during the planning phase of projects. In other words, they work both client-side and server-side.<em>”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dbp0mouy8vkUXC5y-NosiQ.jpeg" /><figcaption>Full Stack Developer In Action</figcaption></figure><p>For the last five-and-a-half years (as of Dec. 21), I have been working at <em>Fiverr’s R&amp;D Team</em>. Formally, I still hold my initial, original position, but much has changed since then: the domain, the technology, the teams — but mostly my skills. Fiverr opened the door for me into the world of web development; before, I was working in Java stack, focusing on building tools for developers.</p><p>Like many colleagues of mine coming from similar backgrounds, I started as a Ruby on Rails backend engineer. My client-side knowledge and experience were poor. I had somewhat of a baptism of fire there during my academic studies, but that didn’t continue. While writing backend code during my day-to-day routine, I knew that one day I would enrich my skills and write frontend code.</p><p>From writing one feature to another, I always felt I was missing part of the picture. Yes, we had an API with the front-end developers. Yes, we integrated. Yet I didn’t feel I could track the project from one side to the other. Also, I felt frustrated about not being able to save the time when a production front-end-related bug occurs.</p><p>As the years passed and I felt like I was realizing my potential in the current specialization, my natural growth path was to develop some FE skills. Up until now, we’ve talked about the reasons I became a full stack developer — aka the “<em>Why</em>”. Now, let’s talk about the process — the “<em>How</em>”:</p><p>1 — I took some online courses, in my own time. At some point, I learned the lesson that if I really want something to happen, then I need to take the first step toward it myself. As to the nature of working in high-paced environments, it is almost impossible to stop the world and ask for long-term training on new subjects, especially when it’s not a priority. New products and features will always be prioritized. As for that, I had to give myself some ramp-up work. I started by taking <a href="https://www.udemy.com/course/advanced-javascript-concepts/?utm_source=adwords&amp;utm_medium=udemyads&amp;utm_campaign=WebDevelopment_v.PROF_la.EN_cc.ROW_ti.8322&amp;utm_content=deal4584&amp;utm_term=_._ag_80385735315_._ad_535397279730_._kw__._de_c_._dm__._pl__._ti_dsa-774930035449_._li_1008006_._pd__._&amp;matchtype=b&amp;gclid=Cj0KCQjwqp-LBhDQARIsAO0a6aKF3tR9dZUjfEF91yR3SV-iVd28EpKjYDalma2G6dbBPtwrpxbEcF8aApBVEALw_wcB">this</a> advanced JavaScript online course. After that, I took a <a href="https://www.udemy.com/join/login-popup/?next=/course/react-redux">React components online workshop</a>.</p><p>Here are a few other online courses that I have heard about and might be useful are as follows:</p><ul><li><a href="https://www.codecademy.com/learn/introduction-to-javascript">Codecademy Javascript for beginners</a> (free)</li><li><a href="https://www.udemy.com/course/perfect-react-js-course/">Udemy — Perfect React JS Course for Beginners</a> (free)</li><li><a href="https://www.coursera.org/learn/website-coding">Coursera — Responsive Website Basics: Code with HTML, CSS, and JavaScript</a></li></ul><p>2 — Accomplished simple tasks. I managed to push to my sprints some small tasks of FE. At the beginning, they were tiny — one line of code. Even version updates. And even with those I asked for help, due to my lack of knowledge. The biggest challenge here was understanding the different paradigms being used in the FE environment. But tasks kept coming and coming, and they became bigger and more demanding. Scaling up was challenging as well, mainly when it was for <em>top-of-the-funnel</em> pages. I had to take into consideration all the possible cases, write proper unit tests, and test my code around every existing environment and browser. Not long after I started, I found myself developing new features (which I talked about in <a href="https://medium.com/fiverr-engineering/last-christmas-i-gave-you-my-heart-but-couldnt-plan-my-time-off-7c84d8e1986b">my previous post</a>). I provided end-to-end solutions, starting from the BE — the trivial part — ending with the FE, which was challenging but satisfying.</p><p>3 — Wrote Node.js code — Node.js is a backend JavaScript runtime environment that runs on the V8 engine and executes JavaScript code outside a web browser. Node.js enables developers to use JavaScript for implementing server-side logic. I see Node as a classical starting point for back-end developers to write JavaScript. This is the place where back-end and front-end development meet. When I was working on the Fiverr promoted ads project, I pushed myself to implement server endpoints in Node. I knew it was a good place for me to start and that I could handle it by myself. My initial production code worked, but its quality was poor, and I even ended up being reprimanded by my manager. I had an iteration to finalize, improve, and add a unit test to it. I was satisfied with the final result.</p><p>4 — Found my buddies. When you are surrounded by great developers, it can only be a waste not to learn from them. I am lucky to have extremely talented colleagues in the FrontEnd field. I learned how to build proper DOM and design it with CSS from <a href="https://www.linkedin.com/in/igor360/">Igor Burshtein</a>. I had <a href="https://www.linkedin.com/in/islam-attrash/">Islam Attrash</a> walking me through and explaining legacy code, and I have <a href="https://www.linkedin.com/in/yair-nitzan/">Yair Nitazn</a> mentoring me on a daily basis for best practices. Thank you guys for your patience.</p><p>Lately, I have been developing a core service — in charge of a top-of-the-funnel experience compatible with the new Fiverr architecture. This project included mainly refactoring Node.JS code, which is responsible for <a href="https://www.educative.io/edpresso/what-is-server-side-rendering">server-side-rendering</a>. The project had no product, only infrastructural changes. While developing it, I felt the strength of having foundational knowledge on each part of the system — starting from the database schema change, server’s response change, and the UI result, which should remain the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9rL1QACTMKHfuyrOCTHXg.jpeg" /><figcaption>Architecture Evolution</figcaption></figure><p>Looking at the skills and stack I’ve gained, I am satisfied with where I stand. I think it’s important for web developers to be able to tackle problems from one end to the other. I also think that holding many paradigms in our heads is enriching and makes us better developers. It might not work for everyone, and some would prefer specializing in specific areas, and that’s totally OK if you do. I was always the kind of person who prefers to go above and beyond.</p><p>I would like to take the opportunity to introduce my role model and code mentor who helped me with the process — <a href="https://www.linkedin.com/in/raphael-boukara-b3433a18/">Raphael Boukara</a>.</p><p>I would also like to thank <a href="https://www.linkedin.com/in/einat-mahat-30916824/">Einat Mahat</a>, for inspiring me to write this, and for her endless contribution to the Fiverr engineering culture.</p><p>Fiverr R&amp;D is working with top-notch technology. Our front end stack includes the latest editions of Javascript HTML &amp; CSS along with React (16) framework and TypeScript.</p><p>Fiverr is hiring in Tel Aviv and Kyiv. Learn more about us <a href="https://www.fiverr.com/jobs/?coref=1.10.r6C_60A&amp;t=1638959855760">here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2dlPdnYXO6JmbVJJo0w5Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=863b71afd303" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiverr-engineering/why-and-how-i-became-a-full-stack-software-developer-863b71afd303">Why and How I Became a Full Stack Software Developer</a> was originally published in <a href="https://medium.com/fiverr-engineering">Fiverr Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Last Christmas I Gave You My Heart But Couldn’t Plan My Time Off]]></title>
            <link>https://medium.com/fiverr-engineering/last-christmas-i-gave-you-my-heart-but-couldnt-plan-my-time-off-7c84d8e1986b?source=rss-75181139df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c84d8e1986b</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[fiverr]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Or Seidman]]></dc:creator>
            <pubDate>Tue, 05 Oct 2021 10:50:22 GMT</pubDate>
            <atom:updated>2022-03-15T12:40:45.985Z</atom:updated>
            <content:encoded><![CDATA[<p>Before we start, let me walk you through the short history of the “Unavailable“ feature (aka Vacation Mode) on <a href="http://www.fiverr.com/">Fiverr</a> ( one of the world’s biggest online freelancer marketplace). This feature was born to provide a solution for Fiverr Sellers who wanted to take some time off and go offline without it affecting their reputation. During this away time, the Sellers would be unavailable to receive orders or messages. In the early days of Fiverr, when it was a small, fast growing start up, things were moving fast and features had to be released quickly, so it’s not surprising that the heavy-lifting of this feature was done in a 3-day Hackathon back in 2014.</p><p>But the years have passed, the marketplace grew immensely, many new sellers have joined, and so my former product manager (<a href="https://medium.com/u/59bacf39ec80?source=post_page-----b1e919ffb0e1--------------------------------">Oz Radiano</a>), was asked to come up with a new and improved “unavailable” feature — one that would support scheduled time off and allow sellers to set future dates to plan their unavailability in advance. Although I’m a senior BE engineer, with this feature I was taking my first steps into end-to-end development — from client to server. And as if that on its own wasn’t challenging enough, I also had to write the server side while getting myself familiar with a new language — “<a href="https://kotlinlang.org/">Kotlin</a>” a modern JVM based language.</p><p>I had to start somewhere, and the best place to start is the beginning. So I set up a design review, came up with ideas on how to tackle the challenge (rewriting the current feature using the existing language, <a href="https://www.ruby-lang.org/en/">Ruby</a>) and they got rejected. The main reason for the rejection was the addition of new code to a legacy service, and language (Fiverr R&amp;D is working on deprecating Ruby services). Re-writing the <strong>entire</strong> legacy code was not an option due to the product timeline. So, I had another DR the day after. This time I suggested we’d use the current mechanism as a “blackbox”, while the new part (supporting planned time off) will be written in a new service in “Kotlin” ,with its own DB. The FE solution was trivial — change UI to support “Start date” and send both fields to the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iNyYOurRFXv-cLd9" /></figure><p>Before I could start writing the code, there were two architecture issues to tackle:</p><p>1 — Schedule an “unavailable” mode</p><p>2 — Support hybrid mode for the rollout and test period</p><p>We integrated both into a single solution. We’ve decided to go with a new “sellers microservice” (monolith, if you insist) that will be managing all scheduling approaching the current product (go on ‘unavailable’ mode immediately), as a single use case. The user story goes like this: User asks to become unavailable starting at X. If X is today, call the old service and mark the user as unavailable. Otherwise, put the request in the scheduling queue. For the Scheduling queue, we used our in-house “boomerang” service. This service gets a message by POST HTTP request, specifying the name, payload and the desired time for the callback (in our case, the unavailable day at midnight) and returns to you as a RabbitMQ msg (routing key of the queue is specified in the request) at the specified time. The alternative (and less elegant) solution was to create a queue by having a cron job running on a planned time off DB and handling the request.</p><p>This was the first step taken towards refactoring this feature. In addition to supporting unavailable requests, we also supported deleting planned off modes through our service (which became a proxy service for now). The mentioned blackbox started moving part by part into the new “Kotlin” service, and is soon to be deprecated.</p><p>Retrospectively , deeper thinking of the architecture might have eased the process management, mainly around knowing that having a proxy object can increase the response time, sometimes drastically. Using “Kotlin” as a programming language has many pros — strongly typed (unlike ruby), has a strong and robust web infra, and is easy to run. The main cons of using “Kotlin”, in my opinion, is having a big boilerplate when creating a new service.</p><p>Along with the challenges and tight schedule, we ended up with a shiny product that has been shipped on time and made our sellers happier. This year, we saved them from tears :) Can’t end up without thanking my team who contributed to this effort — <a href="https://www.linkedin.com/in/shiran-honig-5a465011b/">Shiran</a>,<a href="https://www.linkedin.com/in/michelle-fried/"> Michelle</a> and<a href="https://www.linkedin.com/in/nirga/"> Nir</a>.</p><p>Fiverr is hiring in Tel Aviv and Kyiv. Learn more about us <a href="https://www.fiverr.com/jobs/teams/rnd">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WkNtf6Nkd1VDSPaU7DjcaQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c84d8e1986b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fiverr-engineering/last-christmas-i-gave-you-my-heart-but-couldnt-plan-my-time-off-7c84d8e1986b">Last Christmas I Gave You My Heart But Couldn’t Plan My Time Off</a> was originally published in <a href="https://medium.com/fiverr-engineering">Fiverr Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Last Christmas I Gave You My Heart But Couldn’t Plan My Vacation]]></title>
            <link>https://medium.com/@or.seidman/last-christmas-i-gave-you-my-heart-but-couldnt-plan-my-vacation-b1e919ffb0e1?source=rss-75181139df89------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1e919ffb0e1</guid>
            <category><![CDATA[fiverr]]></category>
            <category><![CDATA[vacation-mode]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[refactor]]></category>
            <category><![CDATA[ooo]]></category>
            <dc:creator><![CDATA[Or Seidman]]></dc:creator>
            <pubDate>Thu, 19 Aug 2021 09:46:53 GMT</pubDate>
            <atom:updated>2021-08-19T09:46:53.330Z</atom:updated>
            <content:encoded><![CDATA[<p>Before we start, let me walk you through the short history of the “Unavailable“ feature (aka OOO / Vacation Mode) on <a href="http://www.fiverr.com/">Fiverr</a> (the world’s biggest online freelancer marketplace). This feature was born to provide a solution for Fiverr Sellers who wanted to take some time off and go offline without it affecting their reputation. During this away time, the Sellers would be unavailable to receive orders or messages. In the early days of Fiverr, when it was a small, fast growing start up, things were moving fast and features had to be released quickly, so it’s not surprising that the heavy-lifting of this feature was done in a 3-day Hackathon back in 2014.</p><p>But the years have passed, the marketplace grew immensely, many new sellers have joined (particularly at the height of the pandemic), and so my former product manager (<a href="https://medium.com/u/59bacf39ec80">Oz Radiano</a>), was requested to come up with a new and improved Out Of Office mode — one that would support scheduled vacation and allow sellers to set a future date for their time off (plan their unavailability beforehand). Although I’m a senior BE engineer, in this feature I was taking my first steps in end-to-end development — from client to server. And as if that on its own wasn’t challenging enough, I also had to write the server side while getting myself familiar with a new language — <a href="https://kotlinlang.org/">Kotlin</a> a modern JVM based language.</p><p>I had to start somewhere, and the best place to start is the beginning. So I’ve set up a design review, came up with ideas on how to tackle the challenge (rewriting the current feature using the existing language, <a href="https://www.ruby-lang.org/en/">Ruby</a>) and got rejected. The main rejection reason was the additional of new code to a legacy service, and language (Fiverr R&amp;D is working on deprecating Ruby services). Re-writing the <strong>entire</strong> legacy code was not an option due to the product timeline. So, I had another DR the day after. This time I suggested we’d use the current mechanism as a “blackbox”, while the new part (supporting planned vacations) will be written in a new service in Kotlin ,with its own DB. The FE solution was trivial — change UI to support “Start date” and send both fields to the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e56hp16BC02x7wUwi6hT7A.png" /></figure><p>Before I could start writing the code, there were two architecture issues to tackle:</p><p>1 — Schedule a vacation</p><p>2 — Support hybrid mode for the rollout and test period</p><p>We integrated both into a single solution. We’ve decided to go with a new “sellers microservice” (monolith, if you insist) that will be managing all scheduling approaching the current product (go on vacation immediately), as a private case. The user story goes like this: User asks to go on vacation starting at X. If X is today, call the old vacation service and put the user on vacation. Otherwise, put the request in the scheduling queue.</p><p>For the Scheduling queue, we used our in-house “boomerang” service. This service gets a message by POST HTTP request, specifying the name, payload and the desired time for the callback (in our case, the vacation day at midnight) and returns to you as a RabbitMQ msg (routing key of the queue is specified in the request) at the specified time. The alternative (and less elegant) solution was to create a queue by having a cron job running on a planned vacation DB and handling the request.</p><p>This was the first step taken towards refactoring this feature. In addition to supporting vacation requests, we also supported deleting planned vacation through our service (which became a proxy service for now). The mentioned blackbox started moving part by part into the new Kotlin service, and is soon to be deprecated.</p><p>In a retrospective view, a deeper thinking of the architecture might have eased the process management, Mainly around knowing that having a proxy object can increase the response time, sometimes drastically. Using Kotlin as a programming language has many pros — strongly typed (unlike ruby), has a strong and robust web infra, and easy to run. The main cons of using Kotlin, in my opinion, is having a big boilerplate when creating new service.</p><p>Along with the challenges and tight schedule, we ended up with a shiny product that has been shipped on time and made our sellers happier. This year, we saved them from tears :) Can’t end up without thanking my team who contributed to this effort — <a href="https://www.linkedin.com/in/shiran-honig-5a465011b/">Shiran</a>,<a href="https://www.linkedin.com/in/michelle-fried/"> Michelle</a> and<a href="https://www.linkedin.com/in/nirga/"> Nir</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1e919ffb0e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>