<?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 The eko Devs on Medium]]></title>
        <description><![CDATA[Stories by The eko Devs on Medium]]></description>
        <link>https://medium.com/@ekoDevs?source=rss-171dd0aa49dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*hLdapp7w1bErxQHrG1i4rw.jpeg</url>
            <title>Stories by The eko Devs on Medium</title>
            <link>https://medium.com/@ekoDevs?source=rss-171dd0aa49dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:10:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ekoDevs/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 we decided to take the lead on hiring new developers]]></title>
            <link>https://medium.com/ekoengineering/why-we-decided-to-take-the-lead-on-hiring-new-developers-b6be7494c888?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6be7494c888</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[job-interview]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Thu, 09 Sep 2021 13:48:02 GMT</pubDate>
            <atom:updated>2021-09-09T13:48:02.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kbxE7BssKKtd3yl9LDEgVg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Last year when the pandemic broke out, everyone assumed companies would downsize or close, that there would be an abundance of unemployed developers, and that recruiting would be easy.</p><p>Boy, were we wrong.</p><p>With an all-time high in funding rounds and new Israeli unicorns, the competition for top talent has never been greater. How much greater? Some estimate developers in Israel get up to <a href="https://www.themarker.com/podcasts/.premium-PODCAST-1.9945396">eight job offers a day</a>(!), which means you gotta move fast. Really fast.</p><p>So, how do companies quickly evaluate someone’s ability to code before they decide to hire them?</p><p>They use technical interviews.</p><p>Technical interviews have many different formats. Some popular ones are code reviews, algorithmic questions, at-home programming challenges, and even “guestimations” like “how many weddings are held each day in Melbourne?”.</p><p>The problem with many of these tests is that interviewers and interviewees turn to Google or popular resources like Gayle Laakmann McDowell’s <a href="https://www.crackingthecodinginterview.com/">“CRACKING the CODING INTERVIEW”</a> for both the questions and the answers, turning technical interviews into nothing more than a pre-rehearsed formality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*giuSXLQDrB4ywf6RsMvKYw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4><strong>Where do great developers come from?</strong></h4><p>Talented developers come from many educational backgrounds. Most have computer science degrees, some are incredibly curious autodidacts, and others went to coding bootcamps.</p><p>Coding bootcamps promise to turn students into developers in a very short time, and one thing they teach their students very well is how to build a strong online presence, the kind that leads recruiters to view them as more experienced than they actually are.</p><p>Since great developers really can come from anywhere, you don’t want to rule someone out just for being a bootcamp graduate. This leaves it to the technical interview to discern between the developers who look great and the ones who are great.</p><h4><strong>What makes a truly great developer?</strong></h4><p>Being a great developer is about so much more than writing code.</p><p>We write code to serve a specific need or solve a problem. Developers tend to find solutions that match their skillset and enforce the problem at hand to fit into the framework or language they’re familiar with. However, great developers know that no technology is perfect and that there are always tradeoffs. Any technology or programming language has its advantages and disadvantages, which is why excellent developers must first and foremost understand the need they’re trying to answer and the logic behind different choices. The more you know, the more options you have to deal with a problem.</p><p>While developers must be able to break down a problem and understand how systems work to see the bigger picture, they also have to be exceptionally good at communicating these things to other people. A lone coder might be an excellent problem-solver, but they can’t work within a team without good communication skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9UNxN6BFiP5IOMOtpd9TcA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4><strong>What developers are we looking for?</strong></h4><p>We work in diverse, multidisciplinary teams that approach problems from a broader perspective. In our eyes, it doesn’t make sense to take talented individuals and box them in job descriptions. Gifted developers can have any engineering background, like real-time, frontend, backend, or data. Being great is not about writing in a particular programming language. If you’ve got a theoretical understanding and strong analytical and problem-solving skills, picking up a new language will not pose a hurdle. Besides, tech stacks change and evolve all the time, so continuous learning is crucial for developers anyway. We’re looking for talented people regardless of their specific technological history. We’ll always find them incredible things to do.</p><h4><strong>Our technical interviews</strong></h4><p>Because we use such a <a href="https://medium.com/ekoengineering/how-we-structured-our-engineering-team-for-happier-more-productive-devs-even-in-times-of-crisis-79ece8b3db92">different organizational model</a> for the eko dev team, our technical interviews also tend to take a different course.</p><p>In one format, we ask developers to walk us through a project they’ve already completed at work, school, or on their own, and before we even get to the code — we want to know what goals they were trying to accomplish and for what purpose.</p><p>We ask our candidates why they made technical choices and how they handled problems, not because we’re trying to judge their decisions but rather to understand their way of thought. We also ask follow-up questions like “what would you change if X would be different?” or “how would you approach this project differently if you had to do it over again today?” Since the conversation is about something candidates have already accomplished — they feel comfortable and free to go as deep as they want into a topic they know.</p><p>In another type of technical interview, we ask candidates to solve a software problem outside their area of expertise. Then, we discuss it together to explore how they defined the problem, if they understood the need behind it, why they chose the technologies they did, how they planned their architecture, design, and APIs, and finally — we examine their coding skills.</p><p>These kinds of open discussions provide a pretty accurate simulation of what it’s like to work on a feature at eko while helping us identify great developers.</p><h4><strong>What we actually mean by “great developers”</strong></h4><p>Great developers understand the many layers of abstractions that make their software run and the deeper layers of other software (and hardware!) their code relies on to function. For example, a good frontend developer might be proficient at crafting CSS animations, but a great one will also understand the browser rendering process, how and why does the GPU come into play, and even how it all fits within the context of the OS and device the browser runs in.</p><p>The approach a developer takes to the practice of programming also talks a great deal about their proficiency. Other than addressing the task at hand, do they handle the less optimistic paths (errors and failures)? How do they test and using which testing methodology and why? What do they log, and how do they make sure to separate the wheat from the chaff? After all — it’s not all about writing code “that just works”. It’s about looking at the entire picture of programming in an organization: making that code solid and trustable, debuggable, maintainable, and readable to other humans (and themselves, in the future).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVgZfgbaEU4N4zyqWEUXTg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4><strong>How does all of this help us move fast?</strong></h4><p>Well, since we are, in fact, developers ourselves, we can figure out who’ll make an excellent professional match to our team a lot quicker than “someone from HR”.</p><p>Plus, because we’re the ones doing the interviews, candidates get to meet the people they’ll be working with right from the very start. And thanks to our <a href="https://medium.com/ekoengineering/how-we-structured-our-engineering-team-for-happier-more-productive-devs-even-in-times-of-crisis-79ece8b3db92">flat organizational structure</a>, we don’t need approvals from five layers of management when we meet someone we like.</p><p>…</p><p>Want to see for yourself what an eko technical interview looks like? Send us your resume <a href="https://eko.engineering/">here</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6be7494c888" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/why-we-decided-to-take-the-lead-on-hiring-new-developers-b6be7494c888">Why we decided to take the lead on hiring new developers</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning a new page: saying farewell to eko dev, Divya Mahadevan]]></title>
            <link>https://medium.com/ekoengineering/turning-a-new-page-saying-farewell-to-eko-dev-divya-mahadevan-942049eb8216?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/942049eb8216</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[office-culture]]></category>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Wed, 23 Jun 2021 14:55:10 GMT</pubDate>
            <atom:updated>2021-06-27T06:48:58.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-U9p7JsMO8l2BqpBUPB4iA.png" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>At the end of the month, we’ll be saying goodbye to Divya Mahadevan, one of our NYC-based developers and an excellent person regardless. Divya has been accepted to the Digital and Social Change Masters program at the University of Oxford, so we know she’ll literally be making the world a better place.</p><p>We took this chance to sit down and talk to Divya about her 2 years and her many contributions here at <a href="https://eko.com/">eko</a>, her many passions, her future plans, and wish her the absolute best in all her future endeavors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpdVURLL9ID5_ldztLw6dA.jpeg" /><figcaption>Divya Mahadevan</figcaption></figure><h4>What’s your role here at eko, and what do you love most about it?</h4><p>I’m a developer at eko, and I’ve been working here for almost 2 years. I think what I love most is that I get to work on a wide variety of problems and work with many different people both inside and outside of the company. I’ve worked with people from <a href="https://eko.com/shows/create-with-me/">Walmart</a>, <a href="https://eko.com/shows/buzzfeed-tasty-eko/">Tasty</a>, and even <a href="https://medium.com/ekoengineering/first-interactive-ad-in-the-super-bowl-3cac52fccb46">Fox</a> broadcast engineers. Within the company, I’ve worked across the stack, from <a href="https://github.com/EkoLabs/sonorous">Sonorous</a>, an open source WebAudio library, to a content management API to the player controls UI. I think it’s cool that everyone here works on so many different products — it means that everyone has a stake in everything and really cares about the work we’re doing.</p><h4><strong>How has your workday changed since the pandemic? Did anything change for the better?</strong></h4><p>In a lot of ways, my job didn’t really change that much. Even before the pandemic, I could be considered a “remote worker” since there are only 3 devs in NYC, with the rest in Tel Aviv. The majority of my meetings were over Zoom ~before it was cool~. There are definitely pain points with remote work, and I think our entire team grew to appreciate and address those pain points more when we all entered lockdown. When everyone is remote, you end up getting included more in impromptu conversations that you would’ve had no clue were happening otherwise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_krCzHFANosWuOrDpoX5g.jpeg" /><figcaption>Locking down.</figcaption></figure><h4><strong>What will you do next?</strong></h4><p>In the fall, I’ll be attending the University of Oxford as part of their Digital and Social Change Masters program. I’ll be studying how we can use technology to reduce inequities in education. Given the amount of Zoom school that’s been happening this past year, I think it’s a fascinating time to take a step back and critically examine how technology can be used in schools and its effect on student learning.</p><p>But if you’re looking for me over the summer, you’ll probably find me at the beach. :)</p><h4><strong>How would you describe your job to a child?</strong></h4><p>Imagine you were watching your favorite show, but you could decide how your favorite character behaves. I help build videos that let you do that! There are 2 big buckets of problems you encounter when making videos like this: “how do you make a video that has choices in it?” and “how do you watch it once you’re done making it?”. The technology I build answers those 2 questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSShnlFGbnjrgkKjVGC_ZA.jpeg" /><figcaption>Divya airing the first interactive ad at the Super Bowl.</figcaption></figure><h4><strong>Tell us about a time when your input made an impact.</strong></h4><p><a href="https://www.walmart.com/cp/paint/1067617">Walmart Paint Finder</a> immediately comes to mind. Paint Finder is our latest experience, which helps you decide which color paint you should buy to paint a room. Normally, when building an eko video, you have a different video for each choice you make. So, if I have 3 different paint color options (i.e., red, green, blue), I would normally need to supply 3 different videos (1 video with red walls, 1 with green walls, 1 with blue… you get the idea). In Paint Finder, you have 5 different room options (bedroom, bathroom, etc.), 3 different styles for each room, and 48 different paint colors to choose from. 5 x 3 x 48 = 720. That’s a lot of videos!</p><p>I have a computer graphics background, which means I love working with shaders and filters and other low-level WebGL graphics-y things. I had already been messing around with building a chroma key (green screening) algorithm that was compatible with our player technology. This seemed like the perfect solution for Paint Finder; instead of having a different video for each paint color, you could supply 1 video — and my algorithm could programmatically change the color of the walls. So, instead of 720 different videos, you would only need 15. Much better!</p><h4><strong>What was your most challenging experience as a developer?</strong></h4><p>I came to eko with very, very little web experience. Until then, I worked as an iOS developer and never spent much time working with web technologies. I was really nervous because there are so many different aspects to web technology, and all of it was foreign to me (Docker? Never heard of her. AWS? Witchcraft, as far as I was concerned.) I didn’t even really know JavaScript before I started. It’s been ~2 years, and I’ve learned so much. I know I still have a long way to go before considering myself an AWS expert, but I feel much more confident about my ability to learn everything I need to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETQtf_hr_3qX6UKfmATFCQ.jpeg" /><figcaption>Planning how to tackle the beer surplus.</figcaption></figure><h4><strong>What are you passionate about? What do you love doing (besides writing code)?</strong></h4><p>Ha. I think I have too many passions. I’m passionate about equitable access to education and love working with kids, so I’m currently teaching intro computer science to a class of high school students in Brooklyn. I love cooking, so I’m working on a cookbook of my grandmothers’ recipes. I love art and animation, so I’m always drawing or modeling/shading/rendering scenes. I love being active and exploring new places, so you can catch me wandering around Brooklyn most weekends.</p><h4><strong>When did you discover your love of teaching?</strong></h4><p>My love of teaching stems from my love of storytelling. I think there’s something so special in the exchange between storyteller and listener, both so engaged and captivated by the story. At some point, I realized that teaching is just another form of storytelling. My history teacher in high school was also the drama director, and his animated portrayal of American history made it much more exciting to learn. From then on, whenever I had study groups with my friends, I would try to turn whatever we were learning into a story. It certainly helped things stick in my brain more. In college, I was a teaching assistant for an introductory computer science class for 3 years. As cheesy as it sounds, I really loved seeing the “aha” moment when something finally clicked for my students.</p><p>As an aside, I think the reason I love teaching is the same reason why I applied to eko in the first place. I love this idea of tech creating new forms of storytelling and storytelling creating new forms of tech. Eko really encompasses that idea, and I can’t wait to see how it pushes the boundaries of storytelling further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*vkIuKp-eqZ3MR5FJEXrUDQ.jpeg" /><figcaption>Once a teacher, always a teacher :)</figcaption></figure><h4><strong>What’s your most memorable work-related facepalm moment?</strong></h4><p>Hmm…There was one that happened a few weeks ago. I was working on this bug where the video kept flickering. I spent days agonizing over how to fix it, and nothing was working. I finally asked Tomer, our Director of R&amp;D, for help, and within 5 minutes, he was like, “have you tried commenting out this one line?” The line in question even had a comment above it that said something like “black frame flicker might occur.” That ended up not being the issue, but still — big facepalm moment.</p><h4><strong>If you could choose anyone alive or dead to be your mentor, who would you choose?</strong></h4><p>Tough question! The first name that comes to mind is Ada Lovelace, who is credited as one of the first computer programmers. She had an interesting life from the get-go: her father was Lord Byron (a poet…among other things), and her mother, Lady Byron, was a mathematician. She carried both of these identities with her throughout her life and considered herself a “poetical scientist.” She’s largely credited as the first person to think about what computers could do outside of crunching numbers. She raised a lot of questions about the relationships among technology, society, and individuals. I think she’d be fascinating to talk to and learn from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GbtIoI6_4TKZhCmGGpTXaA.jpeg" /><figcaption>Divya &amp; Louai at Fox.</figcaption></figure><h4><strong>What will you miss most about eko?</strong></h4><p>Hands down, the people (to both questions). Everyone here has such an interesting background and is so passionate about the work they do. Moreover, there are no egos- — you can walk up to anybody and ask any question, and they’ll be happy to answer. Particularly on the dev team, I think there’s a sort of fearlessness that I haven’t experienced before. Like, if you have an idea — even if it’s something radical like “Hey, let’s rewrite this entire module,” or “Hey, let’s try out this new technology and completely overhaul our existing workflows” — nobody will stop you from trying it out and making it happen!</p><p>I’ll definitely miss that fearless and supportive environment and working with all of these insanely genius developers. I came to eko not knowing anything about web development and learned so much about how to be a better developer and coworker from this team. I know I’ll carry these lessons with me into the future, and I can’t wait to see what comes next for eko.</p><p>Thank you, Divya. We know this is such an amazing opportunity for you, but we still can’t believe you’re leaving.</p><p>There’s a pair of big shoes to fill on our dev team…if you want to try them on, get in touch with us <a href="https://eko.engineering/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m0UQNyz2ssYWWpqgHy9RyA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=942049eb8216" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/turning-a-new-page-saying-farewell-to-eko-dev-divya-mahadevan-942049eb8216">Turning a new page: saying farewell to eko dev, Divya Mahadevan</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Spotlight: Asaf Menahem]]></title>
            <link>https://medium.com/ekoengineering/developer-spotlight-asaf-menahem-6e18e753e509?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e18e753e509</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[office-culture]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Mon, 03 May 2021 11:16:29 GMT</pubDate>
            <atom:updated>2021-05-03T11:16:29.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LWspa1Z2y-4bJ4j5D60ANA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Introducing Asaf Menahem, an eko software developer and the latest subject in our Developer Spotlight series! We spoke to Asaf about a variety of topics, including the many contributions he’s made in his 7 years at eko, working on eko’s latest open source project, iFramily, and bringing his dog to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0mQvq8hBH9gmohyC9Nq5cw.jpeg" /><figcaption>Asaf, looking like a boss ;) (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><h4><strong>What’s your role here at eko, and what do you like most about it?</strong></h4><p>I’ve been a full-stack software developer at eko for the past 7 years. My job includes everything from fixing minor bugs to designing and leading projects from scratch. I also do system designs, DevOps jobs, job interviews, employee training, and more. That’s something I really like about eko — I’m not just doing one particular job. It’s very diverse and challenging.</p><p>Sometimes people ask me, “What’s the point of working at one company for seven years? Leave and find another place, something that will challenge you.” But there <em>are</em> professional challenges here, and work is never dull. Why leave a place that good? Plus, eko is always growing and adjusting its business strategy, improving its product, and advancing its technology to build new things and make them a reality. I love it.</p><p>Other than that, the people here are amazing and fun to be around, in and out of the office.</p><h4><strong>What does your typical workday look like?</strong></h4><p>First of all, I open the day with tea! I’m a big tea fan, in winter <em>and </em>summer. I even had my own office cup, which everyone knew was risky to use since I didn’t wash it very often.</p><p>Then, I go through my emails, Slack messages, and task lists. Then I prioritize what to do first and hope I accomplish everything. I spend half of my time in meetings and working with other developers, and the other half getting half of my tasks done.</p><p>Before COVID, I’d bring my dog to work. Even though he’s huge, I’d forget that he was even there, except for when he’d bark at delivery guys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3aqJQY3yYhRYabX9RqrKvQ.jpeg" /><figcaption>That’s a lot of puppy love ❤ (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><h4><strong>Tell us about a time when your input made an impact?</strong></h4><p><a href="https://studio.eko.com/">Eko Studio</a>, our creators’ tool, was and still is a web-based tool. It’s part of our original ideology that it should be free and easy to use for everyone. This approach was the backbone of eko Studio for the last 5 years. But I thought that for eko Studio to be even more impactful for production houses, we needed to make it a native desktop app — the premier software for interactive videos, just like Adobe is for video editing. This was a change in the company’s mindset and very different from what most companies do, move to cloud or web solutions. This paradigm shift was not easy to convey. But I started to convince everyone that it was the right approach. This opened the door for our new eko Studio 2, a tool for professional creators. It was a pivotal moment for the company.</p><h4><strong>What was your most challenging experience as a developer?</strong></h4><p>It’s a little weird, but I think my most challenging experience was when I started working here. I really wanted to prove myself. And as a first project, I was asked to write a system for running automated tests. In retrospect, I didn’t get that the first project was supposed to be fun. So, of course, I took it seriously and thought about it a lot, not only at work but also at home. I consulted with friends and built a very complex system. It turns out it was just an exercise to get me into things, but it was an experience that I remember to this day because it was so weird, and I was so invested since I thought it had to be perfect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zNVHVfCm73qeMPe45DU4qw.jpeg" /><figcaption>Automated tests? A piece of cake… (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><h4><strong>What are you passionate about? What do you love doing (besides writing code)?</strong></h4><p>Definitely music. I’m into playing the guitar, keyboard, and a bit of drums. My real passion is to create. I had a small band, nothing serious, for a short time. I love making things from scratch. However, I’m not some overly talented person. If you let me draw a cow, some obscure creature will come out. But when I play music, I really enjoy it, even if I don’t end up getting a final product. The process of writing and composing something is really fun. My roots range from ’80s electronic to old and progressive rock. There was a period when I liked blues more. Now I’m more modern, pop and electronic. However, beautiful guitar pieces are a weakness of mine. Writing lyrics is the hardest part, but when I create music, it’s incredible. Sometimes I find myself having more fun not aiming to compose something but enjoying the process; if something good comes out, then great, and if not, that’s also ok.</p><h4><strong>What’s your most memorable facepalm moment?</strong></h4><p>When I was a computer science student, Israel was at war, and we had many missile alerts. A few months later, I woke up to a very loud siren. I was terrified. I quickly got up and knocked on my roommate’s door to wake her up, but she wasn’t there. I went down to the shelter and waited and waited until the siren ended; I was alone. I went back upstairs and turned on the TV to see what was happening. I saw there were Remembrance Day ceremonies and realized that the siren was for that. I felt really stupid. I was so glad my roommate wasn’t there; otherwise, many people would have known about my horrible mistake. But now everyone will know anyway. :)</p><h4><strong>If you could choose anyone alive or dead to be your mentor, who would you choose?</strong></h4><p>Mentor is a hard word, but I would go for George Harrison from the Beatles because I’m crazy about him in many ways — musically, spiritually, and personally. I feel like he could be a good mentor. I’d like to be more like him. I also wouldn’t object to some guitar lessons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kjvp4NBWHb_zFMglrvkJlA.jpeg" /><figcaption>Hello there! (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><h4><strong>What was your favorite video game as a kid?</strong></h4><p>Easy, a game I’ve played for hours on end for years: Quake II — a shooters game. It grabbed me so strongly because it was one of the first online FPS games. There was a community of people playing against each other, and you could expand and change the game with all kinds of mods they created. I was a teenager and had a lot of free time (at the expense of homework, of course). I got addicted. It was really cool.</p><h4><strong>What does success mean to you?</strong></h4><p>Is there a non-cheesy answer to this question? The most important thing is being happy and really having fun; otherwise, what’s the point?</p><h4><strong>What has changed for the better this year?</strong></h4><p>There aren’t many good things I can attribute to this year. However, I do like social distancing. I would be happy to stay at home, but I know it won’t last. And at least the traffic jams are gone for a while, though they’ll come back soon.</p><p>Also, great things happened in my personal life. My wife &amp; I moved the family to a new apartment and had another daughter.</p><h4><strong>What are you missing from work pre-pandemic?</strong></h4><p>I miss the office interactions, being face to face or shouting at someone for a moment. Zoom sessions don’t convey the same feeling, and when I’m trying to do something, it usually comes out awkward.</p><h4><strong>Tell me about your Open Source project.</strong></h4><p><a href="https://github.com/EkoLabs/iframily">iFramily</a> is a library designed to facilitate inter-frame communication. It wraps the cumbersome use of inter-frame communication today and provides a more convenient interface for the developer that focuses on ease and simplicity, especially when two-way communication and multiple frames are required.</p><p>We use iframes a lot at eko to provide the code with an isolated environment, even if those iframes are embedding our own sites. A few years ago, we wanted to simplify communication with these frames. I wrote an internal library that turns the basic communication that HTML provides (postMessage) into something more modern and convenient. At the time, I was looking for libraries that do this and couldn’t find any. Today it’s a different story, and there are quite a few similar libraries with different approaches. Over time, we saw that the library was really easy to use and started using it in various products. We decided to open source it because we believe in sharing it with other developers. We have other open source libraries like <a href="https://github.com/EkoLabs/sonorous">Sonorous</a> and <a href="https://github.com/EkoLabs/react-native-background-downloader">react-native-background-downloader</a>.</p><p>Like what you’re reading? Check out <a href="https://github.com/EkoLabs/iframily">iFramily</a>, and learn more about the possibilities at <a href="https://eko.engineering/">eko Engineering</a>.</p><p>Wanna bring <strong>your </strong>dog to work? <a href="https://eko.engineering/#careers">Send us your resume!</a></p><p>And take another look at our <a href="https://medium.com/ekoengineering">Medium</a> page to meet some of Asaf’s co-workers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*td5ziHzKlrklloOZWRafJA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e18e753e509" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/developer-spotlight-asaf-menahem-6e18e753e509">Developer Spotlight: Asaf Menahem</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2020: Our Year in Numbers]]></title>
            <link>https://medium.com/ekoengineering/2020-our-year-in-numbers-c4bdc6128d99?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4bdc6128d99</guid>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[interactive-video]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Tue, 16 Feb 2021 13:25:11 GMT</pubDate>
            <atom:updated>2021-02-16T16:18:25.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X41ctZt9udM2kWtKAMgIKA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>A year ago, we published our <a href="https://medium.com/ekoengineering/2019-our-year-in-numbers-3ac763976eac?source=friends_link&amp;sk=ec07ee0cb2666c7989390efc80a94251">2019 summary</a> — calling it “one of our most ambitious years yet.” Not only did we meet our goals, we also surpassed every expectation. We raised a toast to our achievements then went right back to business, setting even more so-called “unrealistic” goals for 2020, which is how we’ve always done things here at eko Engineering.</p><p>However, no one could’ve prepared us for what was to come. The pandemic forced us to work from home and change the way many things get done around here. However, we didn’t let all these changes discourage us from our ultimate goal of pushing the boundaries of choice-driven entertainment. And judging by these numbers, we knocked it out of the park.</p><p>So, without further ado, let’s check out a few of our 2020 highlights!</p><h4><strong>In 2020, our viewers spent 6,618,273,177 seconds on the eko platform.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TUhr_PiI96vKcF2Szjq4sA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>That’s almost 210 years of video and 16% more time spent on the platform than in 2019. Insane!</p><h4><strong>Our viewers made 142,060,735 choices — creating 1,956,374,290 data events.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9lxMf8Tr9t8yvnsp89gOQg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Our viewers made <strong>more than seven times</strong> the amount of choices they made in 2019! 🤯 Proving just how much they love to choose for themselves, our viewers created over 15,000,000 data events per hour in only one of our December 2020 peak viewing times.</p><h4><strong>We added 913,160 lines of code and removed 521,970.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BRA0JL8KnP1lvDLpycF-vg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>That’s 156,412 more lines added than in 2019 and 18,085 more removed, in just 7,130 commits.</p><p>Wow! We really put our fingers to work this past year…</p><h4><strong>27,586 projects were published in eko Studio.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVXbQVh-z4XRKzvpZ8S6RQ.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Eko Studio is a powerful and free web application allowing creators to build interactive projects and publish them to the cloud. It’s easy to learn and easy to customize if you know a bit of code.</p><p>Refinery29’s interactive <a href="https://eko.com/shows/60-second-cities-the-world-your-way/">60 Second Cities</a>, the <a href="https://eko.com/shows/eko-buzzfeed-quizzes/cuppy-fortune-teller/">Cuppy Fortune Teller</a> by BuzzFeed, and <a href="https://eko.com/shows/sweet-digs-interactive/">Sweet Digs</a> Interactive are just a few of the fun projects created in 2020.</p><h4><strong>The longest eko project was published, at 115 minutes.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoKn8prb4tVpttA7zm9GMg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>The 2-hour long <a href="https://www.myfestigal.co.il/">My Festigal</a> main event wasn’t just the longest project published on the eko platform in 2020 — it was the longest one <em>ever</em>. With that said, the “most nodes (video segments) in one project award” actually goes to Secret Society: Leading Ladies, with 1,490 nodes. The second runner up has 936 nodes, an <a href="https://video.eko.com/v/Md4LLn">interactive guided tour in Warsaw, Poland</a>!</p><h4><strong>We launched the Walmart Cookshop inspiration hub with 21 original episodes featuring 280 recipes.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VtK-QCPevUq-OhF-6vdnmA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Walmart <a href="https://cookshop.eko.com/">Cookshop</a> serves up an array of delicious recipes by some of your favorite chefs. Each episode allows viewers to customize the recipe according to food preferences and restrictions and then finishes with a shopping cart to purchase all the ingredients. It’s a dream to have a personal chef at home, but the next best thing is continually getting new interactive video recipes directly to your screen from the masters.</p><h4><strong>It took us 4 months to create and publish Camp. It now has 160 episodes and 9.2M total interactions.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omWP88iztFxttoH6e5auHA.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p><a href="https://camp.eko.com/">Camp by Walmart</a> is a partnership between retail giant Walmart, the children’s retail and experience store CAMP, and us. With summer activities cancelled due to the pandemic, we wanted to build something that brings families closer together and created an interactive digital camp experience they can enjoy from the safety and comfort of their homes. With A-list celebrities hosting fun classes, and each episode providing the option to buy art supplies, materials, and other fun objects associated with the video, Camp was always in session in 2020! (Literally: the success of Camp over the summer inspired Walmart to extend the experience through the holidays and into the new year!)</p><h4><strong>943 (and counting) interactive product “Try &amp; Buy” videos on Walmart.com</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lO0U7CuY4KBcpz8DjN56Zw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Eko-powered interactive videos give consumers a chance to “try out” hundreds of products across dozens of categories, before buying them on Walmart’s website.</p><p>Like this <a href="https://www.walmart.com/ip/Oreo-Christmas-Ultimate-Dunk-Gift-Set-2-count/256611497">Oreo Ultimate Dunk Set</a>, or this <a href="https://www.walmart.com/ip/Blackstone-4-Burner-36-Griddle-Cooking-Station-with-Hard-Cover/578992934">Blackstone 4-Burner 36&quot; Cooking Station</a>, helping shoppers choose between different sizes, flavors, colors, and other fun feature combinations.</p><p>What a fantastic year! We hit the ground running, and we didn’t stop. Our content exploded, and we’re bursting with more exciting ideas. Developers, <a href="https://eko.engineering/">join us</a> at eko to make these ideas a reality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4bdc6128d99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/2020-our-year-in-numbers-c4bdc6128d99">2020: Our Year in Numbers</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Spotlight: Maayan Arbiv]]></title>
            <link>https://medium.com/ekoengineering/developer-spotlight-maayan-arbiv-10dcf3db0049?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/10dcf3db0049</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[office-culture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[devlife]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 12:14:58 GMT</pubDate>
            <atom:updated>2021-02-03T12:14:58.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9f8RVCIl533mtF_Y0gq-A.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>We’re delighted to start this new year with another article from our Developer Spotlight series featuring Maayan Arbiv.</p><p>Maayan has been programming with us for 7 years. She’s extremely dedicated to her work yet always makes time for coffee with her fellow devs (that’s us!). We’re excited to have her with us and for you to get to know her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zo4hRYNnu6ekMW1r1KE-g.jpeg" /><figcaption>“Coffee, anyone?”</figcaption></figure><h4>What’s your role here at eko, and what do you love most about it?</h4><p>I’m a programmer, developer, or whatever you want to call it. What I love most about my job is the work itself. It forces me to think.</p><p>What’s fun about my job is that I love the people, which is the most important part. Beyond that, I really like our product. I worked on its core during my first years here at <a href="https://eko.com/">eko</a>. It was super exciting and challenging, and most of the things we do today are built on top of that.</p><p>Being an eko dev is always interesting and challenging. You jump from one thing to the next, and it’s never dull. There’s always something to do, and because we work in an extreme ownership model, when you have a project, you build it from scratch; you plan it, design the architecture, talk to all the relevant people, and lead it from start to finish. It’s great because you get to see the full picture and everything you need to develop something, like QA or devops, for example. The more parts you see, the more you’re able to think for yourself. That’s the advantage of smaller companies, it’s really fun. And if it isn’t, you should be doing something else.</p><h4>How long have you been working at eko?</h4><p>I’ve been at eko for 7 years. One of eko’s most significant advantages is that people work here for a really long time, which isn’t very common with tech companies. It really resonates with potential candidates when we tell them that. I like coming to the office. I like talking to people and hanging out with them.</p><h4>What did your typical workday look like in 2020?</h4><p>Except for lockdowns, I kept coming to the office. We were so used to just sitting together and talking face-to-face whenever we had questions that when the first lockdown started, it took us a couple of weeks to adjust to this new situation of working from home and collaborating on Zoom. At first, things were a bit messy. But once we figured it out, we became very organized. Zoom forced us to work on a schedule, show up to and end meetings on time. For each new feature release, our CTO, Yuval Hofshy, sent a team-wide announcement so anyone could join the Zoom sync meetings if they wanted to.</p><p>I start my days early, and lockdowns made me begin even earlier. I usually sit down to work at 8:30, so I have about two hours of quiet time before communicating with anyone. When everyone worked remotely, we had a lot more meetings throughout the day. When those were done, I’d go back to productivity mode. Now that some of us are back at the office, we had to readjust the meetings’ frequency again, but we’re used to it by now. We needed to adapt to many changes lately, but that’s life, and we make the most of it.</p><h4>Did anything change for the better?</h4><p>Yes. Meetings became a lot more structured and organized. We also learned to be even more available for one another. I also loved reuniting with people at the office when the lockdowns ended. We really missed each other. That’s one thing COVID-19 hasn’t changed at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVkqNRDgwrQbResgCTigmA.jpeg" /><figcaption>Three eko devs and their team lead (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><h4>How would you describe your job to a child?</h4><p>Wow. I would probably start with an example of something that works. I showed <a href="https://eko.com/shows/buzzfeed-tasty-eko/">Tasty</a> to my 6-year-old niece. She made all the possible choices over and over again. I would explain that there is a sequence of actions that she can tell the computer to do according to its language. I’d say I spend most of my day writing words that are computer software commands so that it will do what I want it to do. For example, there’s a tool on our platform that lets anyone upload a video then add cool buttons to it to help them tell their story. The commands I wrote make that happen. But then I’d also say I spend most of my time getting angry at the computer for not doing what I want.</p><h4>Tell us about a time when your input made an impact.</h4><p>I have an excellent example. “Offlining” is what we internally call the process of making projects that are played using an active connection to the internet playable offline. I was responsible for making it work, especially for our CEO, who wanted to showcase our projects at events and presentations without depending on an active, stable network connection. It’s not really part of our core business, and no one properly checked that this feature worked because it wasn’t that important in our day-to-day work.</p><p>Projects always had to be “made offline” at the very last moment. It was something only developers knew how to do, and it was an annoying task every single time. I spoke with our CTO and convinced him that we should treat this just like any other product. So, he assigned an “offline” project manager. Now, anyone, not just the developers, can make any project work offline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQPJQr43ZX-gtao0GSlfKA.jpeg" /><figcaption>Maayan’s delicious homemade cake :)</figcaption></figure><h4>What was your most challenging experience as a developer?</h4><p>My most challenging experience as a developer was what I loved working on most — our player’s core.</p><p>I was part of the team responsible for re-writing our old Flash/ActionScript player as a JavaScript player. We have several audio/video playback engines, and my colleague and I had ownership of the iOS engine. It was challenging because I needed to have a deep understanding of HLS, the protocol we used, and its inner workings. Then I got to improve the experience and performance of our iOS app, and that was even more challenging. I had to handle the bytes you were downloading and understand everything that was going on in the browser and the OS.</p><p>I call it the hardest because I also had to test it differently. I could test the previous engine in Safari, but here I needed to test specifically within the context of an iOS app. I had to generate the audio and video streams and deal with things at a very low level, plus the app layer, which made things more complicated. We needed to work with WebSockets, and that’s something I never really did before. I felt like I had an opportunity to understand things on a much deeper level, which was very interesting.</p><h4>What’s your most memorable facepalm moment?</h4><p>It was just a few months after I started working here. I was working on the iOS engine and had a Mac because I could only test on Safari. I put down my coffee, hit the glass, the coffee spilled all over the computer, and it immediately shut down. Back then, Macs were really expensive in Israel.</p><p>Now, if it were my personal work computer, that would’ve been one thing, but I was just borrowing it for testing purposes. I wanted to disappear off the face of the earth. We opened the computer, let the coffee drip, dried it, cleaned it, and put it next to a heater. It started working again! We keep it at the office to this day as a historical artifact. It was a dark moment in my professional life, and it happened before my morning coffee! A terrible way to start the day.</p><h4>What are you passionate about? What do you love doing (besides writing code)?</h4><p>I really like going to see live music. But, since there aren’t any concerts at the moment, I’m currently into binge-watching Netflix. I just finished The Fall with Gillian Anderson; I love her on that show. I’m also an amateur drummer. Eko is where I got the push to start learning to play the drums.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S5YHqhTeI8ZqzGyh-en0wg.jpeg" /><figcaption>Drummers. Because even guitarists need heroes. (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p>Thanks, Maayan! Now get back to work, but try not to make any more historical artifacts. 😜</p><p>…</p><p>Are you ready to join Maayan and our incredible team? Send us your resume <a href="https://eko.engineering/">here</a>.</p><p>Also, check out more of our fellow eko Engineering team members on Developer Spotlight with <a href="https://medium.com/ekoengineering/developer-spotlight-louai-ghalia-1abd30718dda">Louai Ghalia</a> and <a href="https://medium.com/ekoengineering/developer-spotlight-diana-gavriel-2b112ff382d2">Diana Gabriel</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*myFrRd_JmlyFsqJ6QbXIuw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10dcf3db0049" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/developer-spotlight-maayan-arbiv-10dcf3db0049">Developer Spotlight: Maayan Arbiv</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Sonorous.js: Harmonizing Web Audio]]></title>
            <link>https://medium.com/ekoengineering/introducing-sonorous-js-harmonizing-web-audio-7539cf4a68d8?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/7539cf4a68d8</guid>
            <category><![CDATA[webaudio]]></category>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Mon, 28 Dec 2020 13:16:15 GMT</pubDate>
            <atom:updated>2020-12-28T20:26:24.191Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vjWXmIj_F3Z2eYz6r-Gc1Q.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Web Audio is admittedly very powerful — you can <a href="http://because-recollection.com/">craft an interactive musical journey</a>, <a href="https://www.hashima-island.co.uk/">influence the ambiance</a>, or <a href="https://www.google.com/doodles/clara-rockmores-105th-birthday">recreate an instrument built in the 1920s</a>. Web audio can also be a huge headache.</p><p>For starters, the API is low level and complex. For the simple background music or sound effect, web audio can feel like trying to take a sip of water out of a firehose. (For the record, it should stay that way — to build complex audio experiences, you need something that offers a lot of control.) While there are libraries out there that offer abstractions over web audio, we’ve found them old and outdated. A coworker of mine once said, “Whenever an audio plugin related bug is discovered, instead of quickly fixing it and moving on, we need to spend a whole day debugging internal implementation [of our 3rd party library].”</p><p>I’m here to say that there’s a new way forward. Over the last six months, I’ve been working on Sonorous- a new open source audio library. Sonorous is easy to use, clear to follow, and built with today’s standards in mind.</p><p>Sonorous abstracts the complexity of web audio.</p><p>Just to start playing a sound, web audio requires several set up steps.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ee2617c5ed998d6337def8dc944626e/href">https://medium.com/media/2ee2617c5ed998d6337def8dc944626e/href</a></iframe><p>Sonorous reduces this to 3 lines of code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/343944b47f6b159196e66557a6986caa/href">https://medium.com/media/343944b47f6b159196e66557a6986caa/href</a></iframe><p>Sonorous provides other major advantages other than ease-of-use. If the web audio APIs weren’t tricky enough to understand on their own, there’s the added complexity of each browser implementing the APIs differently. For example, Chrome may allow you to call stop() on a source node before it’s been started, but Safari will throw an error and crash your program. On the other hand, sometimes Safari will fail to initialize an AudioContext but won’t throw an error, and Chrome would. In many browsers now, you are unable to start playing audio without a user interaction first. This is just the tip of the iceberg, but Sonorous handles all of this for you. It’s abstracted by the library, so your code can remain clean and concise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*Yw5P9T9Riw9MawXayUBBUw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Before Sonorous, we used Howler as our audio library for many years. It’s the gold standard and has 50k weekly downloads (according to npm). That being said, there have been a lot of changes to JavaScript/the browser, and I wanted to take advantage of that. For one, web audio is <a href="https://caniuse.com/#search=webaudio">now supported in every modern browser</a>, so Sonorous doesn’t deal with HTML5 audio at all. Web audio is superior in every way; HTML5 audio is pretty old and outdated and doesn’t offer all the flexibility that web audio has. I also wanted to leverage the more modular ES6 class structure to create extensible architecture with clear interfaces. Debugging cross-browser issues could be tricky with Howler, but Sonorous’s architecture was designed to make it easy to pinpoint and fix issues. The current implementation could also easily be expanded in the future as web audio features grow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*7rEvNms7vd26C-usgat07Q.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>While well-defined architecture is thrilling (to me, at least), I’m more excited to talk about Sonorous’s memory management. Audio buffers, once decoded, can be huge. Unfortunately, audio files must be decoded to be played back. And with Howler, as soon as the sound is loaded, the decoded buffer is kept in memory at runtime. <strong>60 seconds</strong> of uncompressed audio translates to <strong>23MB </strong>of memory at runtime. If your program contains just <strong>20 minutes’</strong> worth of audio files, all loaded at once, that’s over <strong>460MB </strong>of memory, which is more than enough to cause an iOS Safari tab to crash instantly. Sonorous gives you the option of storing the encoded buffer or the decoded buffer when the sound loads. If you store the encoded buffer, it would only be decoded when play() is called. Once the play operation finishes, the decoded buffer would be removed again. There might be a lag before playing if the audio file is large, but this solution offers more control over how much memory this library uses when not playing a sound.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/15aa801bf6b683645fd00f868671f679/href">https://medium.com/media/15aa801bf6b683645fd00f868671f679/href</a></iframe><p>At eko, we integrated Sonorous into our audio plugin. Any sound effects or background music played in any of our videos now come through Sonorous. There’s a simple bridge in place for backwards compatibility- any projects that assume the audio plugin uses Howler will receive a wrapped version of Sonorous that matches the Howler API. The audio plugin also adds functionality on top of Sonorous- the ability to link the sound effect playback to video playback (play when the video plays, pause when the video pauses), the ability to load sound effects relative to when they need to be played in the video, etc. Head to <a href="https://eko.com/">eko.com</a> and watch any video to see Sonorous in action!</p><p>Sonorous is an easy to use audio library for the modern age. Whether you’re building a complex game with lots of audio or just adding background music to your website, Sonorous can help you. It hides the complications of working with audio across browsers and is built with the modern browser in mind. If you’re already using Howler, the switch to Sonorous should be pretty painless. Sonorous is just getting started, and I’m excited to share it with you. If you’re as interested in this as I am, feel free to contribute! Sonorous is open source, and we welcome any and all looking to participate in Sonorous going forward.</p><p>If you’re curious to learn more, check out the <a href="https://github.com/EkoLabs/sonorous#sonorous">documentation</a>. And if you’d like to see more examples in action, <a href="https://github.com/EkoLabs/sonorous#examples">check these out</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7539cf4a68d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/introducing-sonorous-js-harmonizing-web-audio-7539cf4a68d8">Introducing Sonorous.js: Harmonizing Web Audio</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Spotlight: Diana Gabriel]]></title>
            <link>https://medium.com/ekoengineering/developer-spotlight-diana-gavriel-2b112ff382d2?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b112ff382d2</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[office-culture]]></category>
            <category><![CDATA[developer-stories]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Thu, 26 Nov 2020 20:22:51 GMT</pubDate>
            <atom:updated>2020-11-26T20:24:53.528Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnZgnD84IZVsu0EQrJkplQ.png" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>We’re back with another article in our Developer Spotlight series, where we highlight different members of our team and offer them an opportunity to share their stories. This time, we sat down to talk with Diana, a master QA engineer who’s been an essential part of development here at eko for over eight years(!!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*932zS0Wmuul15pbewt6oyw.jpeg" /><figcaption>Diana Gabriel (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p>Diana designs and executes test scripts and performs complex manual tests for new features. But most importantly, she’s part of the development process from ideation to going live (and well after), which puts her in the perfect position to see the big picture and make sure everything’s bug-free.</p><p>Let’s get started!</p><p><strong>What’s your role here at Eko? How long have you been at eko? and what do you love most about it?</strong></p><p>I work in QA, and my role is to be constantly alert for bugs, even after testing something a hundred times.</p><p>I’ve been working at eko for more than eight years, and I’ve just realized that I was only 28 years old when I started. Now my 40th birthday is glimpsing at me!</p><p>The thing I love about my job is that even after so many years, I’m still always learning new things. It’s as though I came yesterday. It’s so dynamic, and a lot of things are always happening. There’s no such thing as routine at eko!</p><p><strong>What does your typical workday look like?</strong></p><p>I work from home part-time, and my day usually starts early in the morning until late afternoon. I know my tasks in advance, and I plan my day accordingly. Sometimes that means setting up a meeting on zoom, preparing a test environment, reading specs, or planning tests. I try to get those things out of the way as soon as possible, and that way, I can work smoothly and efficiently on detecting bugs throughout the day.</p><p>I’m not always strict with my hours. Sometimes I find myself drawn to things in the late evening just because I’m curious to investigate some bugs. It’s fun. Working in QA at eko is like solving puzzles; it’s a game that never ends.</p><p><strong>How has your workday changed since the pandemic?</strong></p><p>Since I became a mom, my priorities have changed. But it was important to me not to give up on my job. A year before the pandemic started, I tried working from home to see how it goes. It turned out to be the ideal solution to combine raising my kid and working. So actually, when the pandemic started, it didn’t really change my schedule. I had been preparing for this working environment a year in advance.</p><p>I do miss working at the office, though. The social aspect is essential for my mental energy. But I remind myself that everything is temporary, and the advantage is that my productivity from home is higher than ever. As an added bonus, our eko operations manager sometimes pampers us with surprises delivered to our doorstep, which always raises a smile!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWpecUIF8-UD-uZ4tkhXlw.jpeg" /><figcaption>The good old days, when we could all have lunch together and kids were free to use the force on office dogs. (photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p><strong>How would you describe your job to a child?</strong></p><p>Imagine you ask your dad to make apple muffins with cinnamon. I taste it first to check that he made it well. Then, to my surprise, I find out that dad put in banana instead of apple, salt instead of sugar, and forgot to add any cinnamon! My job is to tell dad to make the muffins better so that you have a yummy muffin :-) Still, no one’s perfect, and he might get the quantity of cinnamon wrong, but hopefully, we can make it as tasty as possible!</p><p><strong>What was your most challenging experience at work?</strong></p><p>I think the most challenging experience was when we completely removed Flash from our creation platform. Flash was tightly integrated with a lot of eko Studio’s core components from its very early days, so untangling it proved a real challenge. Though it wasn’t the first time we said goodbye to Flash in one of our products, it was much more complicated than previous operations. I think it had more QA cycles than any feature I have ever tested. The difficulty wasn’t in the type of tests that I had to do. It was the number of cycles we had, which included many sanity tests. If you work in QA, you know how unforgiving that can be. Thankfully that’s now behind me. RIP Flash!</p><p><strong>What’s your passion? What do you love doing?</strong></p><p>I love reading. I like to linger on words as I read. And read them over and over again if something is beautifully written. Languages and the origin of words, and the connection between words in other languages fascinate me. One day I hope to write my own book (and illustrate it — another of my passions — but that’s another story…;)</p><p><strong>What is similar to QA in other offices, what is different?</strong></p><p>We use some of the same QA methodologies as in other offices, and we have some standards and QA tools used in many other places. But even so, eko is different in many ways. We don’t stick to the rules, and there is much freedom in the way we work. Our emphasis is on moving fast while not compromising on quality. If I choose to test something without a standard test plan and in an unusual way that deviates from what is accepted in the QA community, no one cares as long as the results are satisfying.</p><p>Also, the developers here are close and friendly with the QA team. Unlike other offices I used to work in, they patiently teach me a lot of stuff, and we both want to make the product as refined as possible. It’s a joint effort here. You’re not alone.</p><p><strong>What are the QA challenges?</strong></p><p>Many times we forget to think outside the box. We can lose the big picture, and we might miss trivial or important bugs.</p><p>Sometimes development time comes at the expense of testing time. That ends up forcing us to prioritize our tests and cast aside things that we wanted to test or test things in a superficial manner. It can be really disappointing because, in the end, the quality of our work is measured by the quality of the product.</p><p>Sometimes, we don’t have time to test and examine the features in-depth because we are busy with other tasks on parallel other products. We need to be creative in real-time and improvise quickly to do the best we can.</p><p><strong>What do you think is needed to be a successful QA engineer at eko?</strong></p><p>You need to be open to changes. You need to be mentally flexible, curious, diligent, and agile. You should know how to discern between what is bland what is important, and you shouldn’t be afraid of insisting on things you view as essential to the product’s quality. On top of that, don’t stop learning new things, don’t break from routine tasks, trust your intuition, be nice, be humble, and try to keep a sense of humor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ftoePjnHZBRR1YwWpFiU9g.jpeg" /><figcaption>Diana’s second favorite office</figcaption></figure><p><strong>If you could switch jobs with someone, who would it be and why?</strong></p><p>I’d be a restaurant critic. It’s my dream job… but maybe that’s a side effect of being pregnant and always hungry…</p><p><strong>If you could choose anyone, alive or dead, who would you pick as your mentor and why?</strong></p><p>My grandma was my perfect mentor. She was smart and noble and equally streetwise.</p><p>I was lucky to get to know her. Thanks to her, I learned a lot about taking things in proportion and appreciating what I have.</p><p><strong>What does success mean to you?</strong></p><p>Warning — cliché ahead.</p><p>If I wake up in the morning and am happy for what I have, I have succeeded.</p><p>We are always taught to think big and to look far. Actually, I believe that simple thinking and looking at what’s under your nose can be surprising and take us to unexpected places. I am a fan of minimalism and small details. Maybe that’s why I work in QA :)</p><p><strong>What’s unique to eko that you didn’t see anywhere else?</strong></p><p>Definitely the people at eko. I haven’t yet encountered such a collection of people elsewhere. Each person is a world in their fullness; intriguing and creative people, with a sense of humor, and very smart. They are recruited and picked by hand. Eko is very serious about recruiting. It is not easy to be accepted, but anyone once hired should be proud of themselves.</p><p>Thanks, Diana! Now, can we please get some of these apple-cinnamon muffins you mentioned?</p><p>Want to join our team and work with Diana? Learn about our many open positions <a href="https://eko.engineering/">here</a>!</p><p>And since you made it all the way to the end of this article, you might also enjoy our Developer Spotlight with <a href="https://medium.com/ekoengineering/developer-spotlight-louai-ghalia-1abd30718dda">Louai Ghalia</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-j_ftb3rGHepsY5l3XTog.png" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b112ff382d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/developer-spotlight-diana-gavriel-2b112ff382d2">Developer Spotlight: Diana Gabriel</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bluecadet Blog Takeover Series: Powering the Magic of a Choice-Driven Comedy]]></title>
            <link>https://medium.com/ekoengineering/the-bluecadet-blog-takeover-series-powering-the-magic-of-a-choice-driven-comedy-fd444025fc2d?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd444025fc2d</guid>
            <category><![CDATA[series]]></category>
            <category><![CDATA[interactive]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Tue, 20 Oct 2020 11:36:44 GMT</pubDate>
            <atom:updated>2020-10-20T17:02:48.442Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k24QwD-c0Wb6qGWarurAKw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Hi!</p><p>We’re <a href="https://www.bluecadet.com/">Bluecadet </a>and we’re taking over the eko Engineering blog to talk about <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">our work on Wizard School Dropout</a>.</p><p>Wizard School Dropout is a choice-driven comedy about Andy, a young witch who defies her parents, quits Glimdrang Academy, and has to figure life out in non-magical Los Angeles. But since Glimdrang doesn’t really prepare you for things like getting a job or paying rent, Andy needs viewers’ help navigating work, friendships, spells, and preventing a little bro-pocalypse — all before losing a piece of her soul to her creepy landlord.</p><p>Wizard School Dropout is a collaboration among eko, Walmart, and EffinFunny. The Bluecadet team was tasked with the design, game mechanics, user flow, motion design, and development of the show.</p><p>What do game mechanics and user flow have to do with creating a comedy?</p><p>Wizard School Dropout is not your average TV show. It’s a choice-driven video series on the web. Viewers have to decide Andy’s next moves, help her cast spells by playing mini-games, and collect magical artifacts. How well they do this determines what powers Andy develops, how much money she makes, and the nature of her relationships. Wizard School Dropout is part live-action show, part game, and the users are part viewer, part player.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*kMctkbhIH79ZK7EDCUui1g.gif" /><figcaption>(from the Blue Cadet WSD <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">case study</a>)</figcaption></figure><p>Creating this sort of complex yet immersive entertainment experience was not easy. There’s practically an infinite number of Wizard School Dropout versions one can play through.</p><p>Beyond storylines we also had to tackle some significant technological and logistical challenges to pull everything off.</p><p>This article is a quick overview of the technology. We’ll go in depth into logistics, game design, visual effect rendering and other cool stuff in our next posts, so stay tuned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*KVine65v0JNTlxFWBFMrug.gif" /><figcaption>(from the WSD <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">case study</a>)</figcaption></figure><h3>Is this technology, or is this magic?</h3><p>Wizard School Dropout is a complex web experience. To build the Wizard School Dropout world we had to use a bunch of different tools in tandem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dugW93pSk_Th4ctcJRflrw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>The eko platform is the technological backbone powering the interactive video playback and seamless decision making. Eko gave us the ability to plan out and implement all of the show’s branches; the choices you make, places you go, people you meet — all these different narratives are organized and tracked on the platform. It also stores information and helps track your progress and stats throughout the series. Without eko, we could create all the mini-games we wanted, but the results wouldn’t matter to the story.</p><p>We used <a href="https://reactjs.org/">React </a>for most of the UI, including graphics, animated buttons, and the various progress and energy meters in the show.</p><p>We also used a library called <a href="https://www.pixijs.com/">Pixi</a>, which enabled us to do some more advanced visual effects and graphics. These include the more complex interactions in the show. For example, it is Pixi, combined with some custom shaders we wrote, that allows you to draw a rune and have it sizzle and flare up underneath your finger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*jNflJfvqHf9lFAKaVnqf2A.gif" /><figcaption>(from the WSD <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">case study</a>)</figcaption></figure><p>To sequence out complex animations, we used <a href="https://greensock.com/">GreenSock</a>.</p><p>From a tech point of view, the fact that everything is timeline-based was a big deal. One of our challenges was that both Pixi and GreenSock have their own timelines, but we needed the eko video player to be our ultimate timekeeper. Part of our work was wrapping up Pixi and Greensock to obey eko’s timeline.</p><p>We realized very quickly that we were making a game, and that’s how we needed to approach the work. Building software and games, there’s a particular flow for thinking about logic working and dealing with questions like, do animations pause at the same time you pause the video? Or, what happens to your app state when rewinding to a previous choice moment?</p><p>Really, this was even more unique than a game since it’s fundamentally first a passive and then an active product. We had to think about how these different elements, like game mechanics, could build on each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Os9qfqdIAdvppikNj-oOFA.gif" /><figcaption>(from the WSD <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">case study</a>)</figcaption></figure><p>From the coding standpoint, all the potential choices that a person can make have an effect on what state the code is in and what might happen, which is why one of our biggest challenges was QA and debugging.</p><h3>Testing in progress</h3><p><strong>Testing a layered game experience that built up over the episodes made testing and debugging an interesting task.</strong> Let’s say you want to test one particular animation, you can’t always watch those first 10 minutes until you get to that point. So, how do you test something you just quickly want to iterate on over and over? Similarly, how do you test all the different narrative options?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*--v3owcI7R81m1yOZuPPIQ.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>The hardest bugs were when there was a sequence of decisions, game results, or a bunch of interactions built over many episodes. We might find a bug and then have to trace back the viewer’s actions across five episodes to determine the root cause.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*QNPdq62Z9QHjqLYvzyAfcA.gif" /><figcaption>(from the WSD <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">case study</a>)</figcaption></figure><p>An excellent example is the money meter, which could suddenly revert to zero. Now, this isn’t real life; you can’t suddenly be out of money on episode 5. We had to ask ourselves questions like “Did they work in this episode?”, “Did they not work in this episode?” “What did you play before?” “Where was the money supposed to be at?” Trying to track these down was extremely difficult.</p><p>Our senior developer, Nick, built a Swiss army knife to preview and test features. Those were essentially layers that we added on top of eko’s platform. We used a library called<a href="https://github.com/dataarts/dat.gui"> dat.GUI</a>, a convenient control panel that you hook up to the software and expose its internals. Eventually, it evolved into two layers, one where we could add something to the URL and it would pop up, and the advanced dev-only layer where we kept all our secrets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*yYANOMCrVCGiOlA3kefPtA.gif" /><figcaption>(from the WSD <a href="https://www.bluecadet.com/work/wizard-school-dropout-2/">case study</a>)</figcaption></figure><p>It was great for design tweaking, which can be such a time sink. Our team would just sit down next to each other and tell Nick, “Can you make it more like this?” And he’d be like, “Let me just turn up the dial.”</p><p>It allowed our team to link directly to specific moments in the show and fast forward until right before a decision. But it also gave people a place to fine-tune and adjust the difficulty of a game, the speed or color of an animated part of the UI, sound behavior, and the visual effects on screen.</p><p>Every aspect, from the core logic to game behavior, interaction, and visual effects, was exposed for multiple rounds of fine-tuning thanks to Nick’s tool.</p><h3>Magic moments</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yfyo-Vloh2cSUOCBVutiuQ.jpeg" /></figure><p>Bringing a choice-driven show like Wizard School Dropout to life was no easy task. Still, our team brought all our water, air, earth, and fire elements together to create magical moments, like movers being punched by a table on episode 1 or a grand reveal at the end of episode 12 (we won’t spoil it for you).</p><p>In the meanwhile, you can<a href="https://eko.com/shows/the-choice-is-yours/wizard-school-dropout/"> play Wizard School Dropout here</a> :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fztFgAzhhiV7VbpG58NDPg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd444025fc2d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/the-bluecadet-blog-takeover-series-powering-the-magic-of-a-choice-driven-comedy-fd444025fc2d">The Bluecadet Blog Takeover Series: Powering the Magic of a Choice-Driven Comedy</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we Structured our Engineering Team for Happier, More Productive Devs — Even in Times of Crisis]]></title>
            <link>https://medium.com/ekoengineering/how-we-structured-our-engineering-team-for-happier-more-productive-devs-even-in-times-of-crisis-79ece8b3db92?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/79ece8b3db92</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 14:10:28 GMT</pubDate>
            <atom:updated>2020-08-27T14:10:28.882Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How we Structured our Engineering Team for Happier, More Productive Devs — Even in Times of Crisis</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XFHi3QDk0gUYRWqLtVbmjQ.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>Six months ago, we wrote an article. It was all about how much we love the organizational structure and culture here at eko. We were just about to hit “Publish” when, all of a sudden, COVID-19 happened. From one day to the next, we had to adapt to lockdowns, working from home, and social distancing. Plus, we didn’t think publishing an article about our organizational structure would be relevant, or even appropriate, at the start of a global pandemic. We decided to put the article on ice and spent the next few weeks getting used to “the new reality”.</p><p>We soon learned that good things come to those who wait, as we got to see firsthand how being a flat organization not only helped make our transition smoother but also introduced several opportunities for improvement.</p><p>Fast forward to today, we finally feel like it’s the right time to share some of our insight.</p><p>Long before the pandemic, the way our company was structured affected almost everything we did at work. It enabled us to lead projects from start to finish, become experts in various fields, interact and engage with people from different departments, fully understand WHY we’re developing things, and significantly impact the company’s decision-making process. All of these were key to our team’s happiness and job satisfaction.</p><p>That sense of autonomy combined with collaboration carried on during our months of working together, but apart and from home.</p><blockquote><em>“The structure and processes we adopted throughout the years are an amazing fit to the challenges introduced by COVID-19, allowing us to keep on delivering even though many of us are working from home”. -eko CTO, Yuval Hofshy.</em></blockquote><h4><strong>So, what does “flat organization” mean, anyway?</strong></h4><p>A <a href="https://www.forbes.com/sites/williamcraig/2018/10/23/the-nature-of-leadership-in-a-flat-organization/#7e7812fa5fe1">flat organization</a> has few to no levels of middle management between staff and executives, which means that unlike hierarchical organizations, most middle management and their functions have been eliminated and top management has direct contact with all employees.</p><p>Flat organizations are characterized by less employee supervision and more employee involvement in the decision-making process. They often relinquish things like job titles and seniority, view everyone as equal, and emphasize collaboration.</p><p>To become successful, any startup has to create awesome products, quickly deliver them to customers, and rapidly adapt to market demand changes.</p><p>As a startup company ourselves, we’re constantly trying to push the envelope of choice-driven entertainment in the competitive field of online video. This forces us, the developers, to think on our feet, come up with creative solutions, and execute them immediately.</p><p>For us, a flat organization means we can get things done — fast.</p><p>It also means no one is telling us to “do this” or “do that”. Instead, we come together as a group to solve issues and overcome challenges. It completely changes the company’s dynamics and enables us to fully understand not just the “what” part of our job but also, and more importantly, the “why” — putting us at an excellent position for some high-level decision-making. So, by the time we were working from home, all of us were pretty accustomed to managing ourselves and making our own decisions.</p><blockquote><em>“The freedom to make decisions and operate as you see fit as long as you deliver.” -eko dev, Yariv Fruend.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xpLoqdGHT1iGn49g55aJuQ.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4>A flat structure lets you focus on what’s important</h4><p>When teams are built based on expertise and areas of responsibility, team members are focused on eliminating the team’s task backlog — regardless of the impact these tasks have on the business’ overall success. Getting people to work on what’s really important becomes more complicated. For example, an “iOS team” will only work on iOS-related tasks. There are always tasks waiting in the iOS backlog, even if the company’s most pressing tasks have nothing to do with iOS.</p><p>A flat organization improves the business’ response time to market changes and customer demands. But more importantly, it enables us to smoothly transition from one project to another while leveraging different skills and talents. It allows us to pursue different passions and discover more areas where we excel.</p><p>This approach enabled us to quickly kick off new and exciting projects, like <a href="http://www.campbywalmart.com/">Camp by Walmart</a>, an ambitious online summer camp with 250 interactive experiences, which we helped bring from idea to production in fifteen weeks flat.</p><blockquote><em>“We always feel connected to the bigger picture, each team member gains knowledge vertically and holistically and doesn’t just continue with the skills they had.” -eko dev, Maayan Arbiv.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pMsyFmJ79dgj0gXRZXi77w.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4><strong>Flat organizations reduce overhead</strong></h4><p>Multiple layers of management create a company with many employees who work at overseeing other employees. Once you eliminate these layers, the organization enjoys fewer meetings, shorter approval processes, and a <a href="https://simplicable.com/new/flat-organization">boosted budget</a>.</p><blockquote><em>“There is no fear to speak your mind or ‘what will the boss say?’, this leads to everyone being able to make a difference.” -eko PM, Roe Shani.</em></blockquote><p>Integrating a flat structure has improved eko’s decision-making, efficiency, and performance by empowering us to make decisions and take full responsibility for our work. So, even though we no longer enjoyed each other’s company during the workday, we always knew what we were responsible for. The only change we had to make, in that regard, was the medium we communicated on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elzZhTj-Qj0gZVDTcIY4og.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4>A flat structure creates organization-wide teamwork</h4><p>When people are divided into teams, they collaborate within their group but not so much with other people. It raises issues such as who’s better? Who’s working on more important things? Who gets to impact decisions? And let’s face it, no one likes this kind of <a href="https://www.emerald.com/insight/content/doi/10.1108/RIBS-09-2017-0073/full/html">office politics</a>.</p><p>Flat organizations enjoy better collaboration between all employees. Their leaders communicate more freely with staff instead of just passing on directions, and employees find more meaning in contributing to different projects.</p><blockquote><em>“There’s no bullshit bureaucracy here. You have the complete freedom and full ownership to make decisions. Your voice isn’t just heard, it’s listened to.”-eko dev, Asaf Menahem.</em></blockquote><p>At eko, we have ad-hoc teams created to develop specific features or fulfill cross-product business requirements. Our teams often include developers with frontend, backend, devops, and other expertise.</p><p>These projects create cross-pollination of knowledge between developers with different expertise and prevent situations where one developer is the only domain expert for a task.</p><blockquote><em>“You can contribute in the areas that interest you the most, rather than being shoehorned into a specific team or narrow specialty, and that makes us all more versatile.” -eko dev, Roy Taragan.</em></blockquote><p>For some of us, the situation made it easier to collaborate with people from our New York office. Before quarantine, we had to come to the office and work during “normal” work hours, with the time difference between Tel Aviv and New York making it more challenging to work together. During quarantine, a few of us found it more comfortable to be with our kids during the day and shift work to the evenings — exactly during New York office hours.</p><blockquote><em>“At eko, since you don’t get projects assigned to you from the top, you get to choose, I chose to join projects which require tight collaboration with the NY team, enabling me to spend time with the kids during the day, and work on NY clock.” -eko dev, David Silberstein.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kuhPQlYiAHG6JvTIHZ1Zmg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><h4>Flat organizations encourage extreme ownership</h4><p>An <a href="https://www.inc.com/pierre-yves-hittelet/navy-seal-leadership-lessons.html">extreme ownership model</a> is one where people take full responsibility for their work and its outcomes. It’s about learning lessons, not placing blame. It pushes companies to be proactive, dynamic, and problem-solving, which is what you want to be during a global crisis.</p><p>Ownership is tightly coupled with decision making. Excess layers of management contradict extreme ownership.</p><p>When managers become messengers and decisions are made over multiple meetings by people with different goals and motivations, information gets lost, distorted or misinterpreted along the way — causing great ideas and initiatives to get rejected simply because the people behind them couldn’t pitch them to leadership themselves. This process becomes even more tedious when you can’t get everybody under the same roof to communicate.</p><p>Since we truly understand why we’re doing whatever it is that we’re doing instead of just following other people’s orders, we have an actual stake in the project’s success, we care more about the results, and can accomplish things far more quickly.</p><blockquote><em>“The flat organization forces you, in a good way, to take responsibility for everything you do.” -eko dev, Louai Ghalia.</em></blockquote><p>eko developers lead tasks from ideation to production. When one of us leads a project, it’s our responsibility to connect with all the stakeholders directly; we pitch it to management, write specs with the product managers, build the architecture with other developers, come up with test plans with QA, work closely with the devops, creative, design, data, sales and marketing teams, and support the project on an ongoing basis after it goes live. We’re focused only on results and never have to sit and wait for the approval of a manager.</p><blockquote><em>“Here it’s more than writing code all day. You have the ability to influence, to build something from scratch, to lead, and to constantly gain more knowledge.” -eko dev, Ran Gliksberg.</em></blockquote><h4><strong>So, what’s the catch?</strong></h4><p>If flat structures are so great, how come so many engineering teams are still hierarchical?</p><p>The truth is that flat organizations are not for everyone. Large organizations will have a serious problem maintaining this kind of structure unless they divide into smaller, more manageable units. Some will apply models that support agility, such as<a href="https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/"> the <em>Spotify Tribe Engineering</em> model</a>. Some will end up with deep hierarchies. None can be flat.</p><p>Plus, for a flat organization to work, you need to have the right people with the right mindset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f0H3ANXuUAWUecy7W88m9w.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>You need the entire team to WANT to be proactive in contributing to ideas and tasks, understand WHY they’re doing what they’re doing and take initiative rather than check things off their to-do list one by one. While flat organizations offer greater freedom, they require more responsibility as a price.</p><p>This type of work environment is a dream come true for people who love the idea of being involved with multiple projects while having the freedom to make their own decisions, but a total nightmare for those who want to focus on a single domain or feel less comfortable without reporting to a direct manager.</p><blockquote><em>“Having the right people with the right mindset, and keeping the organization as flat as possible, forces a management style that focuses on empowerment. It’s hard, but it pays off. “-eko CTO, Yuval Hofshy.</em></blockquote><p><strong>Bringing it all together</strong></p><p>When a flat organizational structure meets the right leadership and staff, people find meaning and passion in their work, even when times get hard. They’re motivated to lead projects and see them to fruition, rely on their peers for assistance, and take full responsibility for the success of the company as well as their own and do their best to thrive.</p><p>A flat organizational structure enables us to be dynamic, innovate, and quickly react to business needs.</p><p>We really hope things will get back to normal sooner rather than later, but until then — we’ll continue to stay united (separately, in our own homes) in our goal to be the best dev team possible and to support one another through life’s unpredictable challenges.</p><p>Like what you’re reading?</p><p>Feel free to give us a clap (it’s okay, we’ve sanitized the hands icon) or, better yet, <a href="https://eko.engineering/">send us your resume</a>!</p><p>We’re always looking for awesome devs to join our team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79ece8b3db92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/how-we-structured-our-engineering-team-for-happier-more-productive-devs-even-in-times-of-crisis-79ece8b3db92">How we Structured our Engineering Team for Happier, More Productive Devs — Even in Times of Crisis</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Spotlight: Louai Ghalia]]></title>
            <link>https://medium.com/ekoengineering/developer-spotlight-louai-ghalia-1abd30718dda?source=rss-171dd0aa49dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1abd30718dda</guid>
            <category><![CDATA[office-culture]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[data-developer]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[The eko Devs]]></dc:creator>
            <pubDate>Wed, 13 May 2020 16:27:28 GMT</pubDate>
            <atom:updated>2020-05-17T14:53:15.817Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7E7eKP2Y2iTNBp32aHgtw.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><p>We’re very excited to launch our new blog series, ‘Developer Spotlight’, completely dedicated to us — the eko Engineering team.</p><p>These spotlights are meant to give you a real and unfiltered look behind the scenes of working here at eko by interviewing different members of our team and letting them tell their stories in their own words.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*H5zCcksCxC984CS1z2TMGw.jpeg" /><figcaption>The Meticulous Louai Ghalia (Photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p>We’re kicking things off with one of our more recent hires, Louai Ghalia. Louai is a very methodical guy, which is why he only reached out to us after reviewing all of the companies on Calcalist’s list of <a href="https://newmedia.calcalist.co.il/calcalist-50-startups/index.html">Israel’s 50 most promising startups</a> and choosing the one he liked best. We obviously like him too since it’s been almost a year and he keeps showing up to work :)⠀⠀⠀⠀⠀⠀</p><p><strong>How would you describe your job to a child?</strong></p><p>I’d tell them “I build cool technology that lets you watch those online videos you like and adds cool buttons that let you control where the story goes.”</p><p><strong>How would you describe it to an adult?</strong></p><p>I’m an eko developer and my role here is basically to work on everything. Thanks to the work culture here, it’s really hard to say that someone is responsible for just their part.</p><p>I get to work on all kinds of projects, and always get to choose what I want to work on next. For example, during my weekly meeting with our CTO, Yuval Hofshy, he may present me with 3 different projects and ask me what I think will be most interesting and cool for me to work on. Sometimes I pick the ones in fields I know I’m very good at and sometimes I pick projects in unfamiliar territories. That’s how I know I really work on everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFstxRFTuZMpQ62lC6yzuw.jpeg" /><figcaption>Louai explaining something important…we think (Photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p><strong>What do you love most about your job?</strong></p><p>I especially love working with our data team and the fact that I got to travel to our New York office to get to know them, understand their needs and offer creative solutions. The last time I was there, right before the Corona outbreak, I wrote a bridge that enabled the team to perform apples-to-apples comparisons on events between two data sources.</p><p>I also really love working at a startup that has real potential. The fact that we’re offering the market a whole new medium creates a real business opportunity for us. Since there were failed startups in my background, I wanted to work for a company that not only has a strong product but also a strong business.</p><p>But the thing I love most about working here is the atmosphere. You never feel like you’re working for a corporation. We have an excellent vibe and a sense of family. This company was founded by a group of friends and they managed to keep it that way. We’re all just friends who enjoy working together.</p><p><strong>What does your typical workday look like?</strong></p><p>Before the Corona outbreak, I always hoped to find Ran’s dog Ziggy waiting for me at the office in the mornings. I usually went straight to the kitchen and talked to people. Then, I kicked off my workday by making a list of tasks I wanted to get done. I usually did the tasks that involve talking to other people first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TpmDV2R5q-RXRAv1hkgUfQ.jpeg" /><figcaption>Ziggy waiting patiently for Louai to come to work (Photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p>Then, a few hours of work until lunch. Lunch is very important — you usually saw people going from room to room asking “what are you having?”. We normally brought take out and everyone ate together in the kitchen. The company is growing and when we get back to the office, we’ll need to add more tables, but I hope we can keep our family-like atmosphere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWxwLIKgdMFowRFGS4D_4g.jpeg" /><figcaption>Lunch at eko, pre-social distancing (Photo by <a href="http://dafnatalmon.com/portfolio">Dafna Talmon</a>)</figcaption></figure><p>After lunch, I go back to my office - the music room, but we like to call it “the poster room”. Here, everyone can connect to Spotify and play whatever they want — no restrictions. I’m currently working from home but I really hope we return to normal soon.</p><p><strong>Tell us about a time when your input made an impact. For example, changed product development or a process in the company.</strong></p><p>That happens all the time. The last time was just two hours ago. I want to change our database access management, how we manage users’ access to our general database. So I just went to our CTO, Hofshy, and told him I don’t like how it’s currently being managed. He told me to go for it, which means that our data security will be getting an upgrade in the next two weeks.</p><p>I’ll be redefining permissions for all our databases and collections. For example, a user can have broader access privileges in development environments, but more restricted access in production environments. So if they want to change something, they’ll get minimal, time restricted access.</p><p><strong>What was your most challenging experience as a developer?</strong></p><p>The most challenging experience I’ve had as a developer was working on a project that didn’t challenge me enough. When the work isn’t challenging, you feel like you’re missing out on opportunities to learn. I was worried I’d be stuck in that place for twenty years, but I was scared to walk away from work and a steady paycheck.</p><p>At some point, I was working for a big corporate, it felt like the people there were robots doing the same thing over and over again under close supervision from management.</p><p>Here at eko, my greatest challenge was web development, since I come from a backend and mobile background. I loved the challenge of learning new things. At certain times I didn’t even know if what I was doing was even related or right. But I could always count on Asaf, a fellow eko dev who mentored me when I first got here, for excellent advice. He really helped me see the full picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NkJgKWR781IhggRusN4PBw.jpeg" /><figcaption>Louai working his interactive ad magic at the Super Bowl control room</figcaption></figure><p><strong>What are you passionate about? What do you love doing (besides writing code)?</strong></p><p>I’m passionate about knowledge. I think the best thing about the human experience is knowledge. I think it’s very cool, both historically and looking forward at our potential to know even more. I want to learn as much as possible.</p><p>I’m interested in history, especially of the middle-east. As someone from the Arab community, I want to understand more about the conflict. As a result, I’m also interested in politics, social justice and human rights. I sometimes think about becoming a politician after my career in high-tech.</p><p>Astronomy is also a very interesting field, although more difficult.</p><p>I try to stay curious about everything for the sake of knowing more. I read this week that you should write 50 questions you don’t know the answer to and try to find their common thread to locate your next field of interest.</p><p><strong>If you could choose anyone, alive or dead, who would you pick as your mentor and why?</strong></p><p>Well, that means I can have any historical figure, and there are so many people I’d like to have as mentors. Plato, Socrates, Martin Luther King Jr., Leonardo da Vinci. But if I had to pick just one, it would have to be da Vinci. But I could change my mind in 30 minutes.</p><p><strong>What are your future plans?</strong></p><p>I want to be an entrepreneur, a musician, and a politician. There are so many career and life choices a person can make, but you can’t fit them all into one human life.</p><p>Thanks Louai! You definitely have our vote. But before you go running off for office please consider the fact that you can roll back commits but you can’t do the same with commitments!</p><p>Want to see for yourself what it’s like to work with Louai and our kickass dev team? Send us your resume <a href="https://eko.engineering/#careers">here</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2cUQJqkW5H2b9M7Or_SOQg.jpeg" /><figcaption>(Illustration by <a href="https://www.instagram.com/itairaveh/">Itai Raveh</a>)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1abd30718dda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ekoengineering/developer-spotlight-louai-ghalia-1abd30718dda">Developer Spotlight: Louai Ghalia</a> was originally published in <a href="https://medium.com/ekoengineering">ekoEngineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>