<?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 Edwige Fiaclou on Medium]]></title>
        <description><![CDATA[Stories by Edwige Fiaclou on Medium]]></description>
        <link>https://medium.com/@edwige.fiaclou?source=rss-eca6a4632a5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rT8G9cZbaf_0Wyw1TgNIaw.jpeg</url>
            <title>Stories by Edwige Fiaclou on Medium</title>
            <link>https://medium.com/@edwige.fiaclou?source=rss-eca6a4632a5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:56:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edwige.fiaclou/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[Setting the Foundation for Talent Development: Five actions]]></title>
            <link>https://medium.com/@edwige.fiaclou/setting-the-foundation-for-talent-development-five-actions-526dbe737778?source=rss-eca6a4632a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/526dbe737778</guid>
            <dc:creator><![CDATA[Edwige Fiaclou]]></dc:creator>
            <pubDate>Mon, 20 Nov 2023 17:58:21 GMT</pubDate>
            <atom:updated>2023-11-20T17:58:21.463Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5O0K31OTKtnc098BOKixYw.png" /><figcaption>Talent foundation</figcaption></figure><h3>Extract from my DevTalks Bucharest 2023!</h3><p>This article offers a transcription of my DevTalks presentation for the LeadDev Track in Bucharest from 2023. <em>In this article, you could find the fifth concrete action to cultivate an inspiring talent-focused Culture as a Senior Leader. Just a hint: “To foster” is the keyword!</em></p><p>Before diving into this article, I want to share that my analysis is drawn from my experience as a <strong>Senior Software Engineering Manager</strong> within my current company, <strong>Swissquote</strong>. My focus has been on understanding the software engineering landscape to create the most creative, supportive and healthy environment for them.</p><p>During my DevTalk, I began my introduction with two questions: “<strong>Who is or was the best leader you have ever worked with?</strong>” And, if you have one in mind, “<strong>Can you list at least one or two qualities of that person?</strong>”</p><p>When I think about what makes a great leader, my mind instantly goes to an incredible manager I had as a tech lead. This person was a simple and perfect combination of support and accountability. His constant belief in me encouraged me to grow and flourish professionally. He knew how to back me up during tough times and pushed me to expand my abilities. In my career journey, he was the starting point and the force that propelled me forward. I sincerely wish for everyone to encounter someone like him — a mentor who gives just the right feedback and becomes a trusted ally in their professional path.</p><p>To draw a final comparison, particularly for those familiar with the iconic game World of Warcraft: In collaborative gaming, the main goal is to create the best guild by combining the required talents and skills, specific to your roles and characters. For instance, if you’re an elf with the ability to fly, is it vital to excel in hand-to-hand combat?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/0*OFq9lq-VExPiEGi0.png" /><figcaption><a href="https://blizzardwatch.com/2017/11/13/class-utility-changes-battle-azeroth-pose-hurdle-wows-class-devs/">Class utility changes in Battle for Azeroth pose a hurdle for WoW’s class devs</a></figcaption></figure><p>This concept mirrors the essence of personal growth, much like my manager’s role in my life. It’s about having the proper support and skills at the pivotal moments, enabling you to reach your full potential.</p><p>Now let me present you my five actions that my current company and I are driving to foster a Talent-Focus organisation within Software Engineering.</p><h3>Action #1 — Foster culture of collaboration</h3><p>Let’s dive into the practical aspects of fostering a talent-focused culture. The first essential step is to nurture a collaborative environment.</p><p>Daniel Goleman, a well-known author and psychologist, has thoroughly researched professional interactions. His theories have significantly influenced various concepts and frameworks that are widely embraced in the development sector, including SCRUM, AGILE, Disciplined Agile, and PMP.</p><p>In his book <strong>“Primal Leadership,” </strong>Daniel Goleman points out that a substantial portion, approximately <strong>80%-90%, of the skills that set top performers from the other are in the domain of Emotional Intelligence (EI)</strong>. For a leader, the key challenge is to identify and cultivate this EI in their team members, thus enhancing their potential and contribution.</p><p>Daniel Goleman also introduced a matrix that facilitates in the awareness and understanding of emotional intelligence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*cjIfS7qpdW0-9KRH.png" /></figure><p>This framework emphasises understanding two key dimensions: self and others. Building on top of this concept, I have created a mapping tool to boost collaboration and develop inter-personal skills, a vital component in nurturing a talent-focused culture based on Mentor and Mentee development. Mentorship involves sponsorship and coaching aimed at achieving specific goals.</p><p>Mentorship focuses on:</p><ul><li><strong>Empowering autonomy</strong> and <strong>decision-making</strong></li><li><strong>Recognizing </strong>and valuing contributions</li><li><strong>Empathizing</strong> with others</li><li>Developing <strong>self-awareness</strong> about personal emotions</li><li><strong>Enhancing growth</strong> through attentive listening for better self-management and skill development.</li></ul><p>Coaching, on the other hand, is about being a knowledgeable reference and recognized expert. Coaching involves being a resourceful expert by:</p><ul><li>Offering guidance and advice</li><li>Motivating and inspiring others</li><li>Providing support</li><li>Developing social awareness through careful listening</li><li>Building stronger social relationships and interactions.</li></ul><p>By focusing on these elements, individuals can develop both self-awareness and social awareness, which are essential for effective leadership and team dynamics.</p><p>I’d like to share an example of a mentorship program that I developed at Swissquote, named the “Buddy Program.” This program operates on a volunteer basis, allowing individuals to assume the role of a mentor. But what does this involve?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*KaoFow9D0N4-pOG7uk7grg.jpeg" /><figcaption>Tech Talent Academy @ Swissquote Bank — The Buddy Program for new joiner</figcaption></figure><p>Primarily, it includes supporting, training, and guiding new employees through their onboarding process. We take special care in pairing each mentees/new joiners with mentors, ensuring that the duo, or ‘binome,’ is well-matched and complementary.</p><p>Additionally, it’s crucial to acknowledge and reward both members of these pairs — mentors and mentees alike — upon reaching specific milestones or goals. This practice not only fosters a sense of accomplishment but also promotes the development of both social and self-awareness within the workplace. The Buddy Program is more than just a mentoring scheme; it’s a catalyst for personal and professional growth within our company culture.</p><blockquote><strong>Conclusion#1:</strong> To effectively foster talent development, it’s important to cultivate Emotional Intelligence and deliberately encourage collaboration among employees with diverse profiles, backgrounds, and cultures.</blockquote><h3>Action #2 — Fostering Learning and Growth Opportunities</h3><p>I came across a LinkedIn report from May 2023, which sheds light on why employees tend to leave their jobs when learning opportunities dry up. This lack of growth makes them feel obsolete in a competitive market and stuck in a comfort zone, resulting in stagnation. <strong>The report indicates that 93% of organizations are significantly concerned about retaining</strong> their employees, emphasizing the importance of offering ongoing learning opportunities in the workplace to maintain employee engagement and competence in a rapidly changing professional environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*g7RVMm5t-FeYB8bi0DJKJQ.png" /><figcaption>Source:LinkedIn-Learning_Workplace-Learning-Report-2023-EN.pdf</figcaption></figure><p>Cultivating a learning culture is crucial for both organizational and personal growth. Being regularly engaged in learning enhances resilience and adaptability to change. A focus on continuous training promotes both personal and professional development and attracts talented individuals, creating a cycle where engaged learners contribute to new ideas and drive innovation.</p><p>At Swissquote, we’ve implemented a knowledge database as a fundamental strategy to support new hires and to visually represent our shared knowledge. Additionally, we promote learning by establishing communities where individuals can discuss and share ideas on topics of interest. These communities not only foster growth but also encourage the development of innovative ideas, particularly in side projects.</p><blockquote><strong>Conclusion #2:</strong> To nurture a learning culture, utilizing tools and initiatives like learning resources and platforms, communities, lunch talk, sharing knowledge sessions, workshops, and hackathons is beneficial.</blockquote><blockquote>Equally important are continuous feedback and leading by example. These are crucial skills that you, as a Senior Leader, need to develop and demonstrate.</blockquote><h3>Action #3 — Foster a Supportive and Inclusive Environment</h3><p>This particular point is one that Senior Leadership uniquely enables.</p><p>It’s about influencing how you are perceived and the personal goals you set. A fitting illustration of this is found in “The Internship,” a comedy film depicting two middle-aged men applying for internships at Google after losing their jobs. Surrounded by younger, tech-savvy interns, they initially struggle but soon contribute valuable insights and experiences, highlighting the importance of diverse perspectives in fulfilling a shared mission. The movie demonstrates that through determination and adaptability, individuals of any age or background can align with and contribute to an organization’s objectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/0*gNI-mbCfheoPfJix.jpg" /><figcaption>The internship movie (<a href="https://www.imdb.com/title/tt2234155/">https://www.imdb.com/title/tt2234155/</a>)</figcaption></figure><p>The film emphasizes the value of adaptability and how diverse experiences can enrich a team’s perspective. By the way, Billy and Nick from Internship movie, despite being the oldest interns and initially struggling to adapt to the high-tech environment, bring unique insights that ultimately prove invaluable. The film concludes with Billy and Nick being offered jobs at Google, celebrating their unlikely but triumphant journey in the tech world and they win the competition.</p><blockquote><strong>Conclusion#3:</strong> As a senior leader agrees with the fact that diversity and inclusion are key benefits to increase competencies of everyone. This approach fosters an environment where individuals feel inspired to both face challenges and offer new ones, leading to a deeper, more thoughtful engagement with the myriad dimensions that shape our world and impact organizations. This understanding cultivates a more empathetic and comprehensive perspective, essential for personal and professional growth.</blockquote><h3>Action#4 — Foster recognition and reward achievements</h3><p>Recognition involves acknowledging and appreciating an employee’s contributions to the team or organization. It can be either formal or informal and may come from managers, peers, or customers. Recognized employees tend to be more engaged and motivated in their work.</p><p>In the article “Power of Recognition” from Ernst &amp; Young, a well-known accounting and auditing firm, the three authors (Martha Cook, Katherine Savage, Kim Billeter, and LaKeng Tan) demonstrate that companies are now attracting talent with more than just salary offerings. It appears that salary is not the primary driver of employee development. They emphasize the significance of aligning employee and company expectations and illustrate this concept with an insightful table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NpinSIgckYVX1Fa5.jpg" /><figcaption>Source: Recognition and Reward advisory (<a href="https://www.ey.com/en_ch/workforce/recognition-reward-advisory">https://www.ey.com/en_ch/workforce/recognition-reward-advisory</a>)</figcaption></figure><p>Senior leaders ought to consistently acknowledge their team members’ achievements, emphasizing each person’s unique contributions to the organization’s objectives.</p><blockquote><strong>Conclusion#4:</strong> By offering meaningful recognition and rewards, senior leaders motivate their employees to continue excelling in their respective talents.</blockquote><p>The final point also described in this article is: Employee Choice and Personalization. This involves providing a framework that empowers each employee to select total reward elements that best suit their needs and current situation each year. It leads me to the concluding point.</p><h3>Action#5 — Lead by mission, the most important one!</h3><p>This point is the one that can be enabled only by Senior Leadership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*5f9imuojxFtE_qtU.jpg" /></figure><p>To emphasize and build on what was described in the previous paragraph, the Technical Career Path is an important tool for recognition. It highlights the impact of your talent internally through expertise and level of impact and can also be aligned with the impact external to the company. Many companies, especially in the Tech World, commonly reference their career paths on platforms like <a href="https://www.levels.fyi/">https://level.fyi</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43TUuQOCRPgoAjOVGCh7Bg.png" /><figcaption><a href="https://www.levels.fyi/?compare=Accenture,IBM,UBS,Amazon,Google&amp;track=Software%20Engineer">https://www.levels.fyi/?compare=Accenture,IBM,UBS,Amazon,Google&amp;track=Software%20Engineer</a></figcaption></figure><p>Establishing goals is a method for identifying and rewarding talent, being mindful of performance, and ensuring transparency in set objectives. It also empowers individuals, fostering autonomy within the team.</p><p>This approach supports and aligns with the culture of your team and company. The aim is to provide employees with a clear path that considers equity and transparency in both the process and evaluation.</p><p>This aspect, influenced solely by Senior Leadership, shapes how others view you and the goals you establish for yourself.</p><p>Don’t underestimate the importance of mission and goals.</p><h3>Key takeaways</h3><p>#1 — <strong>Fostering a culture of collaboration</strong> with coaching and mentorship programs.</p><p>#2 — <strong>Fostering a learning</strong> culture by building a knowledge base with them. Communities and learning centers are key ingredients.</p><p>#3 —<strong> Creating a diverse and inclusive environment</strong> for people to foster challenges and an open mindset. This can be done through project initiatives, gathering feedback and insights from diverse backgrounds and cultures.</p><p>#4 — <strong>Rewarding excellence</strong> with good <strong>intentions </strong>to celebrate and highlight the importance of the work done.</p><p>#5 — <strong>Promoting a clear career path</strong>, to consistently align company needs with employee perspectives.</p><p>In conclusion, cultivating an inspiring talent-focused culture for senior leaders requires a combination of vision, communication, support, and appreciation. When senior leaders actively invest in creating such a culture, they not only empower their employees but also foster a dynamic environment where talent can flourish and innovate.</p><p>The reminder of my motto: ‘It is not with one tree that you make a forest!’ And it is the vastness of forests that makes them interesting to explore, isnt’it ?😉!”</p><p>#culture #worplace #inclusion #diversity #professional_development #safety_place #empowerment</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=526dbe737778" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Production issues: the owl effect]]></title>
            <link>https://medium.com/@edwige.fiaclou/production-issues-the-owl-effect-8b721819dc40?source=rss-eca6a4632a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b721819dc40</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[team-building-ideas]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[incident-management]]></category>
            <dc:creator><![CDATA[Edwige Fiaclou]]></dc:creator>
            <pubDate>Mon, 13 Sep 2021 20:45:54 GMT</pubDate>
            <atom:updated>2021-09-13T20:45:54.739Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e71WeZl062JpjjSB96cv0g.png" /></figure><p><strong><em>As a Manager and Software Engineer with over 10 years of experience, I have seen numerous problematic and complex issues during production. However, legacy systems are no different than others when it comes to identifying a problem.</em></strong></p><p>The complexity of legacy and system, this is the driver enabling my team and me to better manage production outages. Over the years, I have grown my mindset from a constant state of emergency management to a well-oiled outage prediction machine. From implementing monitoring probes before developing fancy features to having a recovery application to take on after prod issues. The sum of my experiences have proven useful to date, and today, I would like to share a few with you.</p><p><strong><em>Let us start with a few existential questions; Can we really be an expert? Are we fully aware of all the hidden blocks in our system?</em></strong></p><p>As an engineer, your main goal is to design, develop and deliver on projects that your clients and/or company desires. Your ideal state is to build a system that functions flawlessly. It is a path to value creation, new functionality development and deployment, and, of course, also a way to justify your salary!</p><h3>A — On the road to a good mindset</h3><p><em>(Careful! The following paragraph can bring back bad memories to the most sensitive developer or support people.)</em></p><p>Do you remember that time when your system crashed? Or maybe, that other time, when the bug <em>unknown-unknown</em> happened? Yes, you read that correctly: <strong>UNKNOWN</strong>. Let me share with you several feelings that some of us have already experienced.</p><p>The first feeling you felt was <strong>STRESS</strong>, followed, maybe, by <strong>FEAR</strong>! Numerous questions then instantly popped into your head:</p><p><strong><em>What are the impacts? Stakeholders/Clients — will they be unhappy? What will be lost? But how could it happen? Why have I not detected this before? How much is the company losing? Let’s check the logs! Look at the monitoring board! Dang, there’s nothing there!</em></strong></p><p>Imagine that your system is like a car. When you look at the car bumper below, do you see anything out of place?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*CLyzIPayTZ78UwvyRtxNqA.gif" /><figcaption><em>tip: Did you notice the OWL? </em>😉</figcaption></figure><p>The owl hidden in the car’s grill above is just like a small bug hidden in your system.</p><p>The irony of this kind of a situation is that you cannot anticipate what you do not know. This exactly portrays my initial feelings when a crash happens. Despite all the tests, all the validations, and checks that were completed we did not detect the small bugs…</p><blockquote><em>“The problem with experts is that they do not know what they do not know!”</em></blockquote><p>Nassim Nicholas Taleb, The Black Swan: The Impact of the Highly Improbable</p><p>Keep calm, it is impossible to imagine something that you have never heard of before. When you created your system, you got that false sense of confidence — that you were becoming an expert. You believed that your application was under control. On top of that, you were sure that no bugs could happen, nothing in your mind was able to disturb the logic of your code!</p><p>The first step is to admit that we are not the expert we think we are, and the second is to build an incredible system to manage our mistakes. The waterfall failure effect that happens in micro services oriented systems actually can be prevented. So how do we get to this ideal state you may be asking yourself; by creating a fully revved up, kitted out, incredibly robust recovery mode system that will drive us right back to normality!</p><h3>B — How to scale your application?</h3><p><strong><em>How do we eliminate the blind spots? What do we need to do to recover 20/20 vision?</em></strong></p><p>In literature, writers work with blindspot matrices, and surprisingly, this methodology can also be applied to software development.</p><p>Our natural mindset is always focused on the comfort zone:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*_wwajmBT-a99pJhN2a640w.jpeg" /><figcaption>Blindspot Matrix (to orient strategics perspectives)</figcaption></figure><p>Our goal, however, was to push out of our comfort zone and into the uncertainty in order to manage these blindspots via other known skills. See the matrix above for visualisation.</p><ul><li><strong>Known weaknesses:</strong> help in the creation of a system with minimal client input requirements and no required understanding of application logs</li><li><strong>Known strengths:</strong> help create strong systems with minimal required metrics</li><li><strong>Unknown strengths:</strong> help to construct part of the uncertainty areas and definitely provide an indicator on what we do not know</li></ul><p>The Blindspot matrix pushed me to deeper analyze my needs and to shift my mindset towards prediction.</p><p>Based on the latest talk given by <em>Pierre Vincent</em> from Weareglofox, we learned that to anticipate the red blindspot zone from the above matrix, the following <strong><em>Three pillars of Observability</em></strong> may prove useful:</p><ul><li><strong>Metrics:</strong> Grafana board, Prometheus, JMX; all these tools help you monitor the overall health of a system, and the aggregation of these metrics will provide you with the events that generated trouble or issues</li><li><strong>Traces:</strong> CorrelationId for end-to-end overview</li><li><strong>Logs:</strong> to better understand the process and story in your system</li></ul><p>Below is what I used as a developer to introduce more resilience and possible exploration points:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SnZbioIwHuh8jhwYxyLKg.jpeg" /><figcaption>Mandatory logs to understand what’s happening!</figcaption></figure><p>Based on the above workflow we were able to identify the issues. This greatly helped my operations colleagues and based upon this information they quickly knew how to proceed. In case of outage or issue in your system, what is your first reflex?</p><ol><li>Rollback</li><li>Reduce the load</li><li>Act on the load balancing</li><li>Check the logs</li><li>Communicate and explain the issue to the stakeholders</li><li>Attempt to reproduce the issue on your own (when it is possible obviously), but this may increase stress if the issues is confirmed</li></ol><p>There are many books that cover observability patterns, and they can precisely explain how to implement the best pattern in your system to predict or prevent issues. Now that the cat is out of the bag on the issue(s), we need to get our system back to normal.</p><p>Time is scarce. You have to prioritize which metrics, safety mechanisms, and dashboards you should implement first. My teammates and I learned valuable lessons post-chaos; all consequences need managing. While metrics are useful in a system, a recovery system is vital.</p><p>In the next section, let us review the key takeaways from my experiences.</p><h3>C — Main lessons learned</h3><p><strong>Lesson #1</strong> | As a developer, I want to be able to explain to my stakeholder what happened with precision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*bzC6JKjtnUuAVSR2k_YsDw.jpeg" /><figcaption><a href="https://www.monkeyuser.com/2018/final-patch/">https://www.monkeyuser.com/2018/final-patch/</a></figcaption></figure><p>After recovering our systems, we need to know how to recover the core business (transactions, appointments, orders, articles, etc.) and guarantee that during the blackout nothing was lost.</p><p>Thus, we implemented our own creation, lovingly called, the Workflow re-processor. Such a big name, sounds like a steamroller, it is not, but it really saved our lives and sanity!</p><p><strong><em>So, how did we build it?</em></strong></p><p>We achieved our build by simply understanding every step, every detail, every nook and cranny of our workflow, and how our system was orchestrated. At every step of this system, we identified the essentials needed in order to keep the system efficient. These essentials included but were not limited to the caching system, database, buffer, memory….</p><p>At some point, depending on the legacy items you are managing, you will have to take the strategic decision between monitoring or debugging. This means that you have the choice between analyzing all metrics on your wonderful dashboard which will point you to the specific point of failure, or you could try to reproduce the issue step-by-step in a SAFE environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6majML2w785vgE4V1CXOuw.jpeg" /><figcaption>to monitor or to debug that is the question?</figcaption></figure><p><strong>Lesson #2</strong> | As a developer and third level support, I should be able to have a proper state at each stage of my workflow.</p><p>This lesson taught me that we need to be able to extract each stage of our core business from our workflow. This enables us to understand what each part is in charge of, and truly follow the process behind the scenes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BapV-xJbNic0i66Mv5UEbQ.jpeg" /><figcaption>Example of module interaction with caching and persistencies combined</figcaption></figure><p>In the above example, you can see that each component is independent. Unfortunately, in case of an outage, the communication between two system components is not automatically saved in memory. Hence, we needed to find a way to resend messages between components. We decided to use Redis as a caching system in addition to a database persistence layer. This enables us to restore the core business orders after an outage.</p><p>In our case, consequently, all messages are saved and cached between each component and can be replayed at each step to guarantee the reprocessing in case of an error. You are probably asking yourself right now: “Is it possible that a component reprocesses a message?” Each component is idempotent to be sure that a single message cannot be processed several times.</p><p><strong><em>What are the benefits of this architecture?</em></strong></p><ul><li>The caching system contributes to the save process in progress. We always have a “clear” status before continuing the workflow</li><li>All messages, regardless of status, are displayed in the web application. We can then reprocess a message as we want it at any stage of the workflow</li><li>Keep the technology simple, no huge name like Kafka…</li></ul><p>Through this workflow, we guarantee that every message can be reprocessed in the workflow as if it were the first input.</p><p><strong>Lesson #3</strong> |Observability is not only mandatory but should be introduced at the beginning of each artifact created in any Distributed System.</p><p><strong><em>Perspective reinvented?</em></strong></p><p>It has been my experience that it is always preferable to prevent and predict when a system will become unstable rather than frantically managing through the chaos of a breakdown!</p><p>I like to allude that my experiences as a software engineer run in parallel to that of my peers in the medical sciences. Both sciences deal with a complex mass of interacting components where symptoms are difficult to diagnose and there is no one size fits all diagnostic. <em>It is simply not always obvious what is a hiccup in a body or a system and what is a full blown disaster.</em></p><p>Now that we have introduced a way to manage a hiccup; what<em> </em>about a solution to prevent a disaster?</p><p>In disaster prevention, always manage events through a variety of diagnostics in order to reinforce your system’s predictability:</p><ul><li>Aggregation of events provides us the correct metrics to initialize</li><li>Correlation of events can improve the traceability and highlight the workflow from producer to consumer</li><li>Indexation of events in the logs can show you the full picture</li></ul><p>Remember, when you “inherit” a legacy code ask yourself this question: <em>How do I apply the above observability examples to prevent any un-monitored outages in this new system?</em></p><p>I hope this article serves as a guide to help you avoid chaotic messes and common big system mistakes.</p><p><strong>May the force of observability be with you!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b721819dc40" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>