<?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 Welcome to our Yassir Engineering Blog on Medium]]></title>
        <description><![CDATA[Stories by Welcome to our Yassir Engineering Blog on Medium]]></description>
        <link>https://medium.com/@Yassirtech?source=rss-fd6cbe068730------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Qop0UtGdhCfy39g5SNUjqg.png</url>
            <title>Stories by Welcome to our Yassir Engineering Blog on Medium</title>
            <link>https://medium.com/@Yassirtech?source=rss-fd6cbe068730------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:21:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Yassirtech/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[It’s not just translation! The challenges of multilingual UX Writing]]></title>
            <link>https://medium.com/@Yassirtech/its-not-just-translation-the-challenges-of-multilingual-ux-writing-b85a7bfee4e6?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/b85a7bfee4e6</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[multilingualism]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[ux-writing-challenge]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Wed, 11 Feb 2026 10:22:51 GMT</pubDate>
            <atom:updated>2026-02-11T10:22:51.208Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="It’s not just translation! The challenges of multilingual UX Writing" src="https://cdn-images-1.medium.com/max/1024/1*l91CMSSUOIKrUtdRKVQJKA.png" /></figure><h3>It all started with a Slack message</h3><p>It was a normal, busy day at Yassir. I prepared my coffee and was focusing on writing copy for a new flow, when a Slack message suddenly popped up:</p><p><em>“Hey! Can you check here why the French word is breaking the button?”</em></p><p>A screenshot followed. The French word <strong><em>“Remboursement”</em></strong> was spilling out of its container like a loose thread. At the same time, the English equivalent “Refund” sat perfectly, and the Arabic one, usually the trickiest of all three languages, looked just fine as well.</p><p>Another screenshot arrived moments later. Same word, same position, but smaller. An attempted fix that somehow made it worse.</p><p>It’s just one word! That’s not a big deal! You might think!</p><p>Yes. But it was enough to remind me that multilingual UX writing isn’t about swapping text. It’s about meaning, tone, and shaping words to fit the space they live in.</p><figure><img alt="Challenges of UXW in diffrent languages" src="https://cdn-images-1.medium.com/max/1024/1*ytQjH2UlTZvpDkLsmCF_wg.png" /></figure><h3>The Invisible Work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b4xIvXWaknFvaRcLfctMiA.png" /></figure><p>That moment wasn’t about fixing a label. It was a reminder of something we often overlook: working in three languages means constantly negotiating meaning, space, and language-specific constraints.</p><p>We tend to assume that an experience designed in English will naturally work in French and Arabic. But French expands. Arabic flows right-to-left. And sometimes, a word like <strong>Remboursement </strong>simply refuses to cooperate.</p><p>That little incident became a quiet reminder: words and design don’t exist separately. They move together, especially in products that ship in multiple languages.</p><h3>It takes a team</h3><p>Stepping into a leadership role made one thing very clear to me: UX writing is never solo work.</p><p>Every feature, flow, and microcopy is shaped through collaboration with designers, researchers, and product managers. We debate tone. We negotiate character limits. We wrestle with right‑to‑left layouts. We question whether a French sentence feels too cold when mirrored in Arabic.</p><p>Day after day, the work proves the same point: this isn’t translation. It’s localization, shaping ideas so they make sense within the nuances of each language. And honestly? That complexity is what makes it exciting.</p><h3>The challenges are real!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NiyhDdilWsbWRbI89t61fA.png" /></figure><p>Below are some of the recurring challenges my team and I face as UX writers working in three languages at Yassir. They’re not edge cases or major incidents; just everyday realities that quietly shape how we design, write, and collaborate.</p><h3>1- Space is not neutral</h3><p>Words behave differently across languages. The “<strong>Remboursement” </strong>button was a perfect example.</p><p>French tends to expand: one English word might turn into three in French, or a full sentence in Arabic! Add right‑to‑left directionality, and suddenly space becomes a UX constraint, not a design afterthought.</p><p>English layouts don’t automatically survive translation. They require early awareness of language specifications and close collaboration between designers and writers from the start.</p><p><strong>Key takeaway: Space is a content decision. Designing for multilingual products means designing with language in mind early, not after handoff.</strong></p><h3>2- Tone doesn’t translate</h3><p>While we aim for a cohesive brand voice, this becomes a challenge when our product speaks multiple languages across diverse cultures. What feels “Friendly” in English can often land as “too casual” in French. A polite phrase in French might feel unnaturally stiff in Arabic.</p><p>During our work as writers, we learned that literal translation is the enemy of nuance. Because a single phrase can shift from “acceptable” to “offensive” across borders.</p><p>That’s why we prioritize localization over simple word-swapping, which requires a lot of collaboration and constant debate with designers, product managers, and even among ourselves as writers.</p><p><strong>Key takeaway: Multilingual UX writing isn’t a literal translation, but more like crafting the user’s emotional experience in their own tongue.</strong></p><h3>3- Process debt</h3><p>Like many growing teams, copy doesn’t always arrive early enough.</p><p>Sometimes it comes in after the designs are finished, or even after a feature has shipped, which makes it feel like a last-minute addition rather than a core part of the process. Suddenly, we’re juggling multiple projects under tight deadlines, trying to survive a growing backlog of Jira tickets and endless lists of mismatched keys.</p><p>These misalignments add up quickly. They’re frustrating, but also instructive. They’ve taught us how to anticipate friction and advocate for copy to be part of the process much earlier.</p><p><strong>Key takeaway: Late copy is expensive. Involving writers early reduces rework and protects experience quality.</strong></p><h3>4- Emotional labor</h3><p>Another recurring challenge is seeing copy change in production without the writers’ input.</p><p>Even after alignment on tone and wording, we sometimes discover a different version live in the product. With many teams moving fast, changes get lost, or last‑minute requests never loop back to writers.</p><p>Those moments are draining. They can even make you question your impact.</p><p>But over time, we’ve realized these frustrations are actually a signal. Reminders showing us how important it is to make our work “stick” and to position ourselves as essential parts of the UX journey. It’s not that we’re against making changes; we just want to solidify a culture of collaboration throughout the entire product life cycle. It’s about advocating for clarity and ensuring we stay aligned with the brand’s tone of voice from start to finish.</p><p><strong>Key takeaway:</strong> Emotional labor often points to process gaps. Fixing them strengthens trust and collaboration.</p><h3>Case Studies: when language meets design</h3><p>To give you a better idea of what this looks like in practice, here are two moments where we had to move beyond simple translation to solve a real user problem.</p><h3>1. The “Remboursement” ripple effect</h3><figure><img alt="Before and After copy samples" src="https://cdn-images-1.medium.com/max/1024/1*XI8zlXn4asZQP1JOOdzeoA.png" /></figure><p>This is the button that first caught our attention in that Slack message earlier.</p><p>The French word Remboursement overflowed its container, while English and Arabic worked perfectly.</p><p>What started as a spacing issue turned into a deeper discussion: shorten the word? Truncate it? Adjust the layout? Or Rethink the label entirely?</p><p>There was no single right answer. But talking it through helped us balance clarity, usability, and space, a reminder that every character interacts with the interface and user expectations.</p><p>In the end, the solution was a mix of layout adjustments and word choice. We went with the infinitive verb <strong>“Rembourser”</strong> and slightly increased the button size to resolve the issue.</p><h3>2. The “Got it!” challenge</h3><figure><img alt="Examples of multilingual UXW" src="https://cdn-images-1.medium.com/max/1024/1*83qqn5KKFa6KkHt48AFlwQ.png" /></figure><p>We often debate how to keep Yassir’s voice local, helpful, and bold, consistent, while allowing the tone to flex. Context is everything.</p><p>Take a simple confirmation message.</p><p>In English,<strong> “Got it!”</strong> feels casual and efficient.</p><p>In French: A literal translation feels abrupt, so we polish it for a better flow. Instead of one word “Compris” we use a full sentence: “J’ai compris !” (I understand).</p><p>In Arabic: A direct translation like Fahimt (فهمت) can come across as blunt or even dismissive. By using Hasanan (حسنًا), meaning “Okay,” we keep the voice consistent while respecting local social norms.</p><p>This isn’t about right vs. wrong. It’s about balancing brand consistency with cultural relevance, and it’s these moments that spark the liveliest debates in our team. Every word carries a weight of perception.</p><h3>What we’re learning</h3><p>We’re still figuring out what works best. Early copy audits. Tone alignment sessions. Getting writers involved sooner. Clarifying Jira briefs.</p><p>These are experiments, not magic bullets. Each step teaches us something new. Helps our words as well as our intent travel more faithfully across languages.</p><p><strong>Learning as we go is part of the job. And that’s okay.</strong></p><p>Along the way, a few things have become clear:</p><ul><li>Multilingual UX isn’t translation; it’s language, culture, and psychology combined</li><li>Copy shapes experience from the very beginning.</li><li>Late‑stage edits cost more than early collaboration.</li><li>Writers aren’t QA buffers — they’re part of the product.</li><li>Tone matters as much as meaning, and adapting it locally is essential.</li></ul><h3>Final words</h3><figure><img alt="Translation vs UXW" src="https://cdn-images-1.medium.com/max/1024/1*bT6LBG2kgsVGHvPuuKIjfg.png" /></figure><p>At the end of the day, I love this work. The quiet negotiation between words, languages, and cultural expectations. The small victories when tone lands just right.</p><p>Writing for three languages isn’t easy. We’re still learning. But it matters. Thoughtful copy shows users that their experience, no matter the language, is valued.</p><p>And for our team, navigating this complexity together has made us not just better writers, but better collaborators, communicators, and problem-solvers.</p><p><strong>About The Author</strong></p><p>Dalal Guesseri, UXW Lead</p><p><a href="https://yassir.com/"><strong>Learn more about Yassir</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b85a7bfee4e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[@Preview the Compose Way]]></title>
            <link>https://medium.com/@Yassirtech/preview-the-compose-way-3123aace6aef?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/3123aace6aef</guid>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Mon, 03 Mar 2025 09:13:04 GMT</pubDate>
            <atom:updated>2025-03-06T11:18:19.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lk8ZSWkK_Abh7zdg.jpg" /></figure><p><strong><em>@Preview</em></strong> in Jetpack Compose is a developer’s secret weapon that is generally available now, but are you truly unlocking its full potential? Most developers barely scratch the surface, using less than 10% of what <strong><em>@Preview</em></strong> can do. Let’s see how you can use more of it!</p><p><strong>TL;DR:</strong> Compose has advanced Preview features at our fingertips that can help spot UI problems before shipping the app to the world.</p><p>For those who are not yet familiar with Jetpack Compose, <strong><em>@Preview</em></strong> is a DSL command that informs the compiler that the following part is only going to be rendered on the Android Studio design view panel and won’t be shipped as part of the compiled APK or AAB.</p><p>Let’s first review the benefits of <strong><em>@Preview</em></strong></p><ul><li>Preview composables in design view, with live updates as you edit, as mentioned above.</li><li>Specify dimensions for your preview using the widthDp and heightDp attributes.</li></ul><pre>@Preview(widthDp = 50, heightDp = 50)</pre><ul><li>Test <a href="https://m3.material.io/styles/color/dynamic-color/overview">dynamic colors</a> using the <strong>wallpaper</strong> attribute.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0gaQKJdXUc3OwaGbTOcQQ.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/preview-devicespec-spec-list.png">https://developer.android.com/static/develop/ui/compose/images/preview-devicespec-spec-list.png</a></figcaption></figure><ul><li>Preview famous device models or resolutions using the <strong>device</strong> attribute.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*QFWMVgOiJKnnY7ZyNKjidQ.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/preview-devicespec-spec-list.png">https://developer.android.com/static/develop/ui/compose/images/preview-devicespec-spec-list.png</a></figcaption></figure><ul><li>Test different locales using the <strong>locale</strong> parameter.</li></ul><pre>@Preview(locale = “fr-rFR”)</pre><ul><li>Change background colors using the <strong>backgroundColor</strong> attribute.</li></ul><pre>@Preview(showBackground = true, backgroundColor = 0xFF00FF00)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/195/1*OXWvuy5R9zQnCvJ3ms3R-w.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling-background-preview.png">https://developer.android.com/static/develop/ui/compose/images/tooling-background-preview.png</a></figcaption></figure><ul><li>Display the status and action bars using the <strong>showSystemUi</strong> parameter.</li></ul><pre> @Preview(showSystemUi = true) </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*onB_Wi7UbzhMTPq_kcqPwQ.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling-decorated-preview.png">https://developer.android.com/static/develop/ui/compose/images/tooling-decorated-preview.png</a></figcaption></figure><ul><li>Access code to run only inside <strong><em>@Preview</em></strong> by adding “<em>LocalInspectionMode.current</em>” to the Compose function.</li></ul><pre>@Composable<br>fun GreetingScreen(name: String) {<br>    if (LocalInspectionMode.current) {<br>        // Show this text in a preview window:<br>        Text(&quot;Hello preview user!&quot;)<br>    } else {<br>        // Show this text in the app:<br>        Text(&quot;Hello $name!&quot;)<br>    }<br>}</pre><ul><li>Test gestures directly from the design panel.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M34IN2wiT91d3RWlvPT0LQ.gif" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling-interactive-preview-demo.gif">https://developer.android.com/static/develop/ui/compose/images/tooling-interactive-preview-demo.gif</a></figcaption></figure><ul><li>Run certain composable previews on a real device or emulator.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TBjXLA2v-wpaUxEy5_fVLg.gif" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling-deploy-preview-demo.gif">https://developer.android.com/static/develop/ui/compose/images/tooling-deploy-preview-demo.gif</a></figcaption></figure><ul><li>Create an image from a <strong><em>@Preview</em></strong> by right-clicking on its design panel rendered preview.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*QnkStW1ZE0Bp6Q1DY5sFPg.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling-copy-render.png">https://developer.android.com/static/develop/ui/compose/images/tooling-copy-render.png</a></figcaption></figure><h3>Powerful features you probably never heard about</h3><p>You might know some or most of the previous dozen <strong><em>@Preview</em></strong> benefits and capabilities, but I’m almost positive the information below is under the radar.</p><h3>Multipreview templates</h3><p>The idea of Kotlin is similar to Compose: to decrease the code needed to implement certain functionalities.</p><p>The Android and Jetbrains team in “androidx.compose.ui:ui-tooling-preview 1.6.0-alpha01+” introduced Multipreview API templates (<strong>@PreviewScreenSizes</strong>, <strong>@PreviewFontScales</strong>, <strong>@PreviewLightDark</strong>, and <strong>@PreviewDynamicColors)</strong>, so that, with one single annotation, you can preview your Compose UI in common scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*am_VoFR3zpW4ZCJ9pez1wQ.png" /><figcaption><a href="https://developer.android.com/static/studio/images/design/multipreview-template.png">https://developer.android.com/static/studio/images/design/multipreview-template.png</a></figcaption></figure><p>While Multipreview templates are a highlight, there’s even more to explore. The most powerful feature is that you can create your own <strong><em>Multipreview templates. </em></strong>With just a few lines of code, you can eliminate repetitive configurations and apply consistent preview parameters across your entire project</p><h3><strong>Custom Multipreview annotations</strong></h3><p>Just imagine that instead of repeating your own <strong><em>@Preview</em></strong> annotations and selections for localization or Dark/Light modes previews every time, you can just write it once and use it everywhere.</p><pre>@Preview(<br>    name = &quot;small font&quot;,<br>    group = &quot;font scales&quot;,<br>    fontScale = 0.5f<br>)<br>@Preview(<br>    name = &quot;large font&quot;,<br>    group = &quot;font scales&quot;,<br>    fontScale = 1.5f<br>)<br>annotation class FontScalePreviews</pre><pre>@FontScalePreviews<br>@Composable<br>fun HelloWorldPreview() {<br>    Text(&quot;Hello World&quot;)<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*_cfKVvvIhP7Ms9ZJdPQ1MQ.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling/preview-multipreview-1.png">https://developer.android.com/static/develop/ui/compose/images/tooling/preview-multipreview-1.png</a></figcaption></figure><p>Code Sample: ​​</p><pre>@Preview(<br>    name = &quot;Spanish&quot;,<br>    group = &quot;locale&quot;,<br>    locale = &quot;es&quot;<br>)<br>@FontScalePreviews<br>annotation class CombinedPreviews<br><br>@CombinedPreviews<br>@Composable<br>fun HelloWorldPreview2() {<br>    MaterialTheme { Surface { Text(stringResource(R.string.hello_world)) } }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*ldIbfrwbwFZo8PJNDXsWGA.png" /><figcaption><a href="https://developer.android.com/static/develop/ui/compose/images/tooling/preview-multipreview-2.png">https://developer.android.com/static/develop/ui/compose/images/tooling/preview-multipreview-2.png</a></figcaption></figure><p>Now, imagine that you need to add a new preview to all your <strong><em>@Preview</em></strong> in the whole application because you added a new language and want to test or modify an already existing one in the whole application. You won’t need to visit and search-replace all. All you need to do is visit your custom multi-preview annotations class and update it. Voilà, all previews have been updated!</p><p>To conclude, <strong><em>@Preview</em></strong> is more than a convenience — it’s a powerhouse of UI testing and optimization. Explore these features in your next project and share your experience. What’s your favorite @Preview feature? Let us know in the comments!</p><p><strong><em>Shady Selim</em></strong></p><p><strong><em>Staff Android Engineer</em></strong></p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p><a href="http://yassir.com/"><strong>Learn more about Yassir</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3123aace6aef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 4 Software Engineering Trends to Watch in 2025]]></title>
            <link>https://medium.com/@Yassirtech/top-4-software-engineering-trends-to-watch-in-2025-acabad966d22?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/acabad966d22</guid>
            <category><![CDATA[software-trends]]></category>
            <category><![CDATA[yassir]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Wed, 18 Sep 2024 07:50:41 GMT</pubDate>
            <atom:updated>2024-09-18T07:50:41.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Av6oRqgE3kLwu092m66ZMA.png" /></figure><p>As 2024 draws to a close, the software industry has seen tremendous shifts that will carry significant weight as we move into 2025. The trends we’ve observed this year at Yassir are not fleeting; they are shaping the future of software development in profound ways.</p><p>Hybrid jobs are becoming the new norm of software jobs; generative artificial intelligence is fundamentally changing how we write code, high-performance languages like Go and Rust are driving efficiency in large-scale systems, and proper system design is more critical than ever for scalability and reliability.</p><p>Understanding these trends is essential for any software engineer who aims to thrive in their career.</p><ol><li><strong>The Rise of Hybrid Jobs</strong></li></ol><p>As a Staff Engineer, I oversee a team of over 30 engineers spread across 10 countries, guiding the technical direction at Yassir. In the past, this role required being in the office which meant I could only guide the team members located in my beloved Cairo.</p><p>Today, much of this can be done remotely with a laptop, a reliable internet connection, and good coffee. This has allowed us to scale our teams faster and helped me be available for folks from Morocco to Pakistan.</p><p>We’ve adopted a hybrid model that combines the best of both worlds. Teams can work from home, enjoying flexibility and autonomy, but also come into one of our office hubs for collaborative sessions and in-person problem-solving and coaching.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p>This hybrid approach is becoming the norm in software engineering. Many companies are finding a balance between remote and in-office work, allowing for adaptability while still fostering deeper team connections through occasional interaction and ensuring junior members are offered the support they need. Hybrid jobs offer the flexibility and efficiency of remote work, while maintaining the benefits of in-person collaboration when it’s needed most. This shift has transformed how we approach teamwork, enhancing both productivity and team cohesion in the tech industry.</p><p>2. <strong>AI: The Game Changer</strong></p><p>As teams embrace remote work, another force transforming software development workflows is the integration of Artificial Intelligence(AI). In today’s world, AI has stormed by force nearly every industry, and it’s almost impossible for anyone, regardless of their field, to avoid hearing about or using tools like ChatGPT. For Generation Z, AI tools such as ChatGPT will be as commonplace as the internet itself — resources that were unimaginable just a few years ago. These tools belong to a class called Generative AI, which can be used to moderate conversations, generate content, and assist in a variety of tasks through simple interaction.</p><p>In the software industry, the implications of AI are enormous. It has the potential to revolutionize how we approach coding and development. Today, software engineers can leverage tools such as Github Copilot or Cursor to automate code generation, streamline workflows, and even handle tasks that would have taken hours or days to complete manually. But as with any transformative technology, the question arises: Are these tools truly reliable? Can we trust AI to replace the craftsmanship and problem-solving ability that has always defined software engineering? Can we expect AI to understand the business domain and necessary trade-offs?</p><p>To address these questions, we started a small experiment at Yassir leveraging some of these code generation assistants and trying to understand the impacts on developer productivity.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p>My hunch, in short, is that while AI tools can automate many tasks, they do not replace the deep expertise, problem-solving abilities, and creativity that human engineers bring to the table. Think of AI as a powerful assistant that can augment your work (i.e. a copilot) — streamlining routine tasks, suggesting optimizations, and even generating code snippets. However, the responsibility for ensuring that the final product is scalable, secure, and reliable still lies with you, the engineer.</p><p>For junior engineers, I strongly recommend developing foundational programming skills before diving into AI-generated code. Relying too heavily on these tools from day one can hinder your understanding of core concepts and problem-solving techniques, which are essential for long-term growth in the field. AI can assist with menial tasks, but real engineering still requires human intuition, experience, and judgment.</p><p>In conclusion, AI is undoubtedly a game changer for the software industry and beyond. It has opened doors to efficiency and innovation that we couldn’t have imagined before. But to fully harness its potential, engineers must understand that AI is a tool — a powerful one — but not a replacement for the human mind. It’s the synergy between human expertise and AI’s capabilities that will drive the future of engineering.</p><p>3. <strong>High-Performance Languages (Go, Rust)</strong></p><p>These days, performance is everything when it comes to digital products, especially for products in the on-demand services space. People want a smooth user experience, and if they don’t get it, they’ll just move on to something else.</p><p>To deliver that high performance, you need the right technology behind your system. The programming language you choose plays a huge role. Sure, if you’re chasing pure performance, you could go with something like C or C++, which are super efficient. But let’s be real, the development experience can be a nightmare, and finding developers who are truly experts in those languages is like finding a needle in a haystack.</p><p>That’s where Go and Rust come in. These two languages are on the rise, offering high performance without the steep learning curve of C/C++. I’ve worked with Go in one of our systems and compared it to JavaScript. We’ve seen a +80% performance improvement in this project using much fewer resources. It is clear that Go outperforms JavaScript significantly when it comes to backend systems.</p><p>As for Rust, I’m planning to dive deeper into it, but from what we’re seeing in the market, compilers and runtimes built with Rust are already proving to be super efficient, especially compared to C/C++. Rust is definitely one to keep an eye on.</p><p>4. <strong>System Design: The Key to Scaling Properly</strong></p><p>When startups first design their systems, they often cut corners in terms of how components interact and function together. The focus is usually on shipping features quickly with the limited resources and time they have. But as these startups start to grow, the problems they buried with that quick-and-dirty approach come back to bite them.</p><p>This cycle is almost inevitable but things are changing, especially as talents become more diffuse globally (see point 1) and more engineers start their own companies. These engineers have seen firsthand how complex large-scale systems can be, but they also know that when systems are well-designed, they drive success and help companies scale efficiently.</p><p>For engineers today, it’s crucial to start thinking about system design early on. A great resource is the book <em>“The System Design Interview”</em> by Alex Xu. As you grow in your career, you’ll eventually face interviews that challenge you to design specific system components. If you get a handle on system design early, you’ll be setting yourself up for long-term success.</p><p><strong>Conclusion</strong></p><p>It’s clear that the software industry is undergoing massive changes that will continue to shape the way we build and scale systems in the coming years. To stay ahead, embrace AI tools, invest in high-performance languages, and make system design a priority. The future belongs to those who prepare for it today.</p><p><strong>About the Author</strong></p><p>I’m Yahya ElAraby, a staff software engineer at Yassir, with a decade of experience in the software industry. My journey has been defined by a passion for problem-solving, technical leadership, and driving innovation in engineering teams.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acabad966d22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we achieved a 93% success rate in digital payments, and what it means for the rest of Africa]]></title>
            <link>https://medium.com/@Yassirtech/how-we-achieved-a-93-success-rate-in-digital-payments-and-what-it-means-for-the-rest-of-africa-d67f7bdc8293?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/d67f7bdc8293</guid>
            <category><![CDATA[digital-payment]]></category>
            <category><![CDATA[yassir]]></category>
            <category><![CDATA[africa]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Wed, 22 May 2024 10:32:00 GMT</pubDate>
            <atom:updated>2024-05-22T10:35:23.203Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>Digital commerce continues to grow in Africa. With the recent COVID-19 outbreak, restrictions were placed globally everywhere — from airports to retail outlets — forcing the adoption of digital commerce across multiple regions. As a result, Africans tuned in online and have not slowed down since. According to a global study by Mastercard conducted in 15 markets, consumers are increasingly moving away from cash and opting for contact-free and digital payment experiences — and they don’t expect to return. E-commerce is also seeing a surge, with <a href="https://www.mastercard.com/newsroom/press-releases/2020/june/mastercard-spendingpulse-estimated-53-billion-in-additional-us-e-commerce-sales-as-pandemic-drives-consumers-online-in-april-and-may/"><strong>Mastercard SpendingPulse</strong></a> reporting record growth rates across the globe as consumers increasingly shop online.</p><p>Although initially focused on the Maghreb, Yassir started its expansion across other EMEA regions, and this came with an accompanying and exciting challenge — localizing digital payments per region, which, according to the<a href="https://www3.weforum.org/docs/WEF_Addressing_E-Payment_Challenges_in_Global_E-Commerce_clean.pdf"> <strong>World Economic Forum, 2018</strong></a>, is a determinant of the success or failure of e-commerce. This report documents the exciting challenges we faced, how we conquered the challenges, and how we are using the insights from this experience to shape novel innovations in different parts of Africa.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p><strong>The Challenge</strong></p><p>Strong dominance in the Maghreb region and tight government policies on financial services may have stifled the pace of digital innovation (e.g., card tokenization, server-to-server integrations, etc.), regardless of PCIDSS, SOC, or any other security/compliance standards. Issues such as this will naturally impact the creative boundaries of technical creatives; however, with Yassir, it was different, as the Payment team is armed with diversity. As with any startup, technical depth is often sacrificed for speed, but this was a good problem.</p><p>We had built a multi-currency payment orchestrator localized for each region, but we needed some time to observe product adoption, study usage patterns, and discover insights for optimizations and improvements. We noticed that in one of the markets — South Africa- Mastercard (MC) had more local dominance than Visa; ironically, MC debit cards had an unusual failure rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TKNaPFoY8n8equd_" /><figcaption><strong><em>Fig 1: Comparative analysis of card processing networks adoption rate</em></strong></figcaption></figure><p><strong>Problem Solving with Data</strong></p><p>This challenge was a good one, as it originated from a hybrid security and user experience update MC had just made to their infrastructure to protect merchants from chargeback fraud while provisioning a seamless user experience for merchants to optimize their systems for recurring payments/revenue. A new instruction type was instituted — eliminating the need for cardholders to tokenize every time they wanted to make a payment online.</p><p>Analyzing the transactions revealed a format code 800.100.156 for unsuccessful transactions, unique to MC cards. This happened as a result of failed authentication when a customer wanted to make a payment. However, on discussing with our providers, we discovered a mandate requiring merchants to set their standingInstruction.type to UNSCHEDULED and point initial transactions to Customer initiated transaction (CIT) type, enabling first-time card users to authenticate but returning card not to, using the Merchant initiated transaction (MIT) type to by-pass auth enforcement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hPqAcFf3dKeTHYRS" /><figcaption><strong><em>Fig 2: Analysis of error codes</em></strong></figcaption></figure><p>The concept of 3D secure authentication is one of the paradoxes of the payment processing industry, because if authentication is not enforced, it makes the card acquirer vulnerable to chargeback fraud. However, it is enforced for every transaction, it can reduce the success rate of payments by up to 40%. Finding a balance will always be a no-brainer, and Payment processing leaders such as<a href="https://res.cloudinary.com/dugcmkito/image/upload/v1673854929/Transform_Guest_Shopping_to_A_Member_Experience_117f3292bf.pdf?updated_at=2023-01-16T07:42:09.831Z"> Bolt</a> who have succeeded at creating a seamless UX balance at scale, boast of increasing conversion rate by up to 70%.</p><p><strong>Business Outcome</strong></p><p>Like a Domino effect, solving this problem solved two other associated problems over time, such as risk management timeout and user authentication failure with format errors 100.380.501 and 100.380.401, respectively.</p><p>After deploying all the solutions, we observed a ~94% success rate for every unique customer who tried to make a payment and 84% success rate for unique transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qcj5EXbviqMnV8Zp" /><figcaption><strong><em>Fig 3: Analysis of change in success/failure rate</em></strong></figcaption></figure><p>This is a noteworthy milestone because it puts Yassir’s payment on par with global industry giants that have been in the domain for decades.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p>A post-mortem call with the provider revealed that this was the highest possible result achievable and top 1% by industry standard, and internal data was sufficient to validate their claim. In the payment space, It is impossible to achieve a 100% success rate because of scenarios such as insufficient funds, issuer declining transactions, the amount exceeding credit, canceled by users, amongst others, which are also an important part of the payment lifecycle, which reveals the activities/behavior of the entire ecosystem — from the issuing bank to the providers, the infrastructure partners, the integrators and finally, the end users being served.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MjdAObzaINEYun4a" /><figcaption><strong><em>Fig 4: analysis of unsuccessful transactions</em></strong></figcaption></figure><p><strong>What This Means for the Rest of Africa</strong></p><p>Sometimes, innovation can mean creating something completely new; other times, it can mean discovering something novel and expanding it into a region where it does not exist, and this has been the case for us. Inspired by this Journey, we have moved beyond just standardizing our payment designs to auditing and co-designing the payment experience of payment partners in other parts of Africa to create a seamless yet secure payment experience for our customers in parts of the Maghreb region and West Africa, giving Yassir an opportunity to frontier innovation in the payment industry across the EMEA region.</p><p>Achieving this milestone is significant as it creates trust, which is necessary for individuals to add and, in fact, save their credit card details on e-commerce solutions. It allows the insights gained from this experience to be replicated in other EMEA regions with notoriously low adoption of digital payment — unlocking these regions for complete digital commerce while becoming a leader in payment orchestration. We believe that this is just day 1.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p><strong>Acknowledgement:</strong></p><p>Boipelo.M, Yousra.H, Amadou.B, Marho.O, Mehdi.A, Xiaoxi.Z &amp; Other members of the payment processing team.</p><p><strong>Onothoja Ron (Ogheneruona),</strong></p><p><strong>Product Owner/Lead, Payments processing.</strong></p><p><a href="https://www.welcometothejungle.com/en/companies/yassir"><strong>Learn more about Yassir</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d67f7bdc8293" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Collaboration to System: The Birth of SEFAR]]></title>
            <link>https://medium.com/@Yassirtech/from-collaboration-to-system-the-birth-of-sefar-0587938325ad?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/0587938325ad</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[yassir]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Tue, 23 Apr 2024 13:30:23 GMT</pubDate>
            <atom:updated>2024-04-24T10:31:04.656Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>Our journey began as a small team with a big challenge: merging ride-hailing, delivery, and financial services into a single, powerful SuperApp. Existing apps functioned independently, relying on a basic UI kit that lacked customization and scalability. Fixing it wasn’t an option.</p><p>Our first dilemma: build or buy a design system? Buying wouldn’t provide the understanding needed for long-term success. Off-the-shelf systems lacked the specialization, character, and accessibility we needed. Additionally, vendor lock-in and limited RTL (right-to-left) UI support were important concerns, especially for an application that mainly operates in Arab countries.</p><p><strong>The Challenge: Building a Foundation for the Future</strong></p><p>Creating a SuperApp that covers multiple user needs meant crafting a design system from the ground up. We embarked on a deep exploration of color palettes, meticulously balancing weight and harmony while prioritizing accessibility from the very beginning. This included tokenizing our color system for easy adaptation during a planned rebranding project.</p><p>Typography presented another hurdle. Most Latin fonts lack support for Arabic characters. We meticulously matched the look and feel, ensuring consistent baselines and weights across both alphabets to deliver a seamless reading experience for all users.</p><p>But the challenges didn’t stop there. Building bidirectional and responsive UI components for right-to-left (RTL) interfaces proved particularly complex. We tackled everything from simple elements to intricate layouts, ensuring all components functioned flawlessly regardless of language direction. We’ll delve deeper into these specific challenges in future articles.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-2H9edRZjQgRp3zO" /></figure><p><strong>Fostering Collaboration: Building SEFAR Together</strong></p><p>Given the challenge’s nature and our team’s size, we decided to approach it with a collaborative spirit. Eight passionate designers from various product domains volunteered their expertise to form the core SEFAR team. Their diverse perspectives ensured the system catered to the needs of all our products.</p><p>Building a successful design system requires robust governance. We established a comprehensive set of processes encompassing every step of the development lifecycle:</p><ul><li><strong>Discovery:</strong> We hosted collaborative workshops that fueled our initial design decisions, for component usage across domains.</li><li><strong>Delivery:</strong> A well-defined workflow that ensured efficient component creation and library maintenance.</li><li><strong>Review:</strong> We embraced the 4-to-8-eye principle for both design peer review and developer handoff review to foster open communication and ensure craft quality.</li><li><strong>Handoff &amp; Versioning:</strong> Clear handoff procedures and a version control system maintained consistency and facilitated collaboration across teams.</li><li><strong>Bug Reporting &amp; Support:</strong> Efficient bug reporting processes and ongoing support addressed issues promptly.</li></ul><p>Our vision for SEFAR resonated with the business. Recognizing its long-term benefits, they provided critical support by allocating eight developers from different platforms (iOS, Android, Web) to work alongside the design team. This collaborative, cross-functional approach ensured the seamless integration of SEFAR into our development workflows.</p><p>This combined section emphasizes the collaborative spirit, details the established governance processes, and highlights the crucial buy-in from the business for developer support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QtQzMA7CcPIZqBf3" /></figure><p><strong>SEFAR: A Symphony of Design Disciplines</strong></p><p>SEFAR transcends the boundaries of a typical UI component library. It functions as a comprehensive <strong>“System of Systems,”</strong> harmonizing various design disciplines to create a cohesive user experience. Here’s how each element contributes to the symphony:</p><ul><li><strong>Design:</strong> SEFAR’s core offering lies in its vast library of pre-built, reusable UI components. The majority of these components are opinionated, therefore encompassing behavior and business logic, to ensure consistent, efficient, and scalable behavior across all product domains without being over-generalized. These components are then used to form domain-specific Patterns, where a core component is properly adjusted, within a range of given out-of-box preferences, to address each domain’s needs</li><li><strong>Illustration:</strong> Visual communication plays a vital role in user experience. SEFAR boasts a rich library of over 200 illustrations, empowering designers to enhance interfaces and engage users. The potential for a future illustration system is also under exploration, offering an even more streamlined approach to visual storytelling.</li><li><strong>UX Writing:</strong> Clear and consistent user communication is paramount. SEFAR champions multilingual UX writing (English, French, Arabic + dialects), ensuring a seamless user experience across different languages. Features like live integration with Lokalise, a translation management platform, further streamline the localization process.</li></ul><p>By integrating these UX disciplines, SEFAR creates a unified design language that fosters a consistent and positive experience for users, regardless of their product or language preference. This holistic approach positions SEFAR as a powerful tool for driving user engagement and brand recognition.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*STgcFvJLLck84pzY" /></figure><p><strong>Conclusion: A Collaborative Triumph and A Look Ahead</strong></p><p>SEFAR’s journey is a testament to the power of collaboration. Recognizing the need for a unified design language, a passionate team of designers and developers came together, fueled by a shared vision. We didn’t just build a design system; we created a collaborative environment that went beyond departmental boundaries. The high adoption rate of SEFAR across our products speaks volumes about its success, demonstrating how it empowers both designers and developers to create a cohesive user experience.</p><p>But SEFAR is not a static entity. It’s a living, breathing system that continuously evolves alongside our products and user needs. In future articles, we’ll delve deeper into SEFAR’s functionalities, exploring the intricacies of its component library, its commitment to accessibility across various platforms, and its potential for seamless integration into global experiences. Finally, we’ll discuss the ongoing governance processes that ensure SEFAR remains a valuable tool for all teams and a cornerstone of our design philosophy.</p><p>Stay tuned as we continue to refine SEFAR and showcase its role in elevating our design experience. We believe SEFAR holds immense potential for not only our products but also for the design community at large. We’re excited to share our learnings and explore the possibilities that lie ahead.</p><p><strong>About The Author</strong></p><p>Dimitrios Arapis</p><p>Head of Product Design &amp; User Experience</p><p><a href="https://www.welcometothejungle.com/en/companies/yassir"><strong>Learn more about Yassir</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0587938325ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Platform Engineering is transforming the use of Modern-day Cloud Native Technologies]]></title>
            <link>https://medium.com/@Yassirtech/how-platform-engineering-is-transforming-the-use-of-modern-day-cloud-native-technologies-c55e5060c4b4?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/c55e5060c4b4</guid>
            <category><![CDATA[cloud-technology]]></category>
            <category><![CDATA[yassir]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Mon, 04 Mar 2024 15:38:39 GMT</pubDate>
            <atom:updated>2024-03-06T13:44:58.985Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>In this article, we discuss how Platform Engineering is used at Yassir to transform the use of Cloud-native tooling with a focus on the introduction of the principles of self-service, Internal Development Platforms (IDPs), and automated infrastructure. We also delve into how Platform Engineering benefits such services by encouraging automated infrastructure provisioning, enhanced observability and monitoring, enforced security practices, and finally scalability and resilience.</p><p><strong>Platform Engineering; A fresh air</strong></p><p>Platform Engineering is a discipline that focuses on building tools that combine automated infrastructure and self-service capabilities to provide developers the ability to create apps using standardized frameworks, instead of starting from scratch. Platform engineering aims to create Internal Developer Platforms (IDPs) that abstract the underlying complexities of infrastructure, enabling developers to focus on delivering value, without being experts in infrastructure thereby improving software delivery, reducing toil, and increasing operational efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kX3OdXZIIlj1QagH" /><figcaption><a href="https://www.thoughtworks.com/en-th/insights/articles/platform-engineering-help-developers-deliver-more-value-at-a-lower-cost"><em>Source: How you can help Developers Deliver more value at lower cost (ThoughtWorks)</em></a></figcaption></figure><p>According to the State of Platform Engineering Vol 2, when developers focus on writing code completely, organizations can slash Time To Market (TTM) by 30%, achieve 4x higher deployment frequency and accelerate lead time by 30%.</p><p><strong>How we transform Developer Experience and Cloud Operations with Platform Engineering at Yassir</strong></p><p>At Yassir, we are committed to leveraging cutting-edge tools and practices to deliver innovative services and solutions. We rely on tenets of Platform Engineering to bridge the gap between DevOps practice and the Software Development Cycle, enabling our engineers to deploy faster, easier, and without much friction. One of the cornerstones of platform engineering at Yassir is the use of the CDKTF library for designing infrastructure. This library allows our developers to review software in a relatable programming language without the hassle of having to learn Terraform or understand its syntax.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*SbLEMtxyNSdtgo2W" /><figcaption><a href="https://github.com/hashicorp/terraform-cdk"><em>Source: Github Repository for CDKTF</em></a></figcaption></figure><p>At Yassir, we are focused on the right developer tooling to allow us ship products faster and deploy new releases seamlessly. We make use of an open-source platform called backstage as our Internal Developer Platform(IDP) to encourage collaboration between teams, squads and domains. In addition to backstage, we use another open-source tool called Apache Devlake for our core DORAmetrics. We use Devlake to measure deployment frequency, change failure rate and other necessary metrics that enhance observability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X6L2MDTqvtwg7cok" /><figcaption><em>Source: Yassir’s backstage Homepage</em></figcaption></figure><p>Security is a major concern at Yassir, we employ the use of standard security practices in the use of HashiCorp Vault for secrets management and SonarQube for continuous vulnerability scanning and static code analysis. We integrate these security tools into our CI/CD pipelines, automatically scanning for vulnerabilities and bugs. We also utilize PagerDuty, to ensure the highest reliability and availability of our services. We use pager duty for incident response to automate escalations and manage our incident response systems.</p><p>(<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies here</strong></a>!)</p><p>With the strategic implementation of the afore-mentioned services and tools, Yassir has completely transformed its developer experience and Cloud Operations, making it easier to abstract complexity, automate process and build software securely from start to finish.</p><p><strong>Introducing Platform Engineering to your organization</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LaVKpy75048QT3tG" /><figcaption><a href="https://learn.microsoft.com/en-us/platform-engineering/what-is-platform-engineering"><em>Source: What is Platform Engineering (Microsoft Learn)</em></a></figcaption></figure><p>Introducing platform engineering to your organization should be an iterative process that requires careful planning and continuous improvement. The goal is to build a self-service platform, encourage its adoption then initiate a culture switch to the self-service orientation. The following steps are quick steps ways to achieve this:</p><ul><li>Assess the current state and define the objectives of your migration to Platform engineering.</li><li>Gain Executive support and align stakeholders.</li><li>Establish your first Platform Team.</li><li>Develop a Platform Strategy.</li><li>Implement a pilot project.</li><li>Document your findings and iterate.</li></ul><p><strong>Conclusion</strong></p><p>Platform engineering is leveraging cloud-native technologies to redefine how software is deployed and improve the collaboration between Software engineering and Infrastructure. Also, by abstracting layers of infrastructure into modules and APIs, Platform engineering is improving developer autonomy and embedding best practices into the software deployment process. Adopt Platform Engineering in your organization today.</p><p><strong>About The Author</strong></p><p>Michael Mekuleyi is a Senior DevOps Engineer at Yassir with over 6 years of active Software engineering and DevOps experience. Michael is also passionate about the community as he volunteers as a Cloud Champion for Google Cloud and also as a Community Builder for AWS. Michael is a prolific Technical Writer and speaker, he has written over a dozen articles and has spoken at over 20 conferences. Michael is also a Terraform Associate Cloud engineer, certified by Hashicorp and A Professional DevOps Engineer certified by Google. Apart from writing code and contributing to Open-Source, Michael enjoys bodybuilding, cooking and making new recipes. You can follow Michael on Github here =&gt; <a href="https://github.com/monarene">https://github.com/monarene</a></p><p><a href="https://www.welcometothejungle.com/en/companies/yassir"><strong>Learn more about Yassir</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c55e5060c4b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering OKRs: Is losing weight an Objective or a Key Result?]]></title>
            <link>https://medium.com/@Yassirtech/mastering-okrs-is-losing-weight-an-objective-or-a-key-result-a7343c63f0ce?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7343c63f0ce</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[yassir]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Thu, 08 Feb 2024 14:37:07 GMT</pubDate>
            <atom:updated>2024-02-08T14:37:31.224Z</atom:updated>
            <content:encoded><![CDATA[<h4>Connecting OKRs approach to the Simon’s Sinek Golden Circle model</h4><h3>What are OKRs in the first place?</h3><p>First of all, let’s start from the beginning and explain what this methodology called OKRs is. OKRs (Objectives and Key Results) is a goal-setting framework used by organizations and individuals to define and measure their objectives. Objectives are qualitative, aspirational goals, while Key Results are specific, measurable outcomes that indicate progress. This approach fosters alignment and transparency at various levels within an organization, from company-wide goals to team contributions. Regular check-ins ensure focus and adaptability, creating a dynamic system for achieving and celebrating success. OKRs promote <strong>transparency, collaboration, alignment and agility in goal pursuit</strong>.</p><p>As we entered a hypergrowth phase, it became urgent to adopt an intentional way to set and track goals. We use OKR to focus on the right direction (Do the right things), align on the right things (Do things right) and making fast decisions autonomously (Do things fast).</p><h3><strong>Starting with the Why</strong></h3><p>When coaching on OKRs, I often notice individuals start setting their OKRs (Objective and key results) by discussing tasks, action plans and initiatives. Few can easily connect these solutions with outcomes, and even fewer can explain why they engage in those initiatives in the first place.</p><p>If this resonates with you, know that many share the same experience. In his <strong>Golden Circle theory</strong>, Simon Sinek explained how we are programmed to communicate. We’re used to expressing <strong>WHAT</strong> we do instead of <strong>WHY</strong> we do things. Moreover, we spend much time discussing solutions like products, services, and ideas (outputs), neglecting the reasons behind these solutions. (<a href="http://(Check our open vacancies)"><strong>Check our open vacancies here</strong></a>!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*Lk41hI6-19ePDaVm" /><figcaption><a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=de">The Golden Circle Model</a></figcaption></figure><p>Simon mentioned that leading companies communicate from the inside-out, starting with why they exist, then how they function, and finally, what they do.</p><p>The field of Neuroscience highlights the importance of always starting your message by stating your purpose. When presenting your <strong>WHY</strong>, you activate the part of the brain that activates behaviors — Prefrontal Cortex.</p><p>Starting with the why helps us uncover the true purpose and objectives of a task. This in turn, might transform how we motivate people to pursue more meaningful goals towards making Africans’ lives easier than just “developing a new feature”.</p><h3>Objective &amp; Key Results — Real-life example</h3><p>When I guide Product and Tech teams at <strong>Yassir</strong> in setting significant objectives and Key Results, I often ask them if “losing weight” is considered an Objective or a Key Result.</p><p>Generally, individuals respond by identifying it as an objective. The reason for this is, as humans, we usually perceive goals like “Getting in shape, losing a few pounds, gaining muscles…etc” as more tangible and measurable.</p><p>Following that, I ask another question <strong>“Why would someone try to lose weight?” </strong>Responses come in like this:</p><ul><li>To play around with their kids without feeling tired</li><li>To lace their shoes without struggling</li><li>To increase their self-esteem</li><li>To have better health and live longer</li></ul><p>Setting goals focused only on gaining muscles and losing weight may not be that inspiring after a while and would likely lead to giving up in the middle of the journey. However, when we design our metrics to be focused on deeper reasons behind the goal, we send a strong message to our brain: “It is important to keep going to the gym because we are tired of not being able to lace our shoes properly”.</p><h3>Setting OKRs using the Golden Circle model</h3><p>To stimulate the part of the brain that controls behaviors, we can take inspiration from the Golden Circle model, starting with the objective instead of the key results or tasks. This involves:</p><ol><li>The clarity of our objective (WHY)</li><li>The discipline of tracking our key results (HOW)</li><li>The consistency of what we are doing to reach it (WHAT)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v8d1VsJwI5KXrM75" /><figcaption>The Golden Circle &amp; OKRs</figcaption></figure><p>Returning to the example of getting in shape and setting a personal OKR by using the same approach above, we might have:</p><p><strong>Objective: Become healthier than ever to be able to play with my kids</strong></p><ul><li>KR1: <em>Lose weight from 85 kg to 80 kg</em></li><li>KR2: Decrease my body fat percentage from 27% to 22%</li><li>KR3: Reduce my waist circumference from 104 cm to 94 cm</li></ul><p><strong>Objective: Enhance my running performance to complete Berlin’s Ultramarathon</strong></p><ul><li>KR1: Achieve an average pace of 5:30’’/km during training.</li><li>KR2: <em>Lose weight from 75 kg to 72kg</em></li><li>KR3: Increase my VO² max from 65 to 75 mL/kg/min</li></ul><p>Both examples share the goal of losing weight, but their action plans (tasks) may vary based on the underlying context (reason). Someone aiming to shed pounds for better health might establish tasks like reducing sugar and carbohydrate intake, whereas an individual focused on improving running performance may set goals such as increasing exercise frequency or hiring a professional coach. The crucial factor is must align our initiatives with the underlying motivation (WHY); failure to do so may lead us in the wrong direction.</p><h3>Takeaways</h3><p>Many teams struggle with OKR implementations due to the inability to change how they work. While new frameworks or tools can help, changing the way we approach our goals and tasks can make significant improvements in our work results. What I learned at Yassir is that prioritizing purpose in setting OKRs proved to be effective. Having a narrative that mobilizes and a clear and detailed reason simplifies tasks and makes them more straightforward toward the goal. (<a href="https://jobs.lever.co/Yassir"><strong>Check our open vacancies</strong></a>!)</p><p>As the OKR framework continues to gain prominence in the start-up world, OKR practitioners and champions are asked to be outstanding storytellers who can articulate a compelling vision for why we do what we do (be it losing weight or otherwise).</p><h3>About the Author</h3><p>Luiz Corandin is Programme Manager and an OKR Coach at Yassir. He is a certified OKR Coach with 25+ deployments since 2019, endorsed by Agile Institute Brazil and OKRsTraining.com in the US. Proud member of the Global OKR Coach Network (OKR Mentors). He helps Yassir’s Product Teams integrate product strategies seamlessly.</p><p><a href="https://www.welcometothejungle.com/en/companies/yassir"><strong>Learn more about Yassir</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7343c63f0ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Driving Engineering Performance the Yassir Way]]></title>
            <link>https://medium.com/@Yassirtech/driving-engineering-performance-the-yassir-way-63c8706a1249?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/63c8706a1249</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[berlin-tech]]></category>
            <category><![CDATA[yassirimpacts]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 10:33:24 GMT</pubDate>
            <atom:updated>2023-12-08T10:34:20.981Z</atom:updated>
            <content:encoded><![CDATA[<p>As tech teams grow, every executive would like to know whether they are still (high-) performing. McKinsey, Gartner, and some industry luminaries all came up with their own answers, but as every company is different, we felt there was always something missing in what was out there.</p><p>We pondered a lot about developer productivity and performance. We have built our own framework which has shown good results so far. In this post, I will summarise the core pillars we rely on for measuring and driving engineering performance. If you are on a similar path of hyper-scale, this could serve as a good starting point for you to adapt and improve.</p><p><strong>Our performance framework relies on 4 pillars:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*th24uhO6DqoEHPdp" /></figure><p><strong>1) Company OKR to set the direction and provide alignment</strong></p><p>We use the OKR Framework to define and communicate what the teams need to achieve during a set period. Objectives are shared amongst product and tech teams. Each team inherits a set of ambitious OKRs that include business outcomes as well as engineering performance goals. These objectives are also co-created with the teams.</p><p>The most important engineering objectives that we share are:</p><ul><li><strong>Velocity</strong>: how fast we can deliver stuff</li><li><strong>Quality &amp; Reliabilit</strong>y: how stable and defect-free our services are</li></ul><p>OKRs are a great way to ensure smooth execution and build a culture of accountability. The co-creation elements help strengthen ownership. The shared nature of the OKRs provides the required focus.</p><p>We tend to overshare and over-communicate about our OKRs internally. Reminding the teams on every occasion about the objectives and overall progress.</p><p><strong>2) Key metrics and targets to measure progress</strong></p><p>Once you have your objectives, you need to define the target key results to achieve. We figured there are three categories of metrics that are important for us:</p><p>a) <strong>Lag metrics to define what success looks like</strong></p><p>In our case, each objective described above will come with 3–4 key results. We rely on DORA Metrics to set the targets as well as a home-grown “reliability score” and Tech Debt Index.</p><p>From one quarter to another, we might include additional key results that are usually aligned with some target benchmarks. These “Lag Metrics” (i.e. metrics that show the outcomes) are great to align teams and offer them a clear definition of success they can strive to reach.</p><p>b) <strong>Lead metrics to foster the conditions of success</strong></p><p>We noticed providing a clear idea of where we want to go is not enough to achieve high performance. We need, at the same time, to enable the conditions and environment for high performance. We achieve this by tracking “lead metrics” (i.e. input-based metrics that show what is being done). Here, our focus is on two areas:</p><ul><li><strong>Team Composition</strong>: we have strong views on what a high-performing team looks like, from the team size (smaller teams tend to perform better), the skills it contains (cross-functional teams tend to perform better), or the level of seniority. We call this the Yassir SAUCE. We track how each team fares on this team composition index and strive to get all teams to perfection.</li><li><strong>Capacity Allocation</strong>: we monitor our engineering efforts spent and ensure that a certain level is dedicated to maintenance and tech improvement (vs building new capabilities), sprint over sprint.</li></ul><p><strong>c) Sentiment Analysis for Reality Check</strong></p><p>We can spend a lot of time in Excel sheets tweaking the best formula for high-performing teams, but nothing replaces the unfiltered feedback of the front-line teams to inform on how well we are doing. A solid performance framework should also make space for the voice of the engineers.</p><p>We run several surveys throughout the year to capture this voice. Employee NPS score is a critical metric for us. We also measure psychological safety, developer satisfaction, and our agile maturity regularly. This feedback helps us calibrate our interventions and identify gaps that would otherwise go unnoticed.</p><p><strong>3) Tech Roadmap to ensure execution</strong></p><p>Once we have goals and targets, we can layer in initiatives that enable us to move the needle. Initiatives are organised into a technical roadmap that lives alongside our product roadmap and includes activities such as tech debt management, platform improvements, etc. We also hold demo days and architecture reviews to check on progress and offer a forum for discussion and feedback. We tend to invest 20–30% of our capacity into the tech roadmap each quarter.</p><p>Having a plan and a cadence to review progress helps us strengthen our execution muscle and hold a high standard of accountability.</p><p><strong>4) Continuous monitoring of individual performance to foster growth &amp; development</strong></p><p>The last bit of the framework is about individual performance. Performance reviews are a powerful tool to shape certain behaviors and identify and grow your top performers. You will need a standardized career framework that clarifies the expectations for each role and what is needed to move to the next level. At Yassir, every engineer is evaluated against 4 broad behaviors that reflect our performance expectations as well as our values. Crucially, we decouple individual performance from OKR execution.</p><p>We recommend running bi-annual performance reviews instead of just once a year. That helps capture a more accurate picture. In fact, performance reviews should not be limited to once or twice a year, we encourage all our managers to run 1:1 meetings with their subordinates to provide/receive feedback constantly. We find that type of direct communication to be the number #1 productivity booster.</p><p><strong>Wrapping up</strong></p><p>To summarise, hundreds of models for measuring engineering performance exist. Choose the one that suits your environment, as no two companies are similar. Ours, built through trial and error and observing thousands of developer hours, relies on four key pillars:</p><ul><li><strong>Company objectives:</strong> shared across product and tech teams that cover velocity and quality</li><li><strong>Key metrics</strong> and ambitious targets that inform about outcomes, key activities, and developer sentiment progress</li><li><strong>Tech roadmap:</strong> that highlights what needs to be done by whom</li><li><strong>Individual performance</strong>: that links company performance objectives and expectations to individual career goals and growth plans</li></ul><p>This framework has been instrumental in overhauling Yassir tech capabilities. We’ve seen substantial improvement across our lead time for change (-30%), deployment frequency (+100%), and Mean time to Restore (-90%) as well as developer satisfaction (as measured by eNPS).</p><p>The key is to combine the right mix of metrics (aligned with your business goals) with a solid discipline of execution and excellence. In doing so, one should not rely on metrics solely or too eagerly as it will most certainly fail. Neither should you overlook basic HR hygiene (competitive pay, work conditions, etc) or your team’s motivation and well-being. It’s a system and for it to work, you will need to find the right balance.</p><p>Ultimately, the most important thing is to start somewhere. As long as your high-performance expectations are clear and shared by everyone, you are on the right path. Perhaps, one of the biggest risks with such an endeavor is to over-engineer it and, in doing so, get distracted and lose focus over the business. High performance makes sense, if and only if it enables us to serve our customers better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63c8706a1249" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hotline Bling: Bringing Drivers and Riders Closer through In-App Chat]]></title>
            <link>https://medium.com/@Yassirtech/hotline-bling-bringing-drivers-and-riders-closer-through-in-app-chat-afe179f2a851?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/afe179f2a851</guid>
            <category><![CDATA[chat]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[yassir]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Thu, 12 Oct 2023 08:47:05 GMT</pubDate>
            <atom:updated>2023-10-13T10:58:46.329Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>With the purpose of making communication easier, more cost-effective and secure, we decided to add in-app chat options for our riders and drivers. Here’s how and why we’re doing it!</strong></p><p>Imagine you’re a rider standing by the library. You have your earphones on, you have requested a ride and a driver accepted, then your favorite song comes on. You want to contact your driver to describe to them exactly where you are but do not want to cut off the music. You wish you could just text them. Well, now you can do that without having to leave the Yassir Super app.</p><p>Listening to your favorite music is but a minor example of situations where texting comes in handier and more effective to ensure a pleasant ride experience. For drivers, in particular, they can simply send a text instead of calling while driving. Besides, you don’t need to leave the app to send a text or call, find everything in one place!</p><p><em>Check out our </em><a href="https://www.welcometothejungle.com/en/companies/yassir"><em>open positions</em></a><em> and join our team!</em></p><p><strong>Why embedding Chat?</strong></p><ul><li><strong>More convenience: </strong>Miscommunication can lead to losing your ride or missing an important appointment. A convenient chat conversation can prevent that by making it easy to connect drivers and riders.</li><li><strong>A Cost-effective solution: </strong>Is your data still running but you do not have enough balance left? You can still request or take up rides with Yassir and all your communication with your driver/rider will be done for free on the app.</li><li><strong>Enhanced safety and privacy: </strong>Oftentimes, people do not like to share their personal phone numbers with people they do not know. In order to ensure more privacy, the in-app call and chat feature helps you avoid sharing your phone number.</li></ul><p><strong>How does it work?</strong></p><p>Using the feature is rather simple. Here is a mini guideline:</p><p><strong>Check Your Message Status!</strong></p><p>To send a message, you can tap on the text field, type your message then hit send to your driver. You will then be able to see the status of your message; whether your driver has seen it or not yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*a8e8_xdRNfQtjnVF_t2MfA.gif" /></figure><p><strong>You Can Always Call!</strong></p><p>In case the driver did not see your message, you can always resort to a call with the availability of a call button at the top<strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*JJbz6QZhujcS9Bm-b9HvXw.png" /><figcaption>Message status</figcaption></figure><p><strong>No Need to Type while You Can Have Message Suggestions</strong></p><p>For smoother and easier communication, we introduced message suggestions as well!</p><p>Both you and your driver can have a set of multiple suggested messages that you can select from. Once selected, the messages will be sent instantly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*tqwZz-ZEfs5ToRUbaEFKOw.png" /><figcaption>Message suggestion</figcaption></figure><p><strong>What’s Next?</strong></p><p>In an effort to make communication for our users more seamless and efficient, we plan to include in-app messaging for our other products, as well. The feature will not only be exclusively used for our ride-hailing product, but customers, delivery personnel and vendors will also have the ability to communicate with each other using the app.</p><p>Importantly, we are also exploring adding voice calls within the chat so that you can talk to your driver seamlessly from within our app</p><p>Stay tuned for future updates from us!</p><p>If you would like to contribute and be part of Yassir, check out our <strong>open positions </strong><a href="https://www.welcometothejungle.com/en/companies/yassir">here</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afe179f2a851" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yassir meets Cairo’s vibrant Tech Ecosystem]]></title>
            <link>https://medium.com/@Yassirtech/yassir-meets-cairos-vibrant-tech-ecosystem-9f45405af626?source=rss-fd6cbe068730------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f45405af626</guid>
            <category><![CDATA[techmeetup]]></category>
            <dc:creator><![CDATA[Welcome to our Yassir Engineering Blog]]></dc:creator>
            <pubDate>Tue, 19 Sep 2023 14:53:36 GMT</pubDate>
            <atom:updated>2023-09-19T15:01:17.839Z</atom:updated>
            <content:encoded><![CDATA[<p>On Thursday, July 27, 2023, Yassir held its first tech meetup in Cairo, where over 60 tech enthusiasts, industry professionals, and thought leaders converged for a great day of inspiration, insights, and connections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_go7HtUH2pMg09zm-2B_jg.jpeg" /></figure><p>The event showcased the remarkable journey of Yassir, notably our bustling tech hub in Cairo, through captivating presentations and engaging discussions hosted by our product manager, Mary Girgis.</p><p>Ismail Chaib, our very own General Manager for product &amp; tech kicked off the day with an introduction to Yassir, leaving everyone eager to learn from our achievements.</p><p>Renowned experts graced the stage, sharing their expertise on cutting-edge topics. Staff Engineer and local Youtube superstar, Yahya ElAraby enlightened us on scaling software to serve millions of users and how this is applied at Yassir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*biPQq6rQTq95xzygudNrTg.jpeg" /></figure><p>Hania Ghannam: product manager explored the future of Super apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5PKt44-2ZIcQPQtiSLymTg.jpeg" /></figure><p>While Ahmed Menaim provided insights into clean architecture in iOS development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_flPPeDpBZPS2M99zjmMg.jpeg" /></figure><p>Finally, Shady Selim, a local Android community organizer and also Yassir’s staff engineer shared his expertise in Android and the latest development in this area. These talks provided attendees with invaluable knowledge to enhance their own projects and hopefully gave some inspiration for the next generation of Cairo-based entrepreneurs.</p><p>The meetup also fostered a vibrant networking environment, where professionals connected, exchanged ideas, and built valuable relationships. It served as a catalyst for potential partnerships, strengthening our team and the Cairo tech community.</p><p>Ahmed Fathi, our talent acquisition manager later reflected that “this event was a great opportunity to meet with the local ecosystem and to live by our commitment to build in the open”. Indeed, Yassir’s Cairo tech meetup was an unforgettable experience, leaving a lasting impact on all who were part of it. From inspiring success stories to insightful talks and vibrant networking, the event showcased the power of collaboration and knowledge sharing within our tech community. We express our deepest gratitude to everyone who joined and eagerly anticipates embarking on future events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-JmGrweEKHdjcar4kCuRg.jpeg" /></figure><p>Looking ahead, Yassir is committed to contributing to fueling local talents. We are excited to continue fostering knowledge-sharing, innovation, and collaboration in the region. Stay tuned for more meetups and opportunities to connect, learn, and thrive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f45405af626" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>