GREENHUB

greenhub

The Epitome of Loyalty Marketing, Samurais and The Bushido Code

আনুগত্য বিপণনের এপিটোম, সামুরাই এবং বুশিডো কোড

Der Inbegriff von Loyalty Marketing, Samurais und dem Bushido-Kodex

El epítome del marketing de fidelización, los samuráis y el código Bushido

La quintessence du marketing de fidélisation, des samouraïs et du code Bushido

वफादारी विपणन, समुराई और बुशिडो कोड का प्रतीक

ロイヤルティ マーケティングの典型、サムライと武士道

로열티 마케팅의 전형, 사무라이, 무사도 코드

O epítome do marketing de fidelidade, samurais e o código Bushido

Воплощение маркетинга лояльности, самураев и кодекса бусидо

Sadakat Pazarlamasının Özeti, Samuraylar ve Bushido Kuralları

Hình ảnh thu nhỏ của tiếp thị lòng trung thành, Samurai và mật mã võ sĩ đạo

忠诚营销、武士道和武士道的典范

Toast Notifications are yet another way to provide feedback to the user. They usually contain brief messages and sometimes get accompanied by CTAs as well. This article aims to explain how we could use and to create some beautiful-looking toast messages 😉 react-hot-toast styled-components Project Initialisation npx create-react-app toast-notification Install Dependencies for getting the toast notification functionality react-hot-toast for styling needs styled-components yarn add react-hot-toast styled-components Constants Default Title, Default Description & variants enum is stored in this file. // path: src/components/toast-notification/data.js

export const variants = {
  SUCCESS: "Success",
  WARNING: "Warning",
  QUESTION: "Question",
  FAIL: "Fail",
};

export const DEFAULT_TITLE = {
  Success: "Well done!",
  Warning: "Warning!",
  Question: "Hi there!",
  Fail: "Oh snap!",
};

export const DEFAULT_DESCRIPTION = {
  Success: "You successfully read this important message.",
  Warning: "Sorry! There was a problem with your request.",
  Question: "Do you have a problem? Just use this contact form.",
  Fail: "Change a few things up and try submitting again.",
}; App Component & component is called inside App component. Form Toaster // path: src/App.js

// External
import { Toaster } from "react-hot-toast";

// Components
import Form from "./components/form";

// Styles
import { AppStyles } from "./styles";

const App = () => {
  return (
    <AppStyles>
      <Form />
      <Toaster position="bottom-left" gutter={56} />
    </AppStyles>
  );
};

export default App; Toast Notification Component Toast Notification Component contains the styles for Toast Notification. // path: src/components/toast-notification/index.js

import React from "react";

// External
import toast from "react-hot-toast";

// Components
import CustomIcon from "../CustomIcon";

// Styles
import {
  NotificationCard,
  NotificationImage,
  NotificationImageWrapper,
  NotificationContent,
  NotificationTitle,
  NotificationDescription,
  NotificationIconButton,
  BubblesImage,
} from "../../styles";

const ToastNotification = ({
  t,
  bgColor,
  icon,
  bubbleImage,
  title,
  message,
}) => {
  // handlers
  const handleDismiss = () => {
    toast.dismiss(t.id);
  };

  return (
    <>
      <NotificationImageWrapper>
        <NotificationImage src={icon} alt="" role="presentation" />
      </NotificationImageWrapper>
      <NotificationCard bgColor={bgColor}>
        <BubblesImage src={bubbleImage} alt="" role="presentation" />
        <NotificationContent>
          <NotificationTitle>{title}</NotificationTitle>
          <NotificationDescription>{message}</NotificationDescription>
        </NotificationContent>
        <NotificationIconButton onClick={handleDismiss}>
          <CustomIcon icon="times" />
        </NotificationIconButton>
      </NotificationCard>
    </>
  );
};

export default ToastNotification; Form Component This component contains the inputs used for testing out the component. //path: src/components/form/index.js

import React, { useState, useEffect } from "react";

// External
import toast from "react-hot-toast";

// Components
import ToastNotification from "../toast-notification";

// Styles
import {
  Button,
  RadioButtonContainer,
  RadioButtonInput,
  OptionsContainer,
  Container,
} from "../../styles";

// Image
import questionImage from "../../images/question.png";
import successImage from "../../images/success.png";
import warningImage from "../../images/warning.png";
import failImage from "../../images/fail.png";
import greenBubbles from "../../images/green-bubbles.png";
import redBubbles from "../../images/red-bubbles.png";
import blueBubbles from "../../images/blue-bubbles.png";
import yellowBubbles from "../../images/yellow-bubbles.png";

