RunWhen is a platform for troubleshooting complex tech stacks. It helps engineers identify when issues they are chasing lie in their app, their cloud-native platform or their vendors by answering the question: “What do I run and when?” With a few minutes of training, the platform scans cloud-native clusters and combines the results with community know-how and the power of generative AI to build Digital Assistants that help app developers and new engineers navigate health metrics and troubleshooting commands before escalating to service owners. With a Stack Overflow style prompt for guidance, it can suggest and run hundreds of commands across a platform and applications. Digital Assistants find issues worthy of deeper attention, building a path forward that the teams involved can review and adjust along the way. With RunWhen, application developers and platform engineers can move quickly from problem identification to problem resolution. Visit runwhen.com/beta to find out more and to sign up for our beta! Don't forget to follow us on Youtube for demos: youtube.com/@whatdoirunwhen

RunWhen

FastAPI Got Me an OpenAPI Spec Really... Fast

ফাস্টএপিআই আমাকে একটি ওপেনএপিআই স্পেক দিয়েছে... দ্রুত

FastAPI hat mir wirklich ... schnell eine OpenAPI-Spezifikation besorgt

FastAPI me consiguió una especificación OpenAPI realmente... rápido

FastAPI m'a offert une spécification OpenAPI vraiment... Rapide

FastAPI ने मुझे एक OpenAPI विनिर्देशन वास्तव में... तेजी से दिलाया

FastAPI で OpenAPI 仕様を本当に早く入手できました

FastAPI를 통해 OpenAPI 사양이 정말... 빨라졌습니다.

FastAPI me deu uma especificação OpenAPI muito... rápida

FastAPI дал мне спецификацию OpenAPI действительно... быстро

FastAPI Bana Gerçekten Bir OpenAPI Özelliği Sağladı... Hızlı

FastAPI đã cung cấp cho tôi thông số OpenAPI thực sự... Nhanh

FastAPI 让我快速获得了 OpenAPI 规范

