<?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 Mustafa Ezer on Medium]]></title>
        <description><![CDATA[Stories by Mustafa Ezer on Medium]]></description>
        <link>https://medium.com/@ezer?source=rss-6b810b9480f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*E4eYzYbzxmzMTG2d7Aw7sQ.jpeg</url>
            <title>Stories by Mustafa Ezer on Medium</title>
            <link>https://medium.com/@ezer?source=rss-6b810b9480f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:45:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ezer/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[How does documentation drive easier organizational scaling?]]></title>
            <link>https://ezer.medium.com/how-does-documentation-drive-easier-organizational-scaling-a54c80f5cc75?source=rss-6b810b9480f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a54c80f5cc75</guid>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Mustafa Ezer]]></dc:creator>
            <pubDate>Fri, 20 Aug 2021 09:09:22 GMT</pubDate>
            <atom:updated>2021-08-20T09:12:35.779Z</atom:updated>
            <content:encoded><![CDATA[<p>Talking about focusing on the daily work and documenting the knowledge about them. It has always been a nip and tuck.</p><p>But let’s take a moment and put ourselves in the place where the freshmen are on their first day in your organization. You are starting as an employee for a company or an organization that has a <a href="https://martinfowler.com/bliki/UbiquitousLanguage.html"><strong><em>ubiquitous language</em></strong></a> for its own. There is a lot of business logic and complexity inside. And you will be probably anxious since there is a lot to learn and especially in the case where there is no documentation about a specific context, you have to take someone employee’s time to share their knowledge about it. And probably, it will proceed like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*5x12on8lT0RTSsQrTyZ4wA.jpeg" /></figure><p>In the cases where the organizations or the companies have well-documented systems about their lifecycle, the onboarding process will transition to a smooth one. The employee will be able to access related content or information about the context easily. This will also lead to earlier business value delivery for the employee.</p><p>At some point, the documentation process may seem cheap but don’t forget that your employee’s time is expensive. Whenever you’re provided with an opportunity to leverage from it, don’t hesitate to start documenting the knowledge that can be transitable easily.</p><p>So how to increase the impact of the ongoing documentation process — or even where to start?</p><h4>Listen and observe your organization</h4><p>People won’t always come up about missing parts of a puzzle. Take the initiative for what could be better and watch out for the development areas.</p><p>At the end of the day — a lot of communication in our daily lives are verbal and ends up undocumented. Replacing the <strong><em>assumptions</em></strong> with <strong><em>precision</em></strong> is only possible by ensuring that you have documented the obvious in your organizational culture.</p><h4>Always tell stories</h4><p>Take notes from your observations and listenings. Because they are the key ingredients — if people are complaining about it. Start designing your stories around them to keep your content interesting and engageable.</p><p>In web applications and services, there is a metric for user satisfaction called Apdex. Its purpose is to convert measurements into insights about user satisfaction with the response time analysis. Start imagining your documentation as an application. If the response time or time to interact on an application is too high, you won’t be entertained and close that and move to another. Here, the application is your document. Don’t write documents that their time to interact is too high. Try to keep up your Apdex score high with feedback from your stakeholders. Keep your documents updated for the better. Time is expensive, so does our experiences. ✌🏻</p><blockquote>Humans are inclined to see narratives where there are none because they can afford meaning to our lives — a form of existential problem-solving.</blockquote><p><a href="https://www.theatlantic.com/health/archive/2014/11/the-psychological-comforts-of-storytelling/381964/">The Psychological Comforts of Storytelling</a></p><h4>Keep documentation just simple enough — but not too simple</h4><p>Documentation should offer a low learning curve for the reader. Since the reader is here because they want to learn the fundamentals of the context, about the process or even the motivation behind it. It should contain the required parts adequately.</p><h4>Provide information at a different level of detail</h4><p>Especially in technical documentation, provide information at a different level of detail — rather than the steps. Otherwise, if these steps relate to the topics that require knowledge, it still creates an effort for understanding and uncertainty for those affected after the step’s execution. Code snippets to execute only provides a piece of higher-level information about the process. However, the reader should know the reasoning behind those.</p><h4>Don’t underestimate the power of sharing</h4><p>How often we are taking the time to share our knowledge with our peers while we are dealing with our daily jobs? Keeping this personal touch and commitment will lead to better relationships and creates a sense of belonging to our organization. Don’t hesitate to start your writing journey now. At the end of the day, volunteered contribution and ownership will be the key to your organizational growth.</p><h4>Takeaways</h4><p>They say that — “Slow and steady wins the race”. So start documenting today. Even the tiniest contribution might be fuel to the fire for sharing the knowledge for all levels.</p><p>Stay safe and healthy, see you! 👋🏻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a54c80f5cc75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Loki: A Visual Regression Testing for Your Storybook Projects]]></title>
            <link>https://javascript.plainenglish.io/loki-a-visual-regression-testing-journey-on-projects-that-use-storybook-1ff5a8530a51?source=rss-6b810b9480f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ff5a8530a51</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Mustafa Ezer]]></dc:creator>
            <pubDate>Sat, 07 Aug 2021 19:50:34 GMT</pubDate>
            <atom:updated>2021-08-09T09:28:16.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WqvePokMOfMJ9lFt" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles Deluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Functional regressions are the main key to watching out — when people develop and deliver new features to their products. But — so does the visual ones.</p><p>Let’s say you have a UI Library/Design System that is yours or one that your team is developing. If you are familiar with these fancy “UI Library, Design System” keywords, you know that they contain many atomic components, logic and rules. I’m not even talking about the composite components — the ones that are like a card that contains an action button as the default behaviour for its own. For to be more exact about how complex these libraries are in numbers, there are 70 UI components in <a href="https://chakra-ui.com/">Chakra UI </a>— except the hooks.</p><p>While you are delivering new features — functional results, code quality and the most common mistakes that can be made at the development phase may seem easy to observe and manage — since you have scheduled code review sessions as a team. But for the styling aspect — it does not (always). It requires that people have UI awareness, deep knowledge of the library and know-how about how components interact with each other.</p><p>At this phase, we need an autonomic system for us to watch out for the visual changes in the library — besides our eyes. 🤔</p><h3>Loki</h3><p><a href="https://loki.js.org/">Loki</a> is a visual regression library that has been developed by <a href="https://github.com/oblador">Joel Arvidsson</a>. It aims “easy setup, no additional maintenance cost, reproducible test independent of OS and supports all platforms that Storybook does”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3d56b266eac522cf4a0c4345a9f249d/href">https://medium.com/media/e3d56b266eac522cf4a0c4345a9f249d/href</a></iframe><p>Starting with the installation, you can notice that Loki is a library that needs nearly zero configuration. It also handles the part where it locates its config in the <strong><em>package.json</em></strong> file with the CLI.</p><p>After the initialization, you should build your first snapshots to be used as a reference in the future. But before executing the <strong><em>update</em></strong> command, make sure have started your Storybook application since Loki will try to access your stories.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/32da1e8226263c5841341756f07d3cdd/href">https://medium.com/media/32da1e8226263c5841341756f07d3cdd/href</a></iframe><p>After executing the command — now you should be able to see the folder created under <strong><em>.loki</em></strong>, named <strong><em>reference</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/1*6Errr1X0cfuqoLqgcs8cGw.png" /><figcaption>The folder that has been generated by Loki</figcaption></figure><p>Now it’s time to make some changes to the components that are represented in your stories for Loki to watch out for. After making your changes save them and continue with the command:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1cf809cf5c37120baee5c16a87785847/href">https://medium.com/media/1cf809cf5c37120baee5c16a87785847/href</a></iframe><p>Loki will now create new snapshots under the <strong><em>.loki/current</em></strong>. They will be used for comparison of the application’s current state vs. before (based on <strong><em>.loki/reference</em></strong>).</p><p>If there are any regressions or changes that is situated, you can find them under <strong><em>.loki/difference </em></strong>and as you can guess, as an outcome of those, the tests will fail.</p><p>After reviewing those changes, you can continue with executing approve command to approve those changes — if you were made those changes planned.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/59c0cd6782d1db43edf99debc526e900/href">https://medium.com/media/59c0cd6782d1db43edf99debc526e900/href</a></iframe><blockquote>Commit your changes along with the new reference images and repeat.</blockquote><h3>Caveats and personal thoughts</h3><p>To make sure that your use case fits Loki in the first place, you should review /revisit your Storybook practices. You should avoid using your components in just one state that does not tell more about itself. It will gonna make sense if some of the scenarios are included in your stories.</p><p>But even in the cases where the stories are not detailed as much as they should be, I believe that Loki is still introducing us to a new level of observability and autonomy for detecting visual regression.</p><p>As wrapping up, there are lots of libraries for testing and Loki is just one of them. I found the library useful since it’s easy to configure, needs no additional development for test cases. Actually, it was also built with the intention of running on a continuous integration server. You can easily adapt them in your software development lifecycle as well. ✨</p><p>You can find more detailed information about Loki over their documentation:</p><p><a href="https://loki.js.org/">https://loki.js.org/</a></p><p>And here is the GitHub repository for the project:</p><p><a href="https://github.com/oblador/loki">GitHub - oblador/loki: 👁 Visual Regression Testing for Storybook</a></p><p><em>Did you find </em><strong><em>Loki</em></strong><em> useful? What are some of your favourite libraries in testing? Just let me know!</em></p><p><em>And also, if you enjoyed this article, share it with your friends and colleagues.</em></p><p>Stay safe and healthy, see you! 👋🏻</p><p><em>More content at </em><a href="http://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ff5a8530a51" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/loki-a-visual-regression-testing-journey-on-projects-that-use-storybook-1ff5a8530a51">Loki: A Visual Regression Testing for Your Storybook Projects</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation Hackathon, Derin Yoksulluk Ağı & Momentum]]></title>
            <link>https://ezer.medium.com/innovation-hackathon-derin-yoksulluk-agi-momentum-ad93b2757fcb?source=rss-6b810b9480f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad93b2757fcb</guid>
            <category><![CDATA[türkçe-yayın]]></category>
            <category><![CDATA[yazılım]]></category>
            <category><![CDATA[türkçe]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Mustafa Ezer]]></dc:creator>
            <pubDate>Fri, 06 Nov 2020 15:21:20 GMT</pubDate>
            <atom:updated>2020-11-10T08:17:04.701Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*XoUsijgA65uVBv16kg-64w.png" /></figure><p>Merhaba,</p><p>Geçtiğimiz ay içerisinde “Momentum” adıyla, benim de içerisinde dahil olduğum toplam beş arkadaş olarak Innovation Hackathon’a katıldık.</p><h3>Innovation Hackathon</h3><p>Hackathon; COVID-19&#39;un hayatımıza girmesiyle birlikte adına “yeni normal” dediğimiz bu süreçte, Türkiye bazlı sosyal girişimlerin karşılarına çıkan güçlükleri yenme ve sürece daha elastik olarak uyum sağlayabilmeleri için gerekli olan dijital transformasyon önerilerini toplamayı hedefliyordu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*4OkNqrTBOK7DxVMoQD454A.png" /><figcaption>Jüri üyeleri</figcaption></figure><p>Almanya Federal Ekonomik İşbirliği ve Kalkınma Bakanlığı (BMZ)’nın finanse ettiği “PEP-Promotion of Economic Prospects” programı çerçevesinde organize edilen Innovation Hackathon; Alman Uluslararası İşbirliği Kurumu (GIZ), Re:Coded ve Impact HUB İstanbul tarafından gerçekleştirildi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*qVZVF8yMasri3If9Gdj-zQ.png" /></figure><h3>Derin Yoksulluk Ağı</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbrRCYLGgPYU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbrRCYLGgPYU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbrRCYLGgPYU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/85a56f48746710ee5eb98526fcd30f19/href">https://medium.com/media/85a56f48746710ee5eb98526fcd30f19/href</a></iframe><blockquote>Derin yoksulluk içindekiler, yoksulluk sınırı veya açlık sınırı olarak belirlenen durumun çok daha ötesinde zorluklar yaşıyor.</blockquote><blockquote>2019 yılının Aralık ayında kurulan Derin Yoksulluk Ağı’nın gönüllüleri, “Derin yoksulluk yaşayanların öncelikle gıda, barınma, sağlık, eğitim, giysi, psikososyal destek gibi temel haklara erişmeye ihtiyacı var.” diyorlar.</blockquote><p>Derin Yoksulluk Ağı ekibi ile Hackathon’da, eşleştiğimiz sosyal girişim olmaları yoluyla tanışma şansı yakaladık. Değerli Hacer Foggo, Ceren Gökçen ve Elif Göçmen, Derin Yoksulluk Ağı’nı temsilen, COVID-19 sonrası süreç ile birlikte yürütmeye çalıştıkları destek süreçleri ile alakalı ne gibi zorlukların ortaya çıktığı noktasında aydınlatarak, sürecin sıkıntılı noktalarına değindiler.</p><h3>Momentum</h3><p>Takım olarak Derin Yoksulluk Ağı’nı dinleyip, süreçteki çözülebilir problemleri anlamaya çalıştığımız bu süreçte, aklımızda iki farklı çözüm önerisi oluştu. Bir tanesi daha uzun vadeli ve daha geniş kapsama sahip olması yönündeyken, Hackathon kapsamında ilk olarak MVP olarak gördüğümüz modeli geliştirmeye çalıştık.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-BVQ2Vnmu0jFjk23s8w7VQ.png" /></figure><p>Konunun hassasiyeti ve aynı zamanda kişisel verilerin korunması noktasındaki kısıtlamalar ve kaygılar ile birlikte ilk aşamada, destek olmak isteyen kişilerin Derin Yoksulluk Ağı ile iletişime geçip bir destek talebi oluşturabileceği ve destekleyebileceği haneleri, aynı zamanda da bu hanelerin ihtiyacı çerçevesinde oluşturulan ilgili destek paketlerini görüntüleyebilecekleri bir dijital kurgu üzerine yöneldik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIZ1INi02KzIYoL1oJiKTA.png" /></figure><p>Frontend tarafında ReactJS ve TypeScript, Backend’te API ve Mail Microservice için Golang, Database’de MongoDB Atlas, Conteinarization’da Docker, CI/CD ve Cloud tarafında ise AWS EC2, Netlify ve GitHub Actions kullandık.</p><p>Aynı zamanda demo gününde jürilere sunumun İngilizce yapılacak olması sebebiyle de çözüm önerimize hem Türkçe hem de İngilizce görüntülenebilir olabilmesi için dil desteği ekledik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zbc2ErCL0wIWzRhaaPF-Fg.png" /></figure><h3>Demo Günü &amp; Sonuçlar</h3><p>Yaptığımız sunum ve çözüm önerisi ile beş farklı jüri üyesinin puanlama yapmasının ardından, hackathonda <strong>birinci olarak seçildik</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PrxdZES-PgqWNvXlmFQS6A.png" /></figure><p>Bu süreçte, bilgi paylaşımlarıyla süreci aydınlatma noktasındaki katkıları, bize olan inançları ve her şeyden önce böylesine güzel bir gönüllük insiyatifi alıp, bizlere de küçük olsa bir parçası olabilme şansı tanıdıkları için öncelikle Derin Yoksulluk Ağı’ndan <strong>Hacer Foggo</strong>, <strong>Ceren Gökçen</strong> ve <strong>Elif Göçmen</strong>’e; çözüm önerisinin oluşması ve gerçekleştirilmesinde çok değerli emekleri olan takım arkadaşlarım <a href="https://www.linkedin.com/in/orhangazidizdaroglu/"><strong>Orhan Gazi Dizdaroğlu</strong></a>, <a href="https://www.linkedin.com/in/zisanozdemir/"><strong>Zişan Özdemir</strong></a>, <a href="https://www.linkedin.com/in/fatihfurkanhas/"><strong>Fatih Furkan Has</strong></a> ve <a href="https://www.linkedin.com/in/ceren-haydaro%C4%9Flu-816b54182/"><strong>Ceren Haydaroğlu</strong></a>’na; bu tanışıklıkları mümkün kılan organizasyonun gerçekleştirilmesini sağlayan <strong>Re:Coded</strong>, <strong>GIZ</strong> ve <strong>Impact Hub İstanbul ekibi</strong>ne, yaptıkları değerlendirmeler sonucunda, hackathonda aldığımız bu birincilik sonucunu bize uygun gören değerli jüri üyelerinden <strong>Semih Boyacı</strong>, <strong>Mısra Turp</strong>, <strong>Jaime Mikush</strong>, <strong>Cüneyt Kalpakoğlu</strong> ve <strong>Okan Tübek</strong>’e ve değerli emekleri için, bu yolculukta beraber çözüm üretmeye çalıştığımız katılan tüm takımlara ve üyelerine, bu deneyim için teşekkür ediyorum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cg1Q0d6SGEqH6q1jhANLLA.png" /></figure><p><a href="https://www.instagram.com/p/CHQRjhmggfO/">https://www.instagram.com/p/CHQRjhmggfO/</a></p><p><em>Aynı zamanda Derin Yoksulluk Ağı ile iletişimde kalmaya devam ediyoruz ve ilerleyen günlerde de farklı özelliklerin eklenerek, sistemin gerçekten gündelik yaşamda kullanılabilmesi için ne gibi aksiyonlar alabiliriz, bunlar üzerinde plan ve değerlendirmeler yapıyor olacağız.</em></p><p><em>Yakın zamanda tekrar görüşebilmek ve konu ile ilgili güncellemeler verebilmek dileği ile.</em></p><p><em>Sağlıklı günler.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad93b2757fcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>