// Constants
import {
  variants,
  DEFAULT_TITLE,
  DEFAULT_DESCRIPTION,
} from "../ToastNotification/data";

const Form = () => {
  const [currentVariant, setCurrentVariant] = useState(variants.SUCCESS);
  const [title, setTitle] = useState(DEFAULT_TITLE.SUCCESS);
  const [message, setMessage] = useState(DEFAULT_DESCRIPTION.SUCCESS);

  // change title and message when notification variant changes
  useEffect(() => {
    setTitle(DEFAULT_TITLE[currentVariant]);
    setMessage(DEFAULT_DESCRIPTION[currentVariant]);
  }, [currentVariant]);

  // show appropriate toast notification as per the variant
  const showToastNotification = () => {
    if (currentVariant === variants.SUCCESS) {
      toast.custom(t => (
        <ToastNotification
          t={t}
          icon={successImage}
          bubbleImage={greenBubbles}
          bgColor="#76bf4c"
          title={title}
          message={message}
        />
      ));
    }

    if (currentVariant === variants.QUESTION) {
      toast.custom(t => (
        <ToastNotification
          t={t}
          icon={questionImage}
          bubbleImage={blueBubbles}
          bgColor="#B8B5FF"
          title={title}
          message={message}
        />
      ));
    }

    if (currentVariant === variants.WARNING) {
      toast.custom(t => (
        <ToastNotification
          t={t}
          icon={warningImage}
          bubbleImage={yellowBubbles}
          bgColor="#FCA652"
          title={title}
          message={message}
        />
      ));
    }
    if (currentVariant === variants.FAIL) {
      toast.custom(t => (
        <ToastNotification
          t={t}
          icon={failImage}
          bubbleImage={redBubbles}
          bgColor="#F05454"
          title={title}
          message={message}
        />
      ));
    }
  };

  // handlers
  const handleVariantChange = e => {
    setCurrentVariant(e.target.name);
  };

  const handleTitleChange = e => {
    setTitle(e.target.value);
  };

  const handleMessageChange = e => {
    setMessage(e.target.value);
  };

  return (
    <>
      <OptionsContainer>
        {Object.values(variants).map(variant => (
          <RadioButtonContainer key={variant}>
            <RadioButtonInput
              type="radio"
              id={variant}
              name={variant}
              checked={currentVariant === variant}
              onChange={handleVariantChange}
            />
            <label htmlFor={variant}>{variant}</label>
          </RadioButtonContainer>
        ))}
      </OptionsContainer>
      <br />
      <Container>
        <label htmlFor="title-field">Title</label>
        <input
          id="title-field"
          type="text"
          value={title}
          onChange={handleTitleChange}
        />
        <label htmlFor="message-field">Message</label>
        <textarea
          id="message-field"
          rows="6"
          value={message}
          onChange={handleMessageChange}
        ></textarea>
      </Container>
      <Button
        isSelected={!(!title || !message)}
        onClick={showToastNotification}
      >
        Show Toast!
      </Button>
    </>
  );
};

export default Form; Conclusion And there we have it, we have got elegant-looking alert notification implemented. The is available on Github. Would love to hear your valuable feedback in the comments down below. Code See you guys 👋🏻  in the next article of this Component series! Happy coding & Stay safe! ✨ Follow me on & for more! Twitter Instagram This article can also be read on my . website

Build a Toast Message Component via React and Styled Components with Ease

THE GREENBOTTLES

Bunmi Akinyemiju is a serial entrepreneur, investor, and CEO of Venture Garden Group (VGG), a high-growth technology investment holding company that has incubated and invested in fintech companies that provide innovative solutions in multiple sectors of the African economy. He is also a Founding Partner at GreenHouse Capital (GHC) - the venture arm of the Venture Garden Group which has invested in over 20 innovative fintech companies across Africa like Helium Health, Flutterwave, Migo, Appzone and more. Bunmi is passionate about transforming Africa through technology and has successfully led several impactful change projects through strategic public and private sector partnerships. He studied Computer Science at Michigan State University, USA. In this Founders Connect video, Bunmi shares his background with me, and his experience across decades, innovating, investing and growing businesses in Africa. Watch the video https://www.youtube.com/watch?v=XbvH-8p-ckY Video timestamps - Introduction 0:00 - Bunmi shares his background, favourite memory as a child. 1:58 - Studying Computer engineering and getting into the corporate world (Artemis). 4:44 - Biggest lessons learned in the American Corporate world. 8:56 - Quitting Coding, assuming new roles at Artemis. 10:10 - Challenges faced at Artemis that have helped with new projects. 12:51 - Meeting with Co-Founders. 15:55 - Challenges from starting Venture Garden Group in 2010s. 19:27 - Advice on B2B Businesses. 26:20 - Biggest Milestones for Venture Garden Group. 28:20 - Synergy between Venture Garden and Greenhouse Capital Africa. 30:45 - Key challenges as a VC and it is different from working 22 years as an operator. 31:36 - Companies founded so far. 33:45 - Favourite Sstartup founded so far? The Most Memorable. 34:39 - Anything you will do differently if you could go back? 37:47 - Kind of Founders Bunmi invests in. Qualities he looks for. 41:39 - People Bunmi has learned from. 44:19 - Activities outside work. 48:43 - Questions he wants to be asked, Conclusion. 49:45

#FoundersConnect: Bunmi Akinyemiju, Partner at GreenHouse Capital, Former CEO Venture Garden Group

Episode 21: An interview with the founders of Crypto Disrupted Greeneum.net An interview with the CEO and COO of Greeneum, a green renewable energy blockchain. In the episode we discuss green energy, blockchain, and AI algorithms for detecting renewable energy. Also . available on iTunes For more episodes of , or . Crypto Disrupted subscribe on YouTube subscribe and listen on iTunes

Greeneum Renewable Energy Blockchain

If your team uses Git and Continuous Integration, chances are good that your workflow could benefit from . But first, strap on your VR headset and experience the perils of through the eyes of our seasoned developer, Karen. git greenbase git pull Karen vs the broken build You arrive to work still flush with exertion from your morning run, a smile on your face and a bounce in your step — the light bulb went off mid run: you knew why the identity service was flaking out every morning at 11:48AM. Firing up the console, you to the right repo and flows nimbly from your fingertips, your heel tapping out the beat to the last song on your playlist; it was a good one. cd git pull Git decides it needs to repack and take out the garbage on your oversized repo. You roll your eyes slightly, but no bother — nothing can get you down today. You’re in and out of Vim in a flash. Hard to believe such a simple three-line change would alleviate so much misery for the Ops peeps. You glance at the clock. It just might be possible to get it diffed to code review before the daily standup. Just one thing left to do… Run the tests. “That’s funny…” “That’s funny… 17 tests failed???” You furrow your brow in consternation. “How did my change possibly break the Time widget”, you think, shaking your head. Down below, your once merry foot had stopped tapping, its good beats forgotten. The next ten minutes sneak past you like a puma as you pour over all the source files even remotely related to your fix. Still nothing. A blip on the screen shocks you from your concentration like a cold pie to the face. “You coming to the standup?” Yikes, I’m late! Skidding to a halt Coyote-style near the great semicircle of agility, you sidle up next to your buddy Anne. Everyone looks faintly amused, but they’re not looking at you. Tom is apologizing for breaking the build. “Sorry I’m late everybody”, you interject meekly. “I was looking at some tests I broke.” Tom looks at you sheepishly. “By any chance, were they 17 tests in the Time widget?” Slumping forward, you let out an overly dramatic exasperated sigh of frustration. The team glances around for a second, then bursts into laughter. It was a knowing laugh, one of commiseration and mutual understanding. Where vanilla falls short git pull What happened to you in our story? You pulled a broken build! That sent you down a rabbit hole searching in vain for a problem you didn’t cause. You ran to pull in the latest changes, but think about it, did you really want the changes? Or did you want the latest changes? When people build a house, they take time to prepare the land and the foundation. They don’t just start building on a pile of junk. Likewise, when we start development of a new feature or bug fix, we should start from a known good place. That gives you the confidence that any build or test failures really are fault, and not from Anne, Tom, or that one intern that rides around the office on a unicycle. git pull latest good your If your team practices and has a solid suite of automated tests, your source of truth for what constitutes a “known good build” is your CI server. Continuous Integration (CI) to the rescue! git greenbase This is where comes in. Instead of blindly running like a slot machine and hoping for the best, you run . It queries your CI server for the latest , or “green” build, then resets your local master to match. Voila! is now at a known good state. Start your coding engines with confidence! git greenbase git pull git greenbase passing master What about local feature branches? If you are on a local feature branch that tracks , and your team uses a rebase-based workflow, then still resets to match the green build, but it rebases your local feature branch on top of master. Pretty cool, huh? master git greenbase master also Installing git greenbase sits serenely on Github: . If you’re on Linux, install it like this: git greenbase https://github.com/tygerbytes/git-greenbase git clone cd git-greenbase ./install https://github.com/tygerbytes/git-greenbase.git The script will create a symlink to git-greenbase and add it to your PATH. Git will find it in your path and allow you to run , just like any Git command. ./install git greenbase (See the for the latest installation instructions.) repo But what about Mac and Windows? As of March 2018 git greenbase has only been tested with Linux. It works with Mac OS X as well. It most likely won’t work on Windows. I am totally open to pull requests. If demand is great enough, I’ll write a version in PowerShell. probably as is Configure to work with your CI provider git greenbase Now that it’s installed, how do you configure it to work with your CI provider? Typically you need to provide Git with your CI server’s URL, API token, and the ID of your project. The information is stored in your Git config. For example, if you use Travis CI, you would run commands similar to the following: git config . traviscigit config greenbase. git config greenbase.travisci. git config greenbase.travisci. greenbase provider travisci.token <TOKEN> serverUri <SERVER_URI> repoId <GITHUB_REPO_ID> ( for the latest configuration instructions.) See the repo Which CI providers are supported? As of March 2018 the only CI providers supported out of the OSS box are: Gitlab Travis CI TFS (Not well-tested) That’s a short list! If you would like to add support for another CI provider, feel free to send me a pull request. See below under “Contributing to development.” Contributing to development git greenbase is written in Bash, and tested using the . git greenbase Bats testing framework I tried my best to design it in a modular fashion for testability and maintainability. For example, the logic for communicating with each CI provider lives in its own Bash script, with its Bats tests alongside it in the same directory. Personally, , nor am I a super skilled Bash developer. That said, I feel tools like will bring more peace, love, and butterflies to the DevOps landscape. So I persevere. :) Bash isn’t my favorite language git greenbase See the for the latest development details. development page Can I buy you a coffee? If you’re super stoked about and all the pain it has saved you and your team, . I find coffee a great motivator. git greenbase buy me a coffee Originally published at tygertec.com on March 5, 2018.

git greenbase means never pulling a broken build

How Digital Twins Use Big Data to Mirror the Real World

The importance of reducing methane emissions is underestimated and understudied. Tracking methane emissions is hard due to gas leaking in many places along the long processing and distribution chain. Luckily, the newest technology allows us to track the emissions from space. Satellites armed with advanced sensors and AI are flagging invisible methane leaks that were once impossible to detect. In the era where cutting emissions is more urgent than ever, technology that exposes ‘super-emitter’ leaks from oil wells, gas pipelines, coal mines, and landfills is key to stopping climate change. Why Methane Matters? Why Methane Matters? Methane has a global warming potential higher than that of carbon dioxide on the 20-year scale. It traps heat more effectively than CO2, making it a main contributor to the short-term climate change effect. Moreover, like other greenhouse gases, methane accelerates the climate feedback loop, which in return releases more greenhouse gases. If CO2 is a slow buildup of warmth, methane is a sudden fever. If one CO2 molecule wraps Earth in a single blanket, one methane molecule is like throwing on 80 blankets. It breaks down in the atmosphere way faster than carbon dioxide, but is more harmful in the short term. That is why scientists see reducing methane emissions as the fastest way to slow down global warming. The problem is that methane is invisible and odorless. Leaks can go undetected for years and are related to many different industries, from oil and gas to decomposing trash in landfills. 20-year scale 80 blankets How Can Satellites “See” Methane? How Can Satellites “See” Methane? The issue with methane being transparent is that it cannot be discovered on a simple satellite image. However, imaging spectrometer sensors that are used in space measure what wavelengths of light are absorbed as the sunlight bounces off the Earth. Every gas has a unique light ‘fingerprint’. Methane absorbs sunlight in specific infrared bands that are invisible to our eyes but easily measured by a spectrometer. Thanks to spectrometers, satellites can detect methane by looking for the shadow of the infrared glow on the Earth below, which is specific for CH4. There is a broad range of sensors that can either analyze broad areas or zoom in on fine details, using them together helps create a more precise understanding of the location and size of methane plumes on Earth. Using AI to Contextualize the Data Using AI to Contextualize the Data Sensors from the satellites help create billions of data points every day, but it is Artificial Intelligence that helps understand that data. Machine learning models excel at pattern recognition in huge datasets. For methane detection, these models are trained to distinguish between the subtle signal of a plume from the background noise and from lookalike artifacts. There are multiple models that are trained depending on the data provided. One example is a two-step ML pipeline for Sentinel-5P data that first uses a convolutional neural network (CNN) to scan for anything plume-shaped, then a support vector machine (SVM) classifier double-checks those candidates to remove false detections. It proved extremely effective in 2021, discovering almost 3000 methane plumes around the world. Importantly, AI does this in almost real time, which is key in enforcing leak repairs. example Detecting the plumes is just the first step on the path to reducing emissions and tracking them. AI can also help trace them to their sources. This includes linking a specific plume to an infrastructure such as well, pipeline, or facility on the ground that’s responsible for it. Using the newest models, companies like Google are able to create infrastructure mappings that analyze high-resolution satellite images (such as Google Earth) and map them to the equipment around the world. Cross-referencing these maps with the maps of the methane plumes makes it easier to find specific culprits responsible for the emissions. This step is crucial as it transforms a vague pollution signal into an actionable insight that can be as specific as ‘valve #5 at pipeline X’ is leaking - fix needed. Google Real-World Impact Real-World Impact Finding the methane leak from space is a tremendous achievement, but the real impact comes from actually fixing it. So, how is this used in practice? UN Environment Programme is one example of applying data and technology to create impact using the Methane Alert and Response System (MARS). It continuously tracks the data coming from the satellites and alerts governments and companies when a major plume is detected. Unfortunately, even though in a year, MARS sent 1200 alerts, only 12 were actioned on and fixed, meaning only 1% of all leaks were removed. This shows that while the technology has been rapidly improving, policy is lagging. As Inger Andersen (UNEP’s director) put it bluntly, governments and companies need to ‘stop paying lip service’ and start fixing the leaks when they are alerted. alerts governments Still, there are a few notable success stories. Many alerts were actioned, most notably in Algeria, Azerbaijan, Nigeria, and the U.S.. In certain countries, new regulations, such as a methane fee in the U.S., give companies strong financial incentives to use an alerting system and act on the leaks. Azerbaijan’s state oil company, for example, said it identified 400 leaks via satellite monitoring and is working to fix them. And globally, there’s a push to make all this data public. Certain nonprofit initiatives, such as the Climate TRACE coalition and Carbon Mapper data portal, are aggregating satellite emissions data and sharing it openly. In the ideal scenario, there would be radical transparency, where everyone can see who is emitting, which then puts pressure on the emitter to fix the issue. A good example is the situation in Turkmenistan in 2022. After satellite data revealed huge methane plumes, it turned out the country was the single largest source of super-emitter leaks. This news helped gather international assistance to fix its aging infrastructure. the Climate TRACE coalition and Carbon Mapper data portal Challenges Ahead Challenges Ahead As much as the progress in the areas is impressive, we are far from perfect technology. For example, satellites can’t see through thick clouds, which means methane detection needs clear skies. This makes the tracking especially hard in tropical and high-altitude areas. There is research being done on the ways satellite sensors can complement other techniques, such as on the ground sensors, but the perfect solution is not there yet. Other challenges, such as having enough satellites and 24/7 coverage of the entire Earth in a financially viable manner, are still waiting to be resolved. Finally, even with perfect technology, the final solution still requires boots on the ground work to fix the issues and AI cannot do that for us. Luckily, as we overcome these challenges, the value of the technology itself will only increase. Methane detection through satellite imagery is a climate game-changer! (If we choose to use it)

Satellites Can “See” Methane, And Why This Is Important

The Rise of Tankies: A Data-Driven Look at Far-Left Extremism

The U.S. Dollar Is Just Socialism With Extra Steps

الدولار الأمريكي هو مجرد اشتراكية مع خطوات إضافية

El dólar estadounidense es simplemente socialismo con medidas adicionales

Yhdysvaltain dollari on vain sosialismia lisäaskelineen

米ドルは単なる社会主義に余分なステップを加えたもの

აშშ დოლარი უბრალოდ სოციალიზმია დამატებითი ნაბიჯებით

ເງິນໂດລາສະຫະລັດແມ່ນພຽງແຕ່ສັງຄົມນິຍົມທີ່ມີບາດກ້າວພິເສດ

JAV doleris yra tik socializmas su papildomais žingsniais

د امریکا ډالر یوازې د اضافي ګامونو سره سوسیالیزم دی

Dolarul american este doar socialism cu pași suplimentari

Dola ya Kimarekani Ni Ujamaa Tu Wenye Hatua za Ziada

Idola yaseMelika yiSocialism nje enamanyathelo awongezelelweyo

IDola Lase-U.S. Imane Iwubuhlali Nje Ngezinyathelo Ezingeziwe

Stories, News & Mentions about GREENHUB

Categories

Trending Topics

Stories, News & Mentions about GREENHUB

Greenhub’s Stories on HackerNoon

Categories

Trending Topics