You think that being stuck is a permanent state, and this is the pattern you go through every time: You encounter a new challenge.
Your brain resists it.
It hasn’t been trained to handle discomfort effectively.
You revert to what’s comfortable and familiar.
You shut yourself off from potential growth and enlightenment.
You feel stuck, unfulfilled and unhappy. When you face the challenge of feeling stagnant in your career, in your personal life, nothing seems to help you progress. You feel not just stuck, but regressing. The worst part of it was that in some strange way, it also feels “comfortable” being stuck. I’m sure you have that feeling, because we are wired the same way, and so do I. I wanted to understand why we are so resistant to change, to discomfort. Why is it that it’s easier for us to stay in situations we don’t like while we know damn well it’s not the right path. Why is change hard? Why makes hard things hard? Well, I got some answers while reading a research paper from computational neurobiologist Andrew Gallimore. I finally got a better understanding of how our brain constructs reality, how it cheats us by wanting to save energy, and how we can hack it. 1. Understanding Our Brain: A Reality-Building Machine I won’t bore you with the very technical research paper filled with complicated words and never ending sentences. Here’s a breakdown for you: Central to this process are the cortical columns, functional units within the cerebral cortex that orchestrate your perception of the world. These columns evaluate sensory information against your brain’s existing models, determining “True” or “False” signals to guide your reactions and beliefs. To put this even simpler, They work like little decision-makers in the outer layer of the brain, sorting through what we see and feel. They check this information against what the brain already knows, deciding if it matches (“True”) or doesn’t match (“False”). This helps you figure out how to react and what to believe. Here’s the problem: Your brain and its cortical columns are designed to conserve energy at all costs. This means they’re constantly seeking “True” statements, those that align with what you already know and believe. Why? Because processing familiar information requires less energy than assimilating new data. This is precisely why staying in your comfort zones feels so… comfortable. It’s not just inertia; it’s a battle against a highly efficient computer in your head, always seeking stability over the chaos of change. Your gut might scream for a shift, but you’re up against your brain’s design, which chooses energy conservation over everything else. 2. The Mannequin Misidentification: A Cortex in Action Ok ben, that sounds cool and I get the theory. But how does this actualise, and how is it shaping my reality? Here’s an example: Imagine walking down a street, your eyes catch what appears to be a figure standing in a shop window. Your brain utilizes past data, and quickly categorizes this figure as a man — a “True” response rooted in familiarity. You continue to walk closer, until something happens.. you realize that the figure is not a person, but in fact a mannequin. This unexpected twist sends a “False” signal to your brain, specifically to those cortical columns tasked with visual processing. Faced with this new information, your brain recalibrates, updating your reality from a man to a mannequin. 3. Embracing the Science of Uncomfortability So there we have it. The path to growth is through embracing “False” signals — those challenging, unfamiliar experiences that demand our brain to adjust and grow. This process isn’t just about acquiring new information; it’s about fundamentally reshaping our perception and interaction with the world around us. It’s about changing reality; literally asking your cortex to re-evaluate your current reality, and change it. That’s why it feels so hard. That’s why it feels so weirdly good to stay stuck. So, what are some steps to hack this? 4. Recognizing the State of “Brain Automation” Well, first, you need to understand when you’re stuck in “brain automation”. I’m sure you know this feeling very well. You’re in that state when you go through your daily routines without much thought or variation. You wake up, get dressed, get coffee at the same spot, order the same drink. Tasks and activities feel mundane, and you’re not engaged or stimulated by what you’re doing. You are bored. You wake up every morning saying “ok here we go, another day doing the same thing until I get to go to sleep again. Let’s just get through it with as many distractions as possible.” Nothing seems to make you feel alive. You are just in automation mode. Activities that used to hold your attention don’t mean anything anymore. 5. Breaking Through with Challenging Thoughts Now that you recognize the signs of “brain automation,” the next step isn’t just about what you do; it’s about how you think. Changing your actions without changing your thoughts is like repainting your car when it needs a new engine. Sure, it will look good on the outside, it still won’t run though. So do this: Ask why, and don’t judge. “Why” is such a short but powerful question that can almost always be used successively until the truth is met: “I feel stuck in my career? Why? …Because I don’t like what I do. Why? …Because it doesn’t challenge me or align with my values. Why? …Because I settled into a role that was available rather than pursuing what genuinely interests me. Why? …Because I fear the uncertainty of change and the possibility of failure. Why? …Because past experiences have conditioned me to prioritize security over fulfillment. Why? …Because I internalized the belief that success is defined by stability rather than personal satisfaction and growth.” Take this and keep asking the same question. You’ll get to the root of it soon enough. In this instance, your feeling of being stuck is less about the external circumstances and more about internal barriers — fears, beliefs, and assumptions that keep you tethered to the familiar, however unsatisfying it may be. 6. No, but really.. How do I get unstuck? Listen. True transformation begins when you push beyond the boundaries of what you know and where you’re comfortable. The shift needs to happen in your head, but also physically. You need to consciously and repetitively seek out “False” signals and embrace the discomfort they bring. You need to construct a new reality. In plain, simple terms, you need to: do the uncomfortable thing. Here are a few of the things I have had to do last week alone that finally led me to break out of my cycle: I impulssively bought a plane ticket to Panama, to change my enviroment, create some space for me to:
Sit with my feelings for the first time in years, and finally stop supressing them. I cried. Haven’t done that in years.
I had the uncomfortable conversation with my business partner to tell them I no longer have passion for it and am leaving them the decision to continue or quit.
I made the decision to get a therapist and seek help to access past trauma that I’ve burried deep down.
I replied "I don't know" when asked about something I was unsure of, rather than trying to appear confident. I felt stupid that instant, but I actually learned something and ended up having a meaninful conversation.
I forced myself to talk to strangers every single day. Oh, and talking happened to be in Spanish, for which my vocabulary consisted of a total of 40 words or so. These things were uncomfortable. These things were all dreadful for me. They are supposed to be. They are hard, they are counter-intuitive, and they are painful. But if you don’t do them, you are letting your cortex run on auto-pilot, validating a “true” statement that will feel comfortable. Yes, in the immediate short term, it feels better. But you are reinforcing your mind into shaping the wrong reality. Do that long enough, and you will soon be living in a world that is not yours. You’ll have a job you hate, relationships that don’t support you, a deep lack of purpose, numbing yourself to the world around you until you become nothing more than a ghost, aimlessly drifting through a suffocating and meaningless existence. Waking up to it 10 years later will be very painful. So Wake up. Challenge yourself. Engineer your existence and break free. You think that being stuck is a permanent state, and this is the pattern you go through every time: You encounter a new challenge. Your brain resists it. It hasn’t been trained to handle discomfort effectively. You revert to what’s comfortable and familiar. You shut yourself off from potential growth and enlightenment. You feel stuck, unfulfilled and unhappy. You encounter a new challenge. Your brain resists it. It hasn’t been trained to handle discomfort effectively. You revert to what’s comfortable and familiar. You shut yourself off from potential growth and enlightenment. You feel stuck, unfulfilled and unhappy. When you face the challenge of feeling stagnant in your career, in your personal life, nothing seems to help you progress. You feel not just stuck, but regressing. The worst part of it was that in some strange way, it also feels “comfortable” being stuck. I’m sure you have that feeling, because we are wired the same way, and so do I. I wanted to understand why we are so resistant to change, to discomfort. Why is it that it’s easier for us to stay in situations we don’t like while we know damn well it’s not the right path. Why is change hard? Why makes hard things hard? Well, I got some answers while reading a research paper from computational neurobiologist Andrew Gallimore. I finally got a better understanding of how our brain constructs reality, how it cheats us by wanting to save energy, and how we can hack it. 1. Understanding Our Brain: A Reality-Building Machine I won’t bore you with the very technical research paper filled with complicated words and never ending sentences. Here’s a breakdown for you: Central to this process are the cortical columns, functional units within the cerebral cortex that orchestrate your perception of the world. These columns evaluate sensory information against your brain’s existing models, determining “True” or “False” signals to guide your reactions and beliefs. To put this even simpler, They work like little decision-makers in the outer layer of the brain, sorting through what we see and feel. They check this information against what the brain already knows, deciding if it matches (“True”) or doesn’t match (“False”). This helps you figure out how to react and what to believe. Here’s the problem: Your brain and its cortical columns are designed to conserve energy at all costs. This means they’re constantly seeking “True” statements, those that align with what you already know and believe. Why? Because processing familiar information requires less energy than assimilating new data. This is precisely why staying in your comfort zones feels so… comfortable. It’s not just inertia; it’s a battle against a highly efficient computer in your head, always seeking stability over the chaos of change. Your gut might scream for a shift, but you’re up against your brain’s design, which chooses energy conservation over everything else. 2. The Mannequin Misidentification: A Cortex in Action Ok ben, that sounds cool and I get the theory. But how does this actualise, and how is it shaping my reality? Here’s an example: Imagine walking down a street, your eyes catch what appears to be a figure standing in a shop window. Your brain utilizes past data, and quickly categorizes this figure as a man — a “True” response rooted in familiarity. You continue to walk closer, until something happens.. you realize that the figure is not a person, but in fact a mannequin. This unexpected twist sends a “False” signal to your brain, specifically to those cortical columns tasked with visual processing. Faced with this new information, your brain recalibrates, updating your reality from a man to a mannequin. 3. Embracing the Science of Uncomfortability So there we have it. The path to growth is through embracing “False” signals — those challenging, unfamiliar experiences that demand our brain to adjust and grow. This process isn’t just about acquiring new information; it’s about fundamentally reshaping our perception and interaction with the world around us. It’s about changing reality; literally asking your cortex to re-evaluate your current reality, and change it. That’s why it feels so hard. That’s why it feels so weirdly good to stay stuck. So, what are some steps to hack this? 4. Recognizing the State of “Brain Automation” Well, first, you need to understand when you’re stuck in “brain automation”. I’m sure you know this feeling very well. You’re in that state when you go through your daily routines without much thought or variation. You wake up, get dressed, get coffee at the same spot, order the same drink. Tasks and activities feel mundane, and you’re not engaged or stimulated by what you’re doing. You are bored. You wake up every morning saying “ ok here we go, another day doing the same thing until I get to go to sleep again. Let’s just get through it with as many distractions as possible .” ok here we go, another day doing the same thing until I get to go to sleep again. Let’s just get through it with as many distractions as possible Nothing seems to make you feel alive. You are just in automation mode. Activities that used to hold your attention don’t mean anything anymore. 5. Breaking Through with Challenging Thoughts Now that you recognize the signs of “brain automation,” the next step isn’t just about what you do; it’s about how you think. Changing your actions without changing your thoughts is like repainting your car when it needs a new engine. Sure, it will look good on the outside, it still won’t run though. So do this: Ask why, and don’t judge. “Why” is such a short but powerful question that can almost always be used successively until the truth is met: “I feel stuck in my career? Why? “I feel stuck in my career? Why? …Because I don’t like what I do. Why? …Because I don’t like what I do. Why? …Because it doesn’t challenge me or align with my values. Why? …Because it doesn’t challenge me or align with my values. Why? …Because I settled into a role that was available rather than pursuing what genuinely interests me. Why? …Because I settled into a role that was available rather than pursuing what genuinely interests me. Why? …Because I fear the uncertainty of change and the possibility of failure. Why? …Because I fear the uncertainty of change and the possibility of failure. Why? …Because past experiences have conditioned me to prioritize security over fulfillment. Why? …Because past experiences have conditioned me to prioritize security over fulfillment. Why? …Because I internalized the belief that success is defined by stability rather than personal satisfaction and growth.” …Because I internalized the belief that success is defined by stability rather than personal satisfaction and growth.” Take this and keep asking the same question. You’ll get to the root of it soon enough. In this instance, your feeling of being stuck is less about the external circumstances and more about internal barriers — fears, beliefs, and assumptions that keep you tethered to the familiar, however unsatisfying it may be. 6. No, but really.. How do I get unstuck? Listen. True transformation begins when you push beyond the boundaries of what you know and where you’re comfortable. The shift needs to happen in your head, but also physically. You need to consciously and repetitively seek out “False” signals and embrace the discomfort they bring. You need to construct a new reality. In plain, simple terms, you need to: do the uncomfortable thing . do the uncomfortable thing Here are a few of the things I have had to do last week alone that finally led me to break out of my cycle: I impulssively bought a plane ticket to Panama, to change my enviroment, create some space for me to: Sit with my feelings for the first time in years, and finally stop supressing them. I cried. Haven’t done that in years. I had the uncomfortable conversation with my business partner to tell them I no longer have passion for it and am leaving them the decision to continue or quit. I made the decision to get a therapist and seek help to access past trauma that I’ve burried deep down. I replied "I don't know" when asked about something I was unsure of, rather than trying to appear confident. I felt stupid that instant, but I actually learned something and ended up having a meaninful conversation. I forced myself to talk to strangers every single day. Oh, and talking happened to be in Spanish, for which my vocabulary consisted of a total of 40 words or so. I impulssively bought a plane ticket to Panama, to change my enviroment, create some space for me to: Sit with my feelings for the first time in years, and finally stop supressing them. I cried. Haven’t done that in years. I had the uncomfortable conversation with my business partner to tell them I no longer have passion for it and am leaving them the decision to continue or quit. I made the decision to get a therapist and seek help to access past trauma that I’ve burried deep down. I replied "I don't know" when asked about something I was unsure of, rather than trying to appear confident. I felt stupid that instant, but I actually learned something and ended up having a meaninful conversation. I forced myself to talk to strangers every single day. Oh, and talking happened to be in Spanish, for which my vocabulary consisted of a total of 40 words or so. These things were uncomfortable. These things were all dreadful for me. They are supposed to be. They are hard, they are counter-intuitive, and they are painful. But if you don’t do them, you are letting your cortex run on auto-pilot, validating a “true” statement that will feel comfortable. Yes, in the immediate short term, it feels better. But you are reinforcing your mind into shaping the wrong reality . wrong reality wrong reality Do that long enough, and you will soon be living in a world that is not yours. You’ll have a job you hate, relationships that don’t support you, a deep lack of purpose, numbing yourself to the world around you until you become nothing more than a ghost, aimlessly drifting through a suffocating and meaningless existence. Waking up to it 10 years later will be very painful. So Wake up. Challenge yourself. Engineer your existence and break free.

The Illusion of Being Stuck

আটকে থাকার বিভ্রম

Die Illusion, festzustecken

La ilusión de estar estancado

L'illusion d'être coincé

फँस जाने का भ्रम

行き詰まっているという幻想

갇혀 있다는 환상

A ilusão de estar preso

Иллюзия застревания

Sıkışmış Olma Yanılsaması

Ảo tưởng bị mắc kẹt

陷入困境的错觉

It may not have been the cuts that some speculators had hoped for back in Q4, but the news that the US Federal Reserve were set to cut rates three times throughout 2024 helped to push all three major stock indexes towards new record highs following its March meeting. The prospect of rate cuts will be music to the ears of risk-taking investors, with the prospect of greater confidence levels and stronger liquidity helping to drive markets higher. Riding the wave of good news was the Dow Jones Industrial Average, S&P 500, and the Nasdaq Composite, all of which added posted of between 0.2% and 0.7% as the anticipation of upcoming cuts grew. healthy gains Although the Fed opted to keep rates unchanged in March, new forecasts confirmed plans for three 25-basis-point rate cuts in 2024 in a move that improved optimism throughout Wall Street. Federal Reserve Chair Jerome Powell also hinted that rate cuts will take place provided that the US economy continues to grow as expected, and downplayed the impact of the in inflation that took place in January and February. As a result, markets anticipate a of a rate cut arriving by June. unexpected rises 72% chance The largely optimistic note saw Wall Street’s chip stocks perform exceptionally well, with Nvidia (NASDAQ:NVDA) soaring to yet further highs while the positive sentiment dovetailed for Micron Technology’s (NASDAQ:MT) stock which has now shown Q1 growth of 45% following an report. impressive earnings Provided that the Fed’s anticipation of economic growth meets expectations, it’s likely that higher flows of investor optimism will manifest itself in Wall Street’s tech stocks and various riskier plays that would’ve seemed too hot to handle as recently as 2022. So, is it time for the good times to roll once more? Winning the Battle with Inflation Throughout 2022 and 2023, the economic landscape throughout the US was punctuated by a hawkish monetary policy from the Federal Reserve. Soaring inflation prompted by the post-pandemic recovery and supply chain squeezes throughout industries saw inflation peak at 9.1% in June 2022. By late 2023, optimism began to grow that rate hikes may finally be over, and that cuts may be on the way as soon as Q1 2024. However, January and February of the new year brought more concern. Inflation began to rise unexpectedly, causing more investors to fear that expectations over cuts may be short lived. Despite this, Powell highlighted that recent inflation worries were likely down in part to ‘seasonal effects,’ and although the bank would take the available data seriously, it shouldn’t impact its transition into a more dovish stance. "It certainly hasn't raised anyone's confidence; but I would say that the story is really essentially the same, and that is of inflation coming down gradually toward 2% on a sometimes bumpy path," . explained Powell "We've got nine months of 2.5% inflation now. We've had two months of bumpy inflation; it's going to be a bumpy ride." While the anticipation of cuts has seen investor sentiment become more positive on Wall Street, other investors have sought to move quickly in of advantageous interest rates while they’re still available. taking advantage According to fund tracker EPFR, $22.8 billion has flooded into corporate bond funds in 2024 before anticipated rate cuts impacted yields. The data represents the brightest start to a year since 2019. Big Tech Wins Investor Confidence Wall Street’s brightening outlook saw in the wake of the Fed’s March meeting. US stock futures rally Futures for the Dow Jones Industrial Average advanced 30 points, or 0.1%, the S&P 500 gained 0.2%, and the tech-oriented Nasdaq climbed 0.3% moving into the quieter Easter Weekend period for markets as investors began to bet on clearing skies over US stocks. Crucially, this growing interest in the performance of US markets falls in-line with more bullish revisions of where indexes like the S&P 500 is likely to be by the end of the year. Notably, John Stoltzfus, chief investment strategist at Oppenheimer, has raised expectations for the S&P 500 by 5% to a year ending benchmark of 5,500–representing a strong increase on the initial specified target of 5,200. "All of the above prompts us to increase our year-end price target acknowledging the possibility that we might need to raise the target price again later this year should this economic and market outlook prove us too conservative in our projections," . wrote Stoltzfus Even more bullish is the prediction of a team of Goldman Sachs strategists led by David Kostin who suggested that the S&P 500 could be driven to thanks to big tech rallies in one scenario where megacaps foster growth of 15%. 6,000 this year However, the team also highlighted one prospective scenario that could see the index crash to 4,500. The End of Risk? Although markets have become more optimistic off the back of the Federal Reserve’s March meeting, the performance of inflation between now and June will have a major impact on whether investors retain their confidence in Wall Street’s megacap tech stocks. Another confounding factor may be the continued escalation of geopolitical tensions and a prospective tumultuous presidential election in November, which could be intensified should it become a close-run event. There’s also the danger that markets have already long factored in the inevitability of rate cuts, meaning that there may be less distance to run when the hotly anticipated cuts finally occur. “It is important to realise that the market has changed the paradigm from ‘will there be a rate cut?’ to ‘when?’,” , head of investment research at Freedom Finance Europe. explained Maxim Manturov “In other words, the markets have built into expectations a rate cut soon, and even if it comes later, from a fundamental perspective it won't have much of an impact given the solid Q4 gains for much of the S&P 500 index. And even though expectations for a Fed rate cut have been pushed back to a later date, the threat of a rate hike is off the table for now.” While we’re likely to see the positive sentiment flow back into Wall Street as expectations for rate cuts continue to grow, the impact they’ll have on the risky stocks that have helped to facilitate such a strong end to 2023 may have already been priced in. This means that optimism should be balanced with caution in navigating the Fed’s new dovish stance.

Risk Appetite Floods Back Into Wall Street as Rate Cut Confidence Soars for Investors

ঝুঁকির ক্ষুধা বন্যা ওয়াল স্ট্রিটে ফিরে এসেছে কারণ বিনিয়োগকারীদের জন্য রেট কাটের আস্থা বেড়েছে

Die Risikobereitschaft kehrt an die Wall Street zurück, da das Vertrauen der Anleger in Zinssenkungen steigt

El apetito por el riesgo vuelve a inundar Wall Street a medida que aumenta la confianza de los inversores en el recorte de tipos

L’appétit pour le risque revient à Wall Street alors que la confiance des investisseurs en matière de réduction des taux monte en flèche

निवेशकों के लिए दर में कटौती का विश्वास बढ़ने से वॉल स्ट्रीट में जोखिम की भूख फिर से बढ़ गई है

投資家の利下げに対する信頼感が高まる中、リスク選好がウォール街に再び流入

투자자들의 금리 인하 신뢰도가 높아지면서 위험에 대한 욕구가 다시 월스트리트에 몰려들고 있습니다.

O apetite pelo risco volta a Wall Street à medida que aumenta a confiança dos investidores no corte de taxas

Аппетит к риску возвращается на Уолл-стрит, поскольку уверенность инвесторов в снижении ставок растет

Yatırımcılara Faiz İndirimi Güveni Arttıkça Risk İştahı Wall Street'e Yeniden Taşındı

Sự thèm muốn rủi ro tràn trở lại Phố Wall khi niềm tin cắt giảm lãi suất tăng vọt đối với các nhà đầu tư

投资者对降息信心飙升，风险偏好重回华尔街

PS: This story was written in my indigenous language, Pidgin English, a variant of English. I hope you enjoy it. -All misfortune ends up as stories eventually For the longest time, I wanted to run. When you read this, I hope you understand why I did what I did. And you won’t curse me, too. When I was young, I fell in love with various kinds of food. I hated wastage, so I ate whatever I came across, full or not. They called me a glutton and many unflattering names, but my thick hide remained unruffled. Different foods meant the world to me until I found spaghetti. It’s not what you think, no. It’s beguiling and strips you of common sense. The first time I became addicted to spaghetti, the world tilted on its axis. I was floating. Let’s start at the very day my world came unraveled. “Every time carbohydrate. You go dey chop like baby pig, yet e no dey show for your body. Pankere wọ gown.” Mama said when she walked up to me, a laundry basket under her arms with rolls of fat. “Sorry, mama,” I said, slowing down my food. The apartment is tiny and meant to be stuffy, but Mama makes it work somehow. “My pikin, eat o. But eat a balanced diet, eh? I no wan make you get kwashiorkor. E no look good for body. Na so so head and belle remain. You need fat, even if na small. I go buy milk for you when I come back from the market. That milk, wetin dem dey call am again?” Her memory was sometimes glitchy, and I always came to her aid. “Na Complan.” “Ehn ehn, Complan. Na, im be that. You need am make you add flesh for your body.” But what is a twelve-year-old supposed to know about such? Mama goes to do the laundry, and I sit in front of the television, stomach rumbling. “Open the door, person dey knock,” Mama said from the backyard. Her ears are sharper than the talons of a predator on most days. “Nnena, how are you?” A woman in Mama’s size sizes me up, tying her wrapper correctly. “Fine, ma.” I was courteous even though I’d never seen her before. “Your mama no dey?” She asked, trying to peek inside the house. I hold the door firmly, dissuading her from such an act. “She dey backyard,” I responded, not budging an inch. Mama has told me many times not to let strangers in. No matter how they seem. “Okay, I just say make I greet. Before I forget, you fit to give her this? Tell am say na the new product wey come out.” She handed me a sealed product, and my eyes widened when I spotted the name. It was spaghetti. “Who be that?” Mama comes into the room, drying her hands on her wrapper. “I no know o. She just dropped this thing.” I pointed, and Mama’s eyes relaxed. “Ah, na Mama Nedu na. You no know her? She dey sell spaghetti. She say she go drop by.” I heave a breath of relief, staring at the pack of spaghetti, daring me to move forward. I cooked it the next day. Delicious doesn’t even begin to describe it. It finished a little too fast, and I stared disappointed at my empty plate, licked until it shone like the back of Nnamdi’s head. We all laughed when he came to school with a shaved head, and I never forgot ever since. I cooked it again. I was spending the cash I’d been saving for the festivities of Christmas. It finished—all 3,450 naira of it. The withdrawal symptoms started innocently enough when I hallucinated a plate of spaghetti. I reached for it, but it wasn’t there anymore. I hiss at the eba, not knowing what to do. I ate rice that night. And my life changed forever. I could feel a bubbling sensation in my stomach, as though my entrails were being pulled out of my body, acid searing through my stomach’s lining. “Jesus, wetin? Talk to me! My pikin ooo, make una help me o.” Mama rushed me into her arms, cradling my head with such fondness. I could feel my ribs digging into me. “Wetin happen?” Papa Njedika was the first to answer the call, his wife a few feet behind him. “She just begin to convulse. Her body temperature just dey rise. I no know wetin to do. My God oo, make una come o.” And Mama slips into hysteria again. “Make we carry her go hospital; we go figure out the bills later.” Mama nods, letting Papa Njedika remove me from her grasp. I could see the agony create lines on her face. But I was unconscious. Outside my body, watching me. And fear wears me like a sweater. I was dead. ~~ Being dead didn’t feel terrible, until I touched a lone thread. A thread of white and red was before me, and the non-corporeal world filled up my vision. The chairs were in their first form; a tree stood where all the chairs were, and I found myself standing in a forest. Dense. Silent. Alive. The trees encompass the world, stretching forth into eternity. Whichever way I turned, a forest greeted me. The two threads were on the ground, and I knew I couldn’t touch more than one. It was a choice. I was making a choice. I picked the red. Cliché, but it worked. I was carried into the air as though I weighed less than a feather, and I kept rising until I was above the clouds. And the world was before me. I moved, wondering what would happen if I fell from such a stupendous height. Was there a way to die a second death? I didn’t want to find out. My eyesight had no barriers; I could see the entire world simultaneously. “Child of the Stars, what are you doing here?” I heard a voice from the world, and my eyes almost rolled to the back of my head. “I think I died,” I say, turning 360 to see if I could catch a glimpse of the speaker—no such luck. “Yes, but this isn’t your path to follow. Why did you choose this path?” The voice asked again. I’d already gotten over my fear, and I was feeling irritated instead. “Is there meant to be a tutorial or something? Because I didn’t receive one.” The voice chuckled—light and all-encompassing. “Okay, Child of the Stars. Look no further. Remember who you are.” The voice said with a tone of finality and faded out of existence. Curious. After waiting for a few minutes, I got bored and began to touch the trees around me. They felt like they had a soul, as though the world stole their individuality. “What are you trying to tell me?” I whisper, cradling its bark. A purring sound reverberated around me as though waking the world from its slumber. One by one, the trees made groaning sounds, moving as one. “What’s going on?” I screamed, and they turned to me suddenly. “Child of the Stars, you’ve awoken us from our slumber. We have seen what humans have done, and we rise. No longer playthings, no longer useless. Thank you for waking the Soul of the World. Goodbye, we won’t see you again.” The world faded to black, and I opened my eyes groggily, staring at my mother's worried face. “What happened?” I asked, the mother of all headaches deciding to visit me. “My pikin don wake!” Mama screams, hugging me. Papa Njedika and his wife run into the room, looking at me with worry creasing their foreheads. The hospital waiting room seemed to be full of people. People I didn’t even know. “You’re fine now,” Mama said, but I wondered. Three days after I got home, missiles were launched into China and the US, even though there was a non-aggression pact between the World Powers. “The missiles moved like they had a mind of their own.” The president of the US made that statement, looking stupid on live television. But when Switzerland launched a missile, the world began to listen. A neutral country was calling for war. It was darker than people thought. I needed to get back to the non-corporeal world; I needed to right my wrongs. So, I ate spaghetti until I almost passed out. Nothing. I starved myself for days on end, my body worse than it was before. Nothing still. My body was refusing to die. When I dreamt, I saw the Soul of the World standing before me, eyes filled with malice. It was no longer a giant mass of trees; it was a human with eyes as deep as the universe. No, not a figure of speech. The universe was its eyeballs. “Why do you worry, Child of the Stars? They deserve it.” It says, looking down on me with contempt. “But, I’m part of the world too.” I reasoned, but the look it leveled me with was enough to incinerate. “And?” There was no remorse in its voice. “Stop, please,” I beg. “Why should I? You still use plates: books, wood. You take from us and give nothing in return. No homage, no love. You’re human, too. Born in this age, how can you be anything else? Goodbye. We won’t meet again.” “No. We will.” I stared at the Soul of the World, pleading. It smiled briefly and disappeared. “What have I done?” I asked, feeling the weight settle over my soul. “I don’t know, what have you done?” I heard a cheery voice, the same one from before. “How do I fix this?” I scream at the void, my voice not getting past two feet in front of me. “You can’t. This was your purpose all along. I like the bit with spaghetti, though I found it funny. But now, you must wake. Even stars have to face what it means to fall.” The world shattered, and I woke up with tears in my eyes. My mother was beside me, looking older than I’d ever seen her. She had grey hair. “Mama?” I asked, turning around to be sure I was in the right place. Everything looked so unfamiliar. Mama woke up with a start. She saw me and fainted. People rushed into the room, and they ran out when they saw me awake. “What’s happening?” I didn’t know whether to cry or be worried. Papa Njedika was the only person brave enough to talk to me. He approached me and hesitated but placed his hand on my shoulder. “We’re the last of Nigeria. And this is 2025. The Third World War.” It was my turn to faint. But I didn’t. I’d slept for ten years. And the world had ended. All because of spaghetti.

Spaghetti 

scurries onto the database scene as a resilient and scalable distributed SQL database. Drawing inspiration from the tenacity of its insect namesake, CockroachDB boasts high availability even in the face of hardware failures. Its distributed architecture spans multiple nodes, mirroring the adaptability of its insect counterpart. CockroachDB With strong consistency and ACID transaction support, CockroachDB becomes a reliable choice for applications requiring data accuracy and reliability, thriving in dynamic environments and effortlessly managing the complexities of distributed data. This blog introduces using MinIO as a changefeed sink for CockroachDB. By doing so, you not only benefit from CockroachDB's strengths but also leverage the , , and of MinIO. Use this as a guide to establishing an enterprise-grade CDC strategy. It is inspired by awesome repo. durability scalability performance this What is CDC? CDC is a smart database management technique that tracks and captures changes in a relational database like CockroachDB. It acts like a monitor, detecting CRUD Operations like INSERTS, UPDATES and DELETES in real time. CDC's strength lies in its ability to identify only the altered data, making it more efficient in terms of network bandwidth and expense than traditional methods of replication. This efficiency is crucial for tasks like data integration, real-time analytics, and maintaining consistency across distributed systems. CDC is truly a prerequisite for real-time connected data fabrics and remains a fundamental tool for keeping databases synchronized and maintaining reliability in dynamic data environments. This continuous stream of real-time data updates provides a rich foundation for training and optimizing machine learning models which require huge volumes of up-to-date data for success. Changefeed Sinks with CockroachDB in CockroachDB are like data pipelines that efficiently funnel CRUD operations happening in the database to an external destination. In this instance, MinIO serves as one such destination. When configured as a sink, MinIO becomes the repository for the continuous stream of changes, offering a durable and scalable storage solution for CDC operations. Changefeed sinks One benefit of this approach is that you can use CDC data in your MinIO bucket to replicate your data strategy across clouds. For example, If your CockroachDB is hosted in AWS, but you need your data on-prem for your models to run, you can do that with this approach. This can be an effective way to implement a multi-cloud data strategy. Prerequisites To follow this guide, make sure you have Docker Compose installed. You can install Docker Engine and Docker Compose separately or together using Docker Desktop. The easiest way is to go for Docker Desktop. Check if Docker Compose is installed by running this command: docker-compose --version You will need a self-hosted, Enterprise license of CockroachDB. For this local deployment of CockroachDB, please note that CockroachDB on ARM for MacOS is experimental and is not yet ready for production. Getting Started To get started clone or download the project folder from location. this Open a terminal window, navigate to the project folder and run the following command: docker-compose up -d This command instructs Docker Compose to read the configuration from the `docker-compose.yml` file, create and start the services defined in it, and run them in the background, allowing you to use the terminal for other tasks without being tied to the container's console output. After running the command you should be able to see the containers are up and running. You can access the Cockroach UI at . Verify that your node is live. http://127.0.0.1:8080 You can access the MinIO UI at . Log in with the username and password combination of . http://127.0.0.1:9001 minioadmin:minioadmin Once you log in, you should be able to verify that the mc command in the was executed and a bucket named was automatically created. docker-compose.yml cockroach SQL Commands Once your containers are up and running, you’re now ready to run SQL commands. Run the following command in a terminal window in the same folder where you downloaded the tutorial files and started your containers. This command executes an interactive SQL shell inside the container, connecting to the CockroachDB instance running in that container, and allowing you to enter SQL queries. crdb-1 docker exec -it crdb-1 ./cockroach sql --insecure You should see the following if you executed the shell correctly. #
# Welcome to the CockroachDB SQL shell.
# All statements must be terminated by a semicolon.
# To exit, type: \q.
#
# Server version: CockroachDB CCL v19.2.2 (x86_64-unknown-linux-gnu, built 2019/12/11 01:33:43, go1.12.12) (same version as client)
# Cluster ID: 0a668a2d-056d-4203-a996-217ca6169f80
#
# Enter \? for a brief introduction.
# As noted in the prerequisites, you need an Enterprise CockroachDB account to set up CDC. Use the same terminal window to enter the next commands. SET CLUSTER SETTING cluster.organization = '<organization name>';

SET CLUSTER SETTING enterprise.license = '<secret>';

SET CLUSTER SETTING kv.rangefeed.enabled = true; Crushing CDC You can now build your database and tables. The SQL below creates a new database named , switches the current database context to , creates a table named to store information about machine learning models, and inserts two rows of data into this table representing the performance metrics of specific models. Execute these commands in the same terminal. ml_data ml_data model_performance CREATE DATABASE ml_data;

SET DATABASE = ml_data;

CREATE TABLE model_performance (
     model_id INT PRIMARY KEY,
     model_name STRING,
     accuracy FLOAT,
     training_time INT);

INSERT INTO model_performance VALUES
   (1, 'NeuralNetworkV1', 0.85, 120),
   (2, 'RandomForestV2', 0.92, 150); Next, run the following command to create a changefeed for the table in CockroachDB and configure it to stream updates to MinIO. model_performance CREATE CHANGEFEED FOR TABLE model_performance INTO 'experimental-s3://cockroach?AWS_ACCESS_KEY_ID=minioadmin&AWS_SECRET_ACCESS_KEY=minioadmin&AWS_ENDPOINT=http://minio:9000&AWS_REGION=us-east-1' with updated, resolved='10s'; Navigate to the Cockroach UI at to verify that your changefeed has been successfully created and a high-water timestamp has been established. http://127.0.0.1:8080 Make a change to your data to see the changefeed in action. UPDATE model_performance SET model_name = 'ResNet50' WHERE model_id = 1; Run the following command to make sure the command was executed. SELECT * FROM model_performance ;
  model_id |   model_name   | accuracy | training_time  
+----------+----------------+----------+---------------+
         1 | ResNet50       |     0.88 |           130  
         2 | RandomForestV2 |     0.92 |           150 In a production environment, your transactions would populate MinIO without the need for this step. Navigate back to the MinIO UI at‘ to see your changefeed in action. http://127.0.0.1:9001 End of the Line In this tutorial, you’ve gone through the process of creating a changefeed sink with MinIO to enable a CDC strategy for your enterprise-licensed CockroachDB. This CDC strategy sets the stage for a and continuously synchronized data fabric for your most critical data. When you absolutely need to have a perfect replica of your data for data exploration, analytics or AI applications the combination of CockroachDB and MinIO is your winning strategy. resilient Evolve what has been outlined here and you will continue to support better decision-making, facilitating AI/ML endeavors, and maintaining the reliability of your dynamic data environment. MinIO today for all your cockroach-related needs. MinIO - CockroachDBs check-in, but they don't check out. Reach out to us if you have any questions or trouble with bugs at or on . Download hello@min.io Slack I want to thank the folks at CockroachDB – big shoutout to John Billingsley – for helping us with this post.

Never the One to Die: Persistent Data with a CDC MinIO Sink for CockroachDB

If you need to run operations before completing a Git commit, you can rely on Git Hooks. Git hooks are scripts that run automatically whenever a particular event occurs in a Git repository. They let you customize Git’s internal behaviour and trigger customizable actions at key points in the development life cycle. Extending Git hooks allows you to plug in to the regular Git flow, such as Git , , etc. custom functionalities message validation code formatting I’ve already described how to use , but here I’m gonna use , the version of Husky created for .NET-based applications. Husky with NPM Husky.NET Git hooks: a way to extend Git operations As we said, Git hooks are actions that run during specific phases of Git operations. Git hooks fall into : 4 categories : they execute when you run on your local repository; client-side hooks related to the committing workflow git commit : they are executed when running , which is a command that allows you to integrate mails and Git repositories (I’ve never used it. If you are interested in this functionality, ); client-side hooks related to the email workflow git am here’s the official documentation : these hooks run on your local repository when performing operations like ; client-side hooks related to other operations git rebase : they run after a commit is received on the remote repository, and they can reject a operation. server-side hooks git push Let’s focus on the client-side hooks that run when you commit changes using . git commit How to install Husky.NET and its dependencies in a .NET Application Husky.NET must be installed in the of the solution. root folder You first have to by running: create a file in the root folder tool-manifest dotnet new tool-manifest This command creates a file named under the folder: here, you can see the list of external tools used by dotnet. dotnet-tools.json .config After running the command, you will see that the file contains this element: dotnet-tools.json {
  "version": 1,
  "isRoot": true,
  "tools": {}
} Now you can by running: add Husky as a dotnet tool dotnet tool install Husky After running the command, the file will contain something like this: {
  "version": 1,
  "isRoot": true,
  "tools": {
    "husky": {
      "version": "0.6.2",
      "commands": ["husky"]
    }
  }
} Now that we have added it to our dependencies, we can by running: add Husky to an existing .NET application dotnet husky install If you open the root folder, you should be able to see these 3 folders: , which contains the info about the Git repository; .git that contains the description of the tools, such as ; .config dotnet-tools that contains the files we are going to use to define our Git hooks. .husky Finally, you can by running, for example, add a new hook dotnet husky add pre-commit -c "echo 'Hello world!'"
git add .husky/pre-commit This command creates a new file, (without file extension), under the folder. By default, it appears like this: pre-commit .husky #!/bin/sh
. "$(dirname "$0")/_/husky.sh"

## husky task runner examples -------------------
## Note : for local installation use 'dotnet' prefix. e.g. 'dotnet husky'

## run all tasks
#husky run

### run all tasks with group: 'group-name'
#husky run --group group-name

## run task with name: 'task-name'
#husky run --name task-name

## pass hook arguments to task
#husky run --args "$1" "$2"

## or put your custom commands -------------------
#echo 'Husky.Net is awesome!'

echo 'Hello world!' The default content is pretty useless; it’s time to customize that hook. Notice that the latest command has also generated a file; we will use it later. task-runner.json Your first pre-commit hook To customize the script, . open the file located at .husky/pre-commit Here, you can add whatever you want. In the example below, I run commands that compile the code, format the text (using with the rules defined in the .editorconfig file), and then run all the tests. dotnet format #!/bin/sh
. "$(dirname "$0")/_/husky.sh"

echo 'Building code'
dotnet build

echo 'Formatting code'
dotnet format

echo 'Running tests'
dotnet test Then, add it to Git, and you are ready to go. 🚀 But wait… 3 ways to manage dotnet format with Husky.NET There is a problem with the approach in the example above. Let’s simulate a usage flow: you modify a C# class; you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs ; dotnet format the pre-commit hook runs ; dotnet test after the hooks, the commit is created. What is the final result? Since modifies the source files, and given that the snapshot has already been created before executing the hook, all ! dotnet format the modified files will not be part of the final commit Also, executes linting on every file in the solution, not only those that are part of the current snapshot. The operation might then take a lot of time, depending on the size of the repository, and most of the time, it will not update any file (because you’ve already formatted everything in a previous run). dotnet format We have to work out a way to fix this issue. I’ll suggest three approaches. Include all the changes using Git add The first approach is quite simple: after . run git add . dotnet format So, the flow becomes: you modify a C# class; you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs ; dotnet format the pre-commit hook runs ; git add . the pre-commit hook runs ; dotnet test Git creates the commit. This is the most straightforward approach, but it has some downsides: is executed on every file in the solution. The more your project grows, the slower your commits become; dotnet format adds to the current snapshot all the files modified, even those you did not add to this commit on purpose (maybe because you have updated many files and want to create two distinct commits). git add . So, it works, but we can do better. Execute a dry run of dotnet-format You can to the command: this flag returns an error if at least one file needs to be updated because of a formatting rule. add the --verify-no-changes dotnet format Let’s see how the flow changes if one file needs to be formatted. you modify a C# class; you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs ; dotnet format --verify-no-changes the pre-commit hook returns an error and aborts the operation; run on the whole solution to fix all the formatting issues; you dotnet format you run ; git add . you run ; git commit -m "message" the pre-commit hook runs ; dotnet build the pre-commit hook runs . Now, there is nothing to format, and we can proceed; dotnet format --verify-no-changes the pre-commit hook runs ; dotnet test Git creates the commit. Notice that, this way, if there is something to format, the whole commit is aborted. You will then have to run on the entire solution, fix the errors, add the changes to the snapshot, and restart the flow. dotnet format It’s a longer process, but it allows you to have complete control over the formatted files. Also, you won’t risk including in the snapshot the files you want to keep staged in order to add them to a subsequent commit. Run dotnet-format only on the staged files using Husky.NET Task Runner The third approach is the most complex but with the best result. If you recall, during the initialization, Husky added two files in the folder: and . .husky pre-commit task-runner.json The key to this solution is the file. This file allows you to . task-runner.json create custom scripts with a name, a group, the command to be executed, and its related parameters By default, you will see this content: {
  "tasks": [
    {
      "name": "welcome-message-example",
      "command": "bash",
      "args": ["-c", "echo Husky.Net is awesome!"],
      "windows": {
        "command": "cmd",
        "args": ["/c", "echo Husky.Net is awesome!"]
      }
    }
  ]
} To make sure that runs only on the staged files, you must like this: dotnet format create a new task {
  "name": "dotnet-format-staged-files",
  "group": "pre-commit-operations",
  "command": "dotnet",
  "args": ["format", "--include", "${staged}"],
  "include": ["**/*.cs"]
} Here, we have specified a name, , the command to run, , with some parameters listed in the array. Notice that parameter, which is populated by Husky.NET. dotnet-format-staged-files dotnet args we can filter the list of files to be formatted by using the ${staged} We have also added this task to a named that we can use to reference a list of tasks to be executed together. group pre-commit-operations If you want to run a specific task, you can use . In our example, the command would be . dotnet husky run --name taskname dotnet husky run --name dotnet-format-staged-files If you want to run a set of tasks belonging to the same group, you can run . In our example, the command would be . dotnet husky run --group groupname dotnet husky run --group pre-commit-operations The last step is to call these tasks from within our file. So, replace the old command with one of the above commands. pre-commit dotnet format Final result and optimizations of the pre-commit hook Now that everything is in place, we can improve the script to make it faster. Let’s see which parts we can optimize. The first step is the . For sure, we have to run to see if the project builds correctly. You can consider adding the flag to skip the step before building. build phase dotnet build --no-restore restore Then we have the : we can avoid formatting every file using one of the steps defined before. I’ll replace the plain with the execution of the script defined in the Task Runner (it’s the third approach we saw). format phase dotnet format Then, we have the . We can add both the and the flag to the command since we have already built everything before. ! The format phase updated the content of our files, so we still have to build the whole solution. Unless we swap the and the phases. test phase --no-restore --no-build But wait build format So, here we have the final file: pre-commit #!/bin/sh
. "$(dirname "$0")/_/husky.sh"

echo 'Ready to commit changes!'

echo 'Format'

dotnet husky run --name dotnet-format-staged-files

echo 'Build'

dotnet build --no-restore

echo 'Test'

dotnet test --no-restore

echo 'Completed pre-commit changes' Yes, I know that when you run the command, you also build the solution, but I prefer having two separate steps just for clarity! dotnet test Ah, and at the beginning of the script! don’t remove the #!/bin/sh How to skip Git hooks To trigger the hook, just run . completing the commit, the hook will run all the commands. . git commit -m "message" Before If one of them fails, the whole commit operation is aborted There are cases when you have to . For example, if you have integration tests that rely on an external source currently offline. In that case, some tests will fail, and you will be able to commit your code only once the external system gets working again. skip the validation You can skip the commit validation by adding the flag: --no-verify git commit -m "my message" --no-verify Further readings Husky.NET is a porting of the Husky tool we already used in a previous article, using it as an NPM dependency. In that article, we also learned how to customize Conventional Commits using Git hooks. 🔗 How to customize Conventional Commits in a .NET application using GitHooks | Code4IT As we learned, there are many more Git hooks that we can use. You can see the complete list on the Git documentation: 🔗 Customizing Git - Git Hooks | Git docs Of course, if you want to get the best out of Husky.NET, I suggest you have a look at the official documentation: 🔗 Husky.Net documentation One last thing: we installed Husky.NET using dotnet tools. If you want to learn more about this topic, I found an excellent article online that you might want to read: 🔗 Using dotnet tools | Gustav Ehrenborg Wrapping up In this article, we learned how to create a Git hook and validate all our changes before committing them to our Git repository. pre-commit We also focused on the formatting of our code: how can we format only the files we have changed without impacting the whole solution? I hope you enjoyed this article! Let’s keep in touch on or ! 🤜🤛 Twitter LinkedIn Happy coding! 🐧 Also published . here

Optimizing .NET Development Workflow with Git Hooks and Husky.NET

Carbon Aware Computing: Next Green Breakthrough or New Greenwashing?

কার্বন সচেতন কম্পিউটিং: পরবর্তী গ্রিন ব্রেকথ্রু বা নতুন গ্রিনওয়াশিং?

CO2-bewusstes Computing: Nächster grüner Durchbruch oder neues Greenwashing?

Computación consciente del carbono: ¿próximo avance ecológico o nuevo lavado verde?

Informatique respectueuse du carbone : prochaine percée verte ou nouveau greenwashing ?

कार्बन अवेयर कंप्यूटिंग: अगला ग्रीन ब्रेकथ्रू या नया ग्रीनवाशिंग?

カーボン アウェア コンピューティング: 次のグリーン ブレークスルーか、それとも新たなグリーンウォッシングか?

탄소 인식 컴퓨팅: 차세대 친환경 혁신인가 아니면 새로운 Greenwashing인가?

Computação Consciente do Carbono: Próximo Avanço Verde ou Nova Lavagem Verde?

Вычисления с учетом выбросов углерода: следующий «зеленый прорыв» или новое «зеленое отмывание»?

Karbon Farkında Bilgi İşlem: Bir Sonraki Yeşil Atılım mı, Yeni Bir Yeşil Yıkama mı?

Máy tính nhận biết carbon: Đột phá xanh tiếp theo hay tẩy xanh mới?

碳感知计算：下一个绿色突破还是新的绿色清洗？

React is a component-based library, so you can build interactive apps one component at a time. Components are separate pieces of UI, but still interconnected. Props is a React feature that allows components to receive and pass data, similar to how you’d pass an argument to a function. This allows us to build complex apps with React. In this article, we’ll explore how to use props to pass a function from parent to child components. If you enjoy learning about React, my blog has 50+ . React tutorials Pass a Function via Props in React Let’s see how to do this in 3 simple steps. Define the function First, we need to create a function in the parent component. Most of the time, we pass down functions to handle events in child components, so let’s create a simple event handler. onClick const handleClick = console.log("you just clicked a button") When a user clicks a button, our event handler will simply log a message to the console. Pass the function via props The syntax for setting props is similar to setting an attribute. You can think of props as custom attributes for components in React. To pass a function, you can simply reference the name of the variable that stores the function. In this case, that would be variable. handleClick <childComponent handler={handleClick} /> In this case, the name of the prop (the custom attribute) is . Curly braces are necessary to set its value to a JavaScript expression ( variable holds the function). handler handleClick Do not call the function when you pass it via props. Only pass a reference to a function. Otherwise, the function will run when you don’t want it to (every time the component is rendered). Important: Call the function in the child component Now, let’s call the function passed to the child component via props. Functional components must accept props as an argument. Props is an object where properties and values correspond to props and values passed to the component. In this case, the object has one property - and its value will be the function. props handler You can call the function using dot notation - or you can use new syntax and destructure props object. props.handler() Why Should You Pass a Function via Props? Keeping track of changes in the state and props is very important in React. Storing user data in one component makes your app more consistent and error-free. Usually, this component needs to be at (or near) the top of the component tree, so it can store child components’ internal data. This concept is often called the ‘Single Source of Truth.’ It’s also common to store user inputs in the state. Input elements are usually in child components, and logic is handled in the parent component. You need some way to get data from input elements to the parent component. Props are strictly uni-dimensional - parent components can pass data (or, like in this case, a function) to child components, but the latter can not pass data up to parent components. React developers often pass event handlers to child components, which pass arguments to event handlers that update the state of the parent component.

How to Pass A Function via Props in React

RunWhen

runwhen.com

1-10 employees

Since n.d.

COMPANY RANKING

RUNWHEN

EVERGREEN INDEX #10163

RunWhen WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

RunWhen

runwhen.com

1-10 employees

Since n.d.

COMPANY RANKING

RUNWHEN

EVERGREEN INDEX #10163

RELATED COMPANIESRANK

STORIES ABOUT RUNWHEN

RunWhen WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!