DEV Community: Favour George

Infinite Gallery Viewer with Typescript

Favour George — Fri, 23 Oct 2020 13:24:47 +0000

In our previous series release Build a quote generator with typescript, we converted a regular Javascript code to Typescript, and it was fun. In today's release, we'd be converting an Infinite Gallery viewer built with Javascript to Typescript.

Disclaimer: This article is part of ZTM Andre Negeoi's Portfolio enhancement course

The Javascript codebase is on GitHub. You should obtain the site structure and stylesheet from there. We'd focus on the Typescript conversion here.

Setup Typescript

If you need help setting up your Typescript environment for this exercise, see the setup from our last series here

Getting an Unsplash API key

Head on to Unsplash and register, next click on api/developers tab from the profile menu, then click on Your apps. Follow the guide to create a new app and get your API_KEY.

Writing the App.ts

Let's start with our variables and interface definitions:

const imageContainer = document.getElementById('image-container');
const loader = document.getElementById('loader');

let photosArray: GalleryData[];
let ready = false;
let imagesLoaded = 0;
let totalImages = 0;
let count = 5;
const API_KEY = <your_api_key>;
let API_URL = `https://api.unsplash.com/photos/random/?client_id=${API_KEY}&count=${count}
`;

interface GalleryData {
  alt_description: string;
  urls: {
    regular: string;
  };
  links: {
    html: string;
  }
}

interface Attribute {
  src?: string;
  alt?: string;
  href?: string;
  title?: string;
  target?: string;
}

The functions

Our first function would be the imageLoaded function.

// Check if all images were loaded
function imageLoaded() {
  imagesLoaded++;

  if (imagesLoaded === totalImages) {
    ready = true;
    loader!.hidden = true;
    count = 30;
    API_URL = `https://api.unsplash.com/photos/random/?client_id=${API_KEY}&count=${count}
`;
  }
}

The special conversion highlight here is loader!.hidden = true; When we defined the loader element initially with this const loader = document.getElementById('loader');, we could either have the HTMLElement or null. To tell typescript that we are sure that the element exists on the page, we use the ! before the element name. That overrides typescript's strict null check.

Pro-Tip: Use only when you are double sure that the element exists on the page and will not be removed throughout the lifetime of your code.

setAttribute Helper function

This function will help us stay DRY. Typescript warns when we do not type our parameters. Our function would need

A HTMLElement to set the attributes against, this will be the first parameter.
An object that contains the attributes we want to set and their values.

// Helper function to set attributes on DOM elements
function setAttributes(element: HTMLElement, attributes: Attribute) {
  for (const [key, value] of Object.entries(attributes as Record<string, string>)) {
    element.setAttribute(key, value);
  }
}

Pro Tip: To use Object.entries, ensure you add "ES2017" or later to your tsconfig.json's lib.

displayPhotos function

The displayPhotos function generates the DOM elements and renders it to the screen.

// Display photos
const displayPhotos = () => {
  totalImages = photosArray.length;
  imagesLoaded = 0;

  photosArray.forEach(photo => {
    // Create <a> linking to unsplash
    const item = document.createElement('a');
    setAttributes(item, {
      href: photo.links.html,
      target: '_blank'
    })

    // Create <img> for photo
    const img = document.createElement('img');
    setAttributes(img, {
      src: photo.urls.regular,
      alt: photo.alt_description,
      title: photo.alt_description
    });

    // Event Listerner, check when each is finished loading
    img.addEventListener('load', imageLoaded)

    // Put <img> inside <a>, then put both in the imageContainer;
    item.appendChild(img)
    imageContainer!.appendChild(item);
  });
}

Finally, we will add the getPhotos function and attach our scroll event to the windows object.

// Get photos from Unsplash API
const getPhotos = async () => {
  try {
    const response = await fetch(API_URL);
    photosArray = await response.json()

    displayPhotos();
  } catch (error) {

  }
}

// Hook up the scroll event
window.addEventListener('scroll', () => {
  if (
    window.innerHeight + window.scrollY >=
    document.body.offsetHeight - 1000 &&
    ready
  ) {
    ready = false;
    getPhotos();
  }
})

// On load
getPhotos();

Now run the tsc --build tsconfig.json to build your .ts files into the required .js equivalence.

This was super exciting for me, I hope you enjoy it.

Typescript Beginner: Start Here

Favour George — Tue, 13 Oct 2020 23:46:23 +0000

TypeScript is a superset of JavaScript which compiles into JavaScript code. It's used to improve your code quality with OOP features and static typing. This transfers well into large-scale projects passing code between multiple team members. - Jaime Morrison whatpixel.com

TypeScript has come to stay, the market demand is increasing and the community is amazing.

So you want to learn Typescript

Learning typescript is a good decision, if you are coming from the Javascript ecosystem, OOP, FP, Typed language or nowhere; you'd find Typescript really interesting.

In this post, I'll share some of the places where you can find educating content to help you learn faster.

Basics

Typescript Docs - all of the basic things you need and beyond. This is the one-stop place you'd need throughout your journey.
The Typescript handbook - The handbook provides you with a strong understanding of concepts and topics in Typescript
FreeCodeCamp's Typescript in 5 mins - Samples a brief overview and introductions into data-types and classes.
Your Friendly Guide - An elaborate introduction into the world of Typescript. Valentino Gagliardi takes a bit of a deep dive into the primary concepts around Typescript.
Amanda's Step By Step Guide to Learn Typescript - Amanda Fawcett starts with a comparison approach, comparing Javascript with Typescript and shows a step-by-step directive in picking up Typescript faster.
Typescript for Beginners by RayRay - If you want to fast-forward into the nicer things with simplicity and clarity, read this. Enums, functions, interfaces and many more were succinctly presented.

Videos

Typescript Fundamentals - John Papa breaks it all down, start here for a deep understanding of the Typescript fundamentals.
Understanding Typescript - 2020 Edition - This course by Maximilian Schwarzmüller will get you grounded.

This Course takes you from the very Basics and its most important Feature (Types!) to the point where you're able to use TypeScript in any of your Projects. ReactJS Projects included! - Maximilian Schwarzmüller

Typescript Masterclass - Created by the Angular University is aimed at giving you all the tools you need to create your own Typescript projects from start to finish - like a Pro.
Typescript: The Complete Developer Guide [2020] - Stephen Grider is all about the mastery, you'd find complex topics simplified and accessible. What's more, you have many projects to build and solidify your learning.

Composition vs Inheritance? You'll understand it. Build your own web framework? You'll do it. Typescript with React/Redux? It's here! - Stephen Grider

Ultimate Courses: Master Typescript - This awesome course by Todd Motto will give you new and exciting approaches to mastering Typescript.

This course is currently selling at a discount. Grab it now

YouTube Playlist

Books

Blogs

Communities

Why do you use Typescript?

Typescript is powerful, sometimes is looks dirty, the tooling and setup may seem painful initially, but the challenges it addresses make it worth the effort. So why do you use Typescript in your code?

I'd really love to know... comment in the section below.

Build a Quote Generator with TypeScript

Favour George — Fri, 09 Oct 2020 00:33:05 +0000

This post was originally published here kodeinstincts.hashnode.dev

Typescript is a beautiful language, it gives us a lot of confidence as developers, there are loads of awesome content that share Typescript's awesomeness, but today, we are going to take a different route. You want to build little projects with Typescript so you can solidify your knowledge, and that is why we are here right now.

Project Details

Our quote generator is no different from the ones you've probably built with Javascript or other tutorials have covered, our job here today is to replicate our Javascript code in Typescript.

So then, our app will talk to an API to fetch the quote, and then we can render the quote on our beautiful screen.

This is the first on the #JStoTSconversion series I'd be covering here on my blog. So let's get started with what you need to have fun here.

Requirements

HTML5
CSS3
Javascript
Typescripts basics

If you have basic knowledge on these then you are good to go. Our next milestone is to get our project setup out of the way.

Install typescript globally with npm i -g typescript

Structure and Initialization

Open your terminal, create a directory in your favourite location and cd into it.

mkdir ts_quote_generator && cd ts_quote_generator

Next, add the tsconfig.json file in the root.

touch tsconfig.json

Fill the new tsconfig.json configuration file with the code snippet below:

{
  "compilerOptions": {
    "sourceMap": true,
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "ES2015"
    ],
    "module": "CommonJS",
    "outDir": "dist/",
    "strict": true
  }
}

We'll add a styles directory with a styles.css file in it and an index.html in the root.

styles
- styles.css
index.html

You can get the HTML file content from this gist and the stylesheet from here

Now let's get down to business.

Create an app.ts file in the root of the project, for testing purposes, add this line of code:

console.log("app is connected");

Now open the terminal and run your first tsc build command.

tsc is short for typescript compiler.

Run this command: tsc --build tsconfig.json. You can also run the tsc command without the arguments, like so: tsc. This should generate a new dist/ directory with two files.

Run the app and visit the browser console, we should see our message logging there.

With our typescript compilation working, we will shift attention to fleshing out the app logic.

// app.ts
const quoteContainer = document.getElementById('quote-container');
const loader = document.getElementById('loader');
const quoteText = document.getElementById('quote');
const authorText = document.getElementById('author');
const twitterBtn = document.getElementById('twitter');
const newQuoteBtn = document.getElementById('new-quote');

First, we register our DOM elements into our typescript file and hold them in memory. When making a request to the API for data, we need to show our loading state, we will write two helper functions for that (showContentLoader) and (hideContentLoader);

// app.ts

const showContentLoader = () => {
  if (loader && quoteContainer) {
    loader.hidden = false;
    quoteContainer.hidden = true;
  }
}

const hideContentLoader = () => {
  if (loader && quoteContainer) {
    if (!loader.hidden) {
      quoteContainer.hidden = false;
      loader.hidden = true;
    }
  }
}

In both functions, you'd notice the line if (loader && quoteContainer) {. This is because in our tsconfig.json file we have specified the rule "strict": true, so typescript will fail to build if we don't guard against null values among other things.

But how did we come about the `null` value?

When we try to get the HTMLElement from the DOM via getElementById() or any other API, there are 2 possible scenarios;

The element exists, and returns the corresponding data, or
The element is unavailable at the moment and therefore will return null.

When we try to read the value loader.hidden, we could, in fact, be doing null.hidden, this would crash our app because the getElementById() method returns a union of HTMLElement or null. James Henry talks more about this behaviour in his blog.

What have we gained?

Typescript enforces these checks to help us write quality and less buggy code. By checking for the availability of these elements, we save our app from crashing. Cool right? We will continue with this method throughout the code.

The getQuote Function

The getQuote() is responsible for fetching our quotes from the API, we are expecting a response from that request, and hence, we will utilize Typescript's interface to check for our data shape. Let's get the code;

interface QuoteData {
  quoteAuthor: string;
  quoteText: string;
  quoteLink?: string;
  senderLink?: string;
  senderName?: string;
}

// Get quote from API
const getQuote = async () => {
  showContentLoader();
  const proxyUrl = 'https://cors-anywhere.herokuapp.com/'
  const apiUrl = `https://api.forismatic.com/api/1.0/?method=getQuote&lang=en&format=json`;

  try {
    const response = await fetch(proxyUrl + apiUrl);
    const data: QuoteData = await response.json();

    if (authorText && quoteText) {
      // default to annoynmous if there is no author
      data.quoteAuthor === ''
        ? authorText.innerText = 'Anoynmous'
        : authorText.innerText = data.quoteAuthor;

      // Dynamically change text size
      data.quoteText.length > 120
        ? quoteText.classList.add('long-quote')
        : quoteText.classList.remove('long-quote');

      quoteText.innerText = data.quoteText;

      // show quote
      hideContentLoader();
    }
  } catch (error) {
    getQuote();
  }
}

We ensure that the response coming from the API matches our interface shape with this line const data: QuoteData = await response.json();.

Tweet Function

Hook up the tweet function and the getQuote function like so:

// Tweet quote
const tweetQuote = () => {
  if (quoteText && authorText) {
    const quote = quoteText.innerText;
    const author = authorText.innerText;
    const twitterUrl = `https://twitter.com/intent/tweet?text=${quote} - ${author}`;

    window.open(twitterUrl, '_blank');
  }
}

// Hook up the new tweet event
if (newQuoteBtn && twitterBtn) {
  newQuoteBtn.addEventListener('click', getQuote);
  twitterBtn.addEventListener('click', tweetQuote);
}

// OnLoad
getQuote();

That's all, we have added typescript to our little quote generator app. Your whole app.ts should look like this:

const quoteContainer = document.getElementById('quote-container');
const loader = document.getElementById('loader');
const quoteText = document.getElementById('quote');
const authorText = document.getElementById('author');
const twitterBtn = document.getElementById('twitter');
const newQuoteBtn = document.getElementById('new-quote');

interface QuoteData {
  quoteAuthor: string;
  quoteText: string;
  quoteLink?: string;
  senderLink?: string;
  senderName?: string;
}

const showContentLoader = () => {
  if (loader && quoteContainer) {
    loader.hidden = false;
    quoteContainer.hidden = true;
  }
}

const hideContentLoader = () => {
  if (loader && quoteContainer) {
    if (!loader.hidden) {
      quoteContainer.hidden = false;
      loader.hidden = true;
    }
  }
}

// Get quote from API
const getQuote = async () => {
  showContentLoader();
  const proxyUrl = 'https://cors-anywhere.herokuapp.com/'
  const apiUrl = `https://api.forismatic.com/api/1.0/?method=getQuote&lang=en&format=json`;

  try {
    const response = await fetch(proxyUrl + apiUrl);
    const data: QuoteData = await response.json();

    if (authorText && quoteText) {
      // default to annoynmous if there is no author
      data.quoteAuthor === ''
        ? authorText.innerText = 'Anoynmous'
        : authorText.innerText = data.quoteAuthor;

      // Dynamically change text size
      data.quoteText.length > 120
        ? quoteText.classList.add('long-quote')
        : quoteText.classList.remove('long-quote');

      quoteText.innerText = data.quoteText;

      // show quote
      hideContentLoader();
    }
  } catch (error) {
    getQuote();
  }
}

// Tweet quote
const tweetQuote = () => {
  if (quoteText && authorText) {
    const quote = quoteText.innerText;
    const author = authorText.innerText;
    const twitterUrl = `https://twitter.com/intent/tweet?text=${quote} - ${author}`;

    window.open(twitterUrl, '_blank');
  }
}

// Hook up the new tweet event
if (newQuoteBtn && twitterBtn) {
  newQuoteBtn.addEventListener('click', getQuote);
  twitterBtn.addEventListener('click', tweetQuote);
}

// OnLoad
getQuote();

Final Step

To get your new typescript file ready for the browser, open the terminal and run the build command again.

tsc --build tsconfig.json

Todo

You can optimize the getQuote function, it's recursive nature could mean a perpetual loading or crashing of our app if anything happens with the API providers. Set up a mechanism to guard against that. See the GitHub code here

See you in the next #JStoTSConversion.

The First Things About Your Teams' Agility

Favour George — Mon, 05 Oct 2020 11:31:28 +0000

This was originally published here kodeinstincts.hashnode.dev

Agile is a thinking methodology, a system of operation, a culture that governs systems and processes within a team.

Agile methodologies stem from the "Agile Manifesto". Agile is not a framework, software or tool, it's a concept, a way of thinking, a culture of product/service delivery.

Agile is about values; these values are enshrined in the Agile Manifesto which places the customer experience over the product development cycle.

The manifesto essentially values people above interactions and processes, working software/product above documentation, customer collaboration and satisfaction above contract negotiation, responding to changes above following product development plans.

Agile is discipline agnostic, this means; it works anywhere, from engineering to marketing, law enforcement, media, software development, etc. The need for an agile culture is rather obvious as customers are daily becoming more and more aware of what products and services can offer them, they have inadvertently become more selective, impatient and unforgiving.

Over the years some frameworks have been developed around the Agile concept, these frameworks help solidify the agile manifesto in principles and actions. The "Scrum" and "Kanban" are some of the most notable of such frameworks.
As a team you have to choose what works best for your team, it could be one or a hybrid of the frameworks with a touch of your teams' unique flavour. The goal is to keep the fidelity of the Agile Manifesto while giving it the interpretation that best suits your team.

What Agile offers you

As opposed to the traditional product development and delivery methods, where a team of product developers, designers and owners lock-in with product spec and build it from scratch until they feel their customers will love it, then they ship. Until it's shipped they have no real feedback, no real interactions with the market forces, no meaningful data for validation of their product, processes and systems.

It becomes harder for such a team to respond to changes, they may have to pull out a large chunk of the codebase to respond to a minor/major change, it takes them a long time to fully respond to these dynamics because they aren't prepared for it. They just aren't Agile.

An Agile team is happy with the Minimum Viable Product (MVP), you have surely heard of the term; an MVP represents the smallest working product or features your users can interact with. The MVP is a model to curry feedback to the team. Features are added incrementally as customers favour or dislike the current one. What you find is that these MVPs may not be elegant looking, but they are functional, they are Agile.

An MVP could be termed as the teams' "increment", their definition of done, a milestone, or a shippable Epic. These MVPs are products of sprints engaged by the team, a sprint typically should span a 2-week period. Sprints have backlogs which are definitions of ToDos curated from the project backlog. These backlogs are filtered and altered according to the feedback received from the last shipment. You immediately see how Agile is immersive, involving the customer, designers, developers and product owners.

An Agile team will get to the market faster, get realistic feedback and reiterate on their product, services and systems to meet their customers evolving needs and taste, as well as save production cost. They handle changes more efficiently, implement new features with more confidence and have a more committed team and happy customer base. They are Agile, responsive and dynamic. They learn by failing, you could say failure is their best friend. They constantly reiterate over their failing processes until they have the system that works.

Is your team Agile yet? What Agile methodologies are you implementing? Are you an Agile practitioner?

Keep an eye here as we increase your agility.

Building A CRON-MAN In NodeJs

Favour George — Sat, 21 Sep 2019 15:42:47 +0000

In this article we are going to learn how to setup a NodeJs cron-job, our cron will lookup our database collection and delete redundant users. We are going to see a few NodeJs APIs that will help us achieve our desired goal.

What is a CRON JOB?

A cronjob is a program that runs regularly at a specified time and carries out any specified task. You may think of it as a bot. You could want to send out newsletters to all who signed up on your platform today, you could want to check another service which your application uses for updates and then correctly update your own service. You could do just about anything with a cronjob.

Okay, I hear you, why do I need a CRONJOB?

You see, while working with a database, you may notice that users of your application often upload or save files which they do not need into your database or cloud storage bucket. Your cronjob would occasionally check your storage system, find these redundant files and implement your desired instructions. You are not limited to the database anyway, you can implement this just about anywhere, ideally, the storage system is a popular use case.

The cron-man or manager will handle all our cronjobs. This means all our cronjobs will be managed from the same file.

Ready? Now let's get started

I will assume you already have a functional View and Model already, so we can get to the cron manager immediately.

We will structure our cronjob runner into 3 parts:

The Scheduler
The Action
The cron-man

The Scheduler

The scheduler will take in 2 parameters, the time interval in milliseconds and the action to run.

The Action

This is a function which will be called by our scheduler, this function bears the logic of what needs to be done every time our scheduler calls it. It is important to make your actions pure. Using pure functions will help check against memory leaks and side-effects.

The Cron-Man

The cron manager will bootstrap all our schedulers and manage them for us. We simply import our scheduler function and actions here. This is important for debugging and more so it makes our cron modular.

The cron manager

Now that we have conceptually described our cron program, let's get into the code level. Create a cron directory in your project, it should have 2 sub folders (cron-jobs & scheduler) and the cronMan.js file.

Your folder structure

We start by fleshing out the scheduler function. It will look like so:

Our scheduler needs two vital pieces. The setInterval() timer API and the process.nextTick() API from NodeJs. For more information on the timer API, see their documentation. The setInterval() takes the time and the action to call once the time provided has elapsed.

The process.nextTick() will ensure that our scheduler function is called once the current job in the NodeJs event loop is completed. It gets called before any other I/O event, or timers are loaded into the event loop. This is a good way for us to hook into the life-cycle of our program and inject our cron job.

There is a beautiful article written by Tendai Mutunhire on this. You should check it out: Events and Timers in Node.js. You can also see the official documentation on process.nextTick(callback[,…args])

Let's continue building, now we will focus on the actions. You will notice how we have named our directory cron-jobs, this means we can have more than one job and house them together inside of the cron-jobs directory.

For this example, we will setup a deleteInactives cronjob. This will lookup our database and delete all currently inactive users.
In a real-world application, you should not delete the users, but the redundant files they have, like pictures, videos, pdfs, and the likes which have not been saved by the user but uploaded to your database.

In our example app, say we give all users 24 hours to activate their accounts, at the expiration of this time, we will delete all inactive accounts. Great, let's write the code now.

Our deleteInactive users function above will remove any user whose isActive property is false.

Let's now set up the cron manager file, open the cronMan.js file and write code away…

All we have to do now is to inject the cronMan.js file into our app. Inside our index.js, we will require the cronMan file at line 1 like so:

require("./cron-man/cronMan");

Awesome, now when check our console we should see new messages logging the number of users deleted.

Currently, our scheduled job runs every 10000 milliseconds, you should set your timer according to the needs of your application.

you rock

There you have it. You have successfully set-up your first CRON-JOB. That was easy right? Now go and save the world your cron-man 🚀🚀🚀

Tracking Result

Favour George — Thu, 21 Jun 2018 23:54:07 +0000

Sometimes it’s hard to figure out what you have achieved, keeping track of the past comes with a price, one that most people prefer not to pay. The importance of keeping these records abundantly reveal that sticking with this seemingly painful habit is rewarding. Most multi-national companies implement this on daily basis, even if you had a month old start-up you could take advantage of this and steer your business into greatness. You may or may not be a record keeper, statistician or anything of the sort, but learning these principles would help you decisively place your work, business or personality on the platform that matters.

These steps would help you stay on top of this habit if you read on…

HAVE A PLAN

This is arguably the most talked about step in the history of articles, while this may be true, the essence of this step cannot be over-emphasized. Having plans help you to stay on track, articulate and take decisions faster. Plans help you visualize the road map leading to your destination.

If there were no plans, it becomes difficult to say where on the progress line you were at the moment. Modeling your actions on paper makes your transition to the Result faster.

WIN TODAY

Next up after you have setup a proper plan, you have to start off the process with the Goals of winning today!

What that means? Set plans that you will have to achieve TODAY. Whether they are simple or not! You have to start out conquering the activities of Today. Say you have a Press Conference talk to hold, a meeting at the office with the Regional Managers, a Date with a family member late in the evening and perhaps a quick manifest at the gym, that is sure some scheduling to do… but your day won’t be entirely successful if half of the things to-do were not done.

So you take all the activities and stack them by precedence and priority, this allows you to know what is important at the moment and focus your energy and attention to completing it.

If today is lost, tomorrow is half spent fixing today. @tz_fayvor

So keep a clean record of these little daily activities that make up the big picture and finish them on time. That way you are efficiently producing the needed Result.

AUDIT TODAY

At the end of everyday, you should take out sometime to briefly check through your list / plan and discover which ones you did complete, which ones were half done and why? Maybe some circumstances beyond your control came up and distorted the flow of things… you will have to note this down and look out for ways to handle such logistics next-time they show up so they don’t ultimately stall your progress.

You also do need to note what was done well, what was done perfectly well and what was untouched at all. To increase productivity, you may need to constantly improve your way of doing things well… seek for ways to do them better.

Keeping record about this would help you know when, how and why you are improving.

TAKE DECISIONS ON TIME

To get more result, you have to take decisions on time. Decisions are the pivot points that define balance in whatever you do. When you have a habit of taking decision late, or making the wrong decisions, you will discover you almost always have the poor results rewarded.

In my opinion it is best to take decisions while planing; at such moments you get a peek into each future moment. What actions would ensue based on the current decision. What reactive measure could safely handle bad occurrences or what decisions are best suited for a particular task and why those decisions matter!

Taking Decisions in the middle of execution is somewhat unhealthy because there could be pressures that would lead you to taking the wrong decision. You get what am trying to say right? You just have to have it ready. You just have to be prepared and ready to tackle stuffs right? Pressuring yourself into a decision could hurt when the pressure recedes and you become more rational.

Decisions sharpen Precisions

To forestall this, you need to take decisions ahead of time, and be confident those decision are right for you and the Result you seek. Be sure to know why such decisions are right and then stand by your decisions. This will make people believe in you and your Results. Even if they fail at the moment be sure to be firm on your decisions.

STAY FOCUSED AND POSITIVE

Getting the required Result most times can be a rather unbearable process. But with patience, focus and hard-work virtually anything pays off. When the ladder becomes too steep to ascend, hold on and stay positive. A lot of people are in rots and are clanged up with a myriad of barriers, while giving up may seem good an option, breaking to the realms of success will take a lot of determination, courage and focus.

Most times you could need support from environment, people and friends around you. The support you seek should be one that drives you to fulfilling your set goals and not the other way round.

Its good you have come this far. I am excited you stayed with me through it. I am more than excited to hear your success story and help spread your Result approach to all that care to listen… we can get talking @tz_fayvor on twitter, @ignyte4 on twitter and also facebook.