<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sulenchy on Medium]]></title>
        <description><![CDATA[Stories by Sulenchy on Medium]]></description>
        <link>https://medium.com/@abuduabiodunsulaiman?source=rss-c4b3bd64c255------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*c4K2AmOYefrUImps98AuIw.jpeg</url>
            <title>Stories by Sulenchy on Medium</title>
            <link>https://medium.com/@abuduabiodunsulaiman?source=rss-c4b3bd64c255------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:40:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abuduabiodunsulaiman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[TSRX: The Next Evolution of React Development]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@abuduabiodunsulaiman/tsrx-the-next-evolution-of-react-development-2e04e1340e31?source=rss-c4b3bd64c255------2"><img src="https://cdn-images-1.medium.com/max/1894/1*VqENZKupHpUkPB9Z_EjGag.png" width="1894"></a></p><p class="medium-feed-snippet">React developers have spent years writing UI with JSX. While JSX transformed frontend development, it also introduced a compromise: UI&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@abuduabiodunsulaiman/tsrx-the-next-evolution-of-react-development-2e04e1340e31?source=rss-c4b3bd64c255------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@abuduabiodunsulaiman/tsrx-the-next-evolution-of-react-development-2e04e1340e31?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e04e1340e31</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[tsrx]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 00:24:51 GMT</pubDate>
            <atom:updated>2026-06-23T00:35:18.568Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Introducing pagination-core — Headless, Isomorphic Pagination for JavaScript/Typescript]]></title>
            <link>https://medium.com/@abuduabiodunsulaiman/introducing-pagination-core-headless-isomorphic-pagination-for-javascript-typescript-bc30306e4a2b?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc30306e4a2b</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[pagination]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Mon, 23 Mar 2026 14:20:25 GMT</pubDate>
            <atom:updated>2026-03-23T14:20:25.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wU5osWyvHwdB1Uw9Dv2Y8Q.png" /></figure><p><strong>pagination-core</strong> is a lightweight, framework-agnostic pagination library for JavaScript. It works <strong>both on the client and server</strong>, providing full pagination logic without imposing any UI so that you can use it anywhere: React, Vue, Svelte, Node.js, or plain JS.</p><p><strong>npm:</strong> <a href="https://www.npmjs.com/package/pagination-core">https://www.npmjs.com/package/pagination-core</a></p><h3>Key Features</h3><ul><li><strong>Headless Logic</strong> — Full state and actions, no UI forced</li><li><strong>Isomorphic</strong> — Works in browsers and Node.js</li><li><strong>Framework-Agnostic</strong> — React, Vue, Svelte, or Vanilla JS</li><li><strong>Smart Pagination</strong> — Automatic truncated page lists (e.g., [1, 2, 3, &#39;...&#39;, 10])</li><li><strong>Lightweight &amp; TypeScript Ready</strong> — Zero dependencies with full typings</li></ul><h3>Quick Setup</h3><pre>npm install pagination-core<br># or<br>yarn add pagination-core<br># or <br>pnpm add pagination-core</pre><h3>Basic Usage</h3><pre>import { createPagination } from &quot;pagination-core&quot;;</pre><pre>let state;</pre><pre>const paginator = createPagination({<br>  totalItems: 100,<br>  itemsPerPage: 10,<br>  onStateChange: (s) =&gt; state = s,<br>});</pre><pre>// initialize<br>state = paginator.initialState;</pre><pre>console.log(state.pages); <br>// Output: [1, 2, 3, &quot;...&quot;, 10]</pre><h3>Navigating Pages</h3><pre>paginator.nextPage();<br>paginator.previousPage();<br>paginator.goToPage(5);</pre><h3>Client-Side Example (React)</h3><pre>{state.pages.map((page) =&gt;<br>  typeof page === &quot;number&quot; ? (<br>    &lt;button onClick={() =&gt; goToPage(page)}&gt;<br>      {page}<br>    &lt;/button&gt;<br>  ) : (<br>    &lt;span&gt;...&lt;/span&gt;<br>  )<br>)}</pre><h3>🌐 Server-Side Example (Node.js)</h3><pre>const paginator = createPagination({<br>  totalItems: data.length,<br>  itemsPerPage: 10,<br>  onStateChange: (s) =&gt; state = s,<br>});</pre><pre>paginator.goToPage(page);</pre><pre>const start = (state.currentPage - 1) * 10;<br>const paginatedData = data.slice(start, start + 10);</pre><blockquote><em>One logic, two environments, zero duplication.</em></blockquote><h3>Why Use pagination-core?</h3><ul><li>Reusable logic across projects</li><li>Clean separation of logic and UI</li><li>Works consistently in frontend and backend</li><li>Predictable, smart pagination behavior</li><li>Lightweight and AI-friendly</li></ul><p><strong>npm:</strong> <a href="https://www.npmjs.com/package/pagination-core">https://www.npmjs.com/package/pagination-core</a></p><p><strong>github</strong>: <a href="https://github.com/sulenchy/pagination-core">https://github.com/sulenchy/pagination-core</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc30306e4a2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Re-renders Explained: The Mental Model Most Developers Miss]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@abuduabiodunsulaiman/react-re-renders-explained-the-mental-model-most-developers-miss-00385ce97576?source=rss-c4b3bd64c255------2"><img src="https://cdn-images-1.medium.com/max/1000/1*cQFK6iESaqJtbD7-neXMfg.png" width="1000"></a></p><p class="medium-feed-snippet">If you&#x2019;ve worked with React for a while, you&#x2019;ve probably heard things like:</p><p class="medium-feed-link"><a href="https://medium.com/@abuduabiodunsulaiman/react-re-renders-explained-the-mental-model-most-developers-miss-00385ce97576?source=rss-c4b3bd64c255------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@abuduabiodunsulaiman/react-re-renders-explained-the-mental-model-most-developers-miss-00385ce97576?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/00385ce97576</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 14:11:49 GMT</pubDate>
            <atom:updated>2026-02-03T14:11:49.525Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Learning a New Framework or Tool: Why Manual Setup Matters More Than CLI Shortcuts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/chingu/learning-a-new-framework-or-tool-why-manual-setup-matters-more-than-cli-shortcuts-2e82d290fbf0?source=rss-c4b3bd64c255------2"><img src="https://cdn-images-1.medium.com/max/2072/1*smV3piBIOWVcn7cHV3afxg.png" width="2072"></a></p><p class="medium-feed-snippet">A case study of React app setup</p><p class="medium-feed-link"><a href="https://medium.com/chingu/learning-a-new-framework-or-tool-why-manual-setup-matters-more-than-cli-shortcuts-2e82d290fbf0?source=rss-c4b3bd64c255------2">Continue reading on Chingu »</a></p></div>]]></description>
            <link>https://medium.com/chingu/learning-a-new-framework-or-tool-why-manual-setup-matters-more-than-cli-shortcuts-2e82d290fbf0?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e82d290fbf0</guid>
            <category><![CDATA[manual-setup]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[js]]></category>
            <category><![CDATA[js-framework]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 10:34:53 GMT</pubDate>
            <atom:updated>2025-12-19T11:08:56.410Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Setup React app with webpack(TS and JS)]]></title>
            <link>https://medium.com/@abuduabiodunsulaiman/setup-react-app-with-webpack-ts-and-js-da80cf3b7278?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/da80cf3b7278</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[typescript-with-react]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 20:43:06 GMT</pubDate>
            <atom:updated>2022-02-18T18:36:47.393Z</atom:updated>
            <content:encoded><![CDATA[<p>This is intended to walk you through setting up react app with webpack from scratch(without CRA). React is popular with two major languages: Javascript and Typescript. And as a result, this doc target readers who are interested in setting up react with javascript as well as typescript. It begins with javascript and ends with typescript. Before we get started, ensure you have node installed. See <a href="https://nodejs.org/en/download/">node doc</a>. Here are the key points discussed:</p><ol><li>Initialize the application</li><li>Install react and react-dom</li><li>Install and setup babel for Js transpiling(es6 features to es5)</li><li>Install and setup webpack for modules and files bundling</li><li>Add basic files (index.html, index.js and app.js)</li><li>Update the package.json</li><li>Test the app</li><li>Migrate to Typescript</li></ol><h3>Initialize the App</h3><p>Initialize the app by creating a new directory and run npm init(Node helps you prepare the directory for the task ahead by asking a few questions). For the purpose of this course, you can accept the default answers and move on.</p><h3>Install React and React DOM</h3><p>We just created a bare node application and we need to specify that the node application is a react application. To do that we need two packages from npm: react and react-dom. React package contains only the functionalities necessary to define React components(User Interface). The react-dom serves as the entry point to the DOM and server renderers for React. Install the packages by running the command below in your command line</p><pre>npm install --save-dev react react-dom</pre><h3>Install and setup babel for transpiling JS new features</h3><p>Babel is a compiler that converts new features in javascript to the old version so that old machines(browsers) could understand it. In the case of React, among others, JSX is the main feature. Browsers do not understand JSX(a proper way to declare a component in react) and other es6 features. To setup babel, run the command below to install babel and other related packages:</p><pre>npm install --save-dev @babel/core babel-loader @babel/preset-env @babel/preset-react</pre><p>Wait until babel installation is successfully complete and add to the root directory a config file for babel named .babelrc and paste the following code snippet</p><pre>{</pre><pre>&quot;presets&quot;: [</pre><pre>&quot;@babel/preset-env&quot;,</pre><pre>&quot;@babel/preset-react&quot;</pre><pre>]</pre><pre>}</pre><h3>Install and setup webpack for modules bundling</h3><p>Webpack is a static module bundler for modern javascript applications (see official doc). It is good at bundling all modules and files that constitute a javascript application into a file from where the application can be served. An easier way to set up a webpack is to have a config file that directs how webpack goes about the bundling. The config file is a js file that exports an object. The object contains the following keys:</p><p><strong>Entry</strong>: This tells webpack the entry point to begin the bundling</p><p><strong>Output</strong>: This tells webpack where to emit bundles when it has finished the bundling</p><p><strong>Loaders</strong>: Webpack only understands javascript and JSON. Loaders tell webpack how to handle other files in the javascript application such as CSS, images, typescript, etc</p><p><strong>Mode</strong>: This tells webpack the environment in which the bundles are meant for. This enables webpack’s built-in optimizations that correspond to each environment.</p><p><strong>Plugins</strong>: While loaders are used to transform certain types of modules, plugins can be leveraged to perform a wider range of tasks like bundle optimization, asset management, and injection of environment variables (see official doc).</p><p>To set up webpack, first we need to install some webpack related packages. Precisely, three of them: webpack, webpack-cli and webpack-dev-server. Run the command below in your terminal:</p><pre>npm install webpack webpack-cli webpack-dev-server html-webpack-plugin --save-dev</pre><p>Then create a new file in the root directory and name it <strong>webpack.config.js</strong>. Then paste the code snippet below in it.</p><pre>const path = require(&#39;path&#39;);</pre><pre>const HtmlWebpackPlugin = require(&#39;html-webpack-plugin&#39;);</pre><pre>module.exports = {</pre><pre>mode: &#39;development&#39;,</pre><pre>entry: &#39;./main.jsx&#39;,</pre><pre>devtool: &#39;inline-source-map&#39;,</pre><pre>output: {</pre><pre>path: path.join(__dirname, &#39;/dist&#39;),</pre><pre>filename: &#39;bundle.js&#39;</pre><pre>},</pre><pre>devtool: &#39;inline-source-map&#39;,</pre><pre>devServer: {</pre><pre>static: &#39;./dist&#39;,</pre><pre>},</pre><pre>module: {</pre><pre>rules: [</pre><pre>{</pre><pre>test: /\.jsx?$/,</pre><pre>exclude: /node_modules/,</pre><pre>loader: &#39;babel-loader&#39;</pre><pre>},</pre><pre>]</pre><pre>},</pre><pre>resolve: {</pre><pre>extensions: [&#39;.jsx&#39;, &#39;.ts&#39;, &#39;.js&#39;],</pre><pre>},</pre><pre>plugins:[</pre><pre>new HtmlWebpackPlugin({</pre><pre>template: &#39;./index.html&#39;</pre><pre>})</pre><pre>]</pre><pre>}</pre><h3>Add basic files (index.html, index.js, and app.js)</h3><p>Create three new files in the root folder as shown below:</p><h4>index.html</h4><pre>&lt;!DOCTYPE html&gt;</pre><pre>&lt;html&gt;</pre><pre>&lt;head&gt;</pre><pre>&lt;meta charset=&quot;utf-8&quot;&gt;</pre><pre>&lt;meta http-equiv=&quot;X-UA-Compatible&quot; content=&quot;IE=edge&quot;&gt;</pre><pre>&lt;title&gt;&lt;/title&gt;</pre><pre>&lt;meta name=&quot;description&quot; content=&quot;&quot;&gt;</pre><pre>&lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1&quot;&gt;</pre><pre>&lt;link rel=&quot;stylesheet&quot; href=&quot;&quot;&gt;</pre><pre>&lt;/head&gt;</pre><pre>&lt;body&gt;</pre><pre>&lt;div id=&quot;root&quot;&gt;&lt;/div&gt;</pre><pre>&lt;/body&gt;</pre><pre>&lt;/html&gt;</pre><h4>app.jsx</h4><pre>import React from &#39;react&#39;;</pre><pre>function App() {</pre><pre>return (</pre><pre>&lt;div&gt;{&#39;react setup from scratch without cra testing ts&#39;}&lt;/div&gt;</pre><pre>);</pre><pre>}</pre><pre>export default App;</pre><p>The above code snippet specify a basic functional component in react js.</p><h4>main.jsx</h4><pre>import React from &quot;react&quot;;</pre><pre>import ReactDOM from &quot;react-dom&quot;;</pre><pre>import App from &#39;./app&#39;;</pre><pre>ReactDOM.render(&lt;App /&gt;, document.getElementById(&#39;root&#39;));</pre><p>The above is the entry point where react renders the application with the help of reactDOM. As you can see in the last line of code, the app is being rendered on a div element with id root.</p><h3>Update the package.json</h3><p>Now, the package.json created at the beginning when the app was initialized needs to be updated. We need to inform it how to build and start the application. To do that, the script section of package.json needs to be updated as follows:</p><pre>{</pre><pre>&quot;name&quot;: &quot;react-scratch-sample&quot;,</pre><pre>&quot;version&quot;: &quot;1.0.0&quot;,</pre><pre>&quot;description&quot;: &quot;&quot;,</pre><pre>&quot;main&quot;: &quot;main.js&quot;,</pre><pre>&quot;scripts&quot;: {</pre><pre>&quot;test&quot;: &quot;echo \&quot;Error: no test specified\&quot; &amp;&amp; exit 1&quot;,</pre><pre>&quot;start&quot;: &quot;webpack-dev-server --open --mode development --hot&quot;,</pre><pre>&quot;build&quot;: &quot;webpack --mode production&quot;</pre><pre>},</pre><pre>&quot;author&quot;: &quot;&quot;,</pre><pre>&quot;license&quot;: &quot;ISC&quot;,</pre><pre>&quot;devDependencies&quot;: {</pre><pre>&quot;@babel/core&quot;: &quot;^7.16.5&quot;,</pre><pre>&quot;@babel/preset-env&quot;: &quot;^7.16.5&quot;,</pre><pre>&quot;@babel/preset-react&quot;: &quot;^7.16.5&quot;,</pre><pre>&quot;babel-loader&quot;: &quot;^8.2.3&quot;,</pre><pre>&quot;html-webpack-plugin&quot;: &quot;^5.5.0&quot;,</pre><pre>&quot;react&quot;: &quot;^17.0.2&quot;,</pre><pre>&quot;react-dom&quot;: &quot;^17.0.2&quot;,</pre><pre>&quot;webpack&quot;: &quot;^5.65.0&quot;,</pre><pre>&quot;webpack-cli&quot;: &quot;^4.9.1&quot;,</pre><pre>&quot;webpack-dev-server&quot;: &quot;^4.7.1&quot;</pre><pre>},</pre><pre>}</pre><h3>Test the App</h3><p>Now, it is time to test the react application. Run the command below in your terminal(ensure you are on the app directory)</p><pre>npm start</pre><p>Congratulations! That is how to set up a react app from scratch with webpack using javascript.</p><h3>Migrate to Typescript</h3><p>Typescript is a superset of javascript. Unlike javascript, it is strongly typed and easy to debug. It comes with some extra code but it can save you a lot headaches later during development. Typescript shines better in a robust application. Javascript usually becomes messy when an application is bigger in robustness. Let&#39;s migrate the application to typescript:</p><h4>Install the typescript and ts-loader</h4><pre>npm install --save-dev typescript ts-loader</pre><h4>Add ts-config JSON</h4><p>Create a ts-config.json file and add the snippet below:</p><pre>{</pre><pre>&quot;compilerOptions&quot;: {</pre><pre>&quot;outDir&quot;: &quot;./dist/&quot;,</pre><pre>&quot;sourceMap&quot;: true,</pre><pre>&quot;noImplicitAny&quot;: true,</pre><pre>&quot;module&quot;: &quot;es6&quot;,</pre><pre>&quot;target&quot;: &quot;es5&quot;,</pre><pre>&quot;jsx&quot;: &quot;react&quot;,</pre><pre>&quot;allowJs&quot;: true,</pre><pre>&quot;moduleResolution&quot;: &quot;node&quot;</pre><pre>}</pre><pre>}</pre><h4>Update webpack.config</h4><p>There are two sections to modify in the webpack.config: the loaders and resolve. Replace the snippet in the webpack.config with the snippet below:</p><pre>const path = require(&#39;path&#39;);</pre><pre>const HtmlWebpackPlugin = require(&#39;html-webpack-plugin&#39;);</pre><pre>module.exports = {</pre><pre>mode: &#39;development&#39;,</pre><pre>entry: &#39;./main.tsx&#39;,</pre><pre>devtool: &#39;inline-source-map&#39;,</pre><pre>output: {</pre><pre>path: path.join(__dirname, &#39;/dist&#39;),</pre><pre>filename: &#39;bundle.js&#39;</pre><pre>},</pre><pre>devtool: &#39;inline-source-map&#39;,</pre><pre>devServer: {</pre><pre>static: &#39;./dist&#39;,</pre><pre>},</pre><pre>module: {</pre><pre>rules: [</pre><pre>{</pre><pre>test: /\.jsx?$/,</pre><pre>exclude: /node_modules/,</pre><pre>loader: &#39;babel-loader&#39;</pre><pre>},</pre><pre>{</pre><pre>test: /\.tsx?$/,</pre><pre>use: &#39;ts-loader&#39;,</pre><pre>exclude: /node_modules/,</pre><pre>},</pre><pre>]</pre><pre>},</pre><pre>resolve: {</pre><pre>extensions: [&#39;.tsx&#39;, &#39;.ts&#39;, &#39;.js&#39;],</pre><pre>},</pre><pre>plugins:[</pre><pre>new HtmlWebpackPlugin({</pre><pre>template: &#39;./index.html&#39;</pre><pre>})</pre><pre>]</pre><pre>}</pre><h4>Add the declarative files</h4><p>Add declarative files for react and react-dom. Run the command below</p><pre>npm i <a href="http://twitter.com/types/react">@types/react</a> <a href="http://twitter.com/types/react-dom">@types/react-dom</a></pre><h4>Test the app</h4><p>Now that we have typescript installed and some configurations set up, we need to update the files extension to ts or tsx. Update the main.jsx filename to main.tsx and app.jsx to app.tsx. Also, update the modules import section of the files as follows:</p><pre>import * as React from &#39;react&#39;;<br>import * as ReactDOM from &#39;react-dom&#39;;</pre><p>Then start the app by running</p><pre>npm run start</pre><p>Congratulations!!!! The app has been migrated to typescript and the application can scale without much a headache.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da80cf3b7278" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zenhub 101: The Essential Guide]]></title>
            <link>https://medium.com/chingu/zenhub-101-the-essential-guide-da46ce7aff9d?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/da46ce7aff9d</guid>
            <category><![CDATA[zenhub]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-tools]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Mon, 28 Oct 2019 10:05:39 GMT</pubDate>
            <atom:updated>2019-11-17T19:03:13.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TmCbMxI5eYrG9ieaOSjioQ.gif" /></figure><h3>Introduction</h3><p>Ever think of what it feels like having a software development tool and project management tool in one unit. Most of the common project management tool (software development) like PivotalTracker, Asana, Trello, Jira etc are entirely separated from the software development in the sense that keeping progress up-to-date and projects on track requires some additional configurations.</p><p>Zenhub is an agile project management tool inside Github. Its comes with a lot of advantages. It brings project management closer to the code to reduce context switching and increase team productivity. Provides the chance to be connected two or more GitHub repositories to a workspace. Generally, ZenHub works where you need it, either inside GitHub via our browser extension or as a full-featured standalone web app. This focuses on ZenHub via a browser extension.</p><p>Gitlab has it’s own issue board and doesn’t support ZenHub. This means that if you are maintaining your project repo in Gitlab you’ll need to use its issue board rather than ZenHub. You can find out more at <a href="https://about.gitlab.com/blog/2016/08/22/announcing-the-gitlab-issue-board/">https://about.gitlab.com/blog/2016/08/22/announcing-the-gitlab-issue-board/</a></p><h3>Hands-On Practical</h3><ol><li>Visit <a href="https://www.zenhub.com/extension">https://www.zenhub.com/extension</a></li><li>As at the time of writing this article, ZenHub extension is available for chrome and Firefox. For chrome, Click the “available in the chrome webstore&quot; link. For Firefox, click the &quot;install zenhub for mozilla firefox&quot; link.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S426UO80goBZ8cB9wViwoQ.png" /></figure><p>3. Allow ZenHub to access your GitHub account by clicking Authorize zenhubio</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SNZ-4cNj_CeRjYtmzfxJxQ.png" /></figure><p>4. Confirm your GitHub account password, by entering your valid password and click Confirm Password button</p><p>5. Next, you are redirected to ZenHub website. Choose to receive news on ZenHub products, offers and events and then click the “Agree&quot; button to agree to ZenHub’s terms of service and privacy policy.</p><p>6. Head straight to one of your GitHub repositories, you will see a page as shown below briefing you on what ZenHub is all about. Please notice the ZenHub tab beside Pullrequeststab and the blue-pink coloured box with “Head to the Board button”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhJsSQWMSzUVIxO5y-QiQA.png" /></figure><p>7. Next is the Create new Workspace page. A workspace is a space where you and your team works. Add a name, description, optionally you can add other repositories your work with and click &quot;Next&quot; button. See the screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oUi2tHIynqfdmlv3nQkgAg.png" /></figure><p>8. Next is the Workspace setup page. One can set up the workspace depending on the team’s workflow. For regular Scrum and Kanban, click “Complete Board Setup button&quot; to complete the setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gngbk_ioYWb0MlGZKpzVg.png" /></figure><p>Next is the screenshot is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yzrkv-iuwGLcAPuKzY9ojQ.png" /></figure><p>One can easily follow the intro tooltips to get familiar with organising issues, tracking tasks with Epics, learning more about ZenHub’s report feature, and how to invite team members.</p><h3>Conclusion</h3><p>Organizing the project backlog is a critical job for any project team. ZenHub helps teams organize, prioritize, assign, and track tasks across the team. Most importantly, it gives everyone on the team visibility to the backlog and to what their teammates are doing.</p><h3>References</h3><ol><li><a href="https://www.youtube.com/watch?v=TRu7vKCg920">https://www.youtube.com/watch?v=TRu7vKCg920</a></li><li><a href="https://about.gitlab.com/blog/2016/08/22/announcing-the-gitlab-issue-board/">https://about.gitlab.com/blog/2016/08/22/announcing-the-gitlab-issue-board/</a></li><li><a href="https://www.youtube.com/watch?v=UWsJ8tkHAa8">https://www.youtube.com/watch?v=UWsJ8tkHAa8</a></li><li><a href="https://www.zenhub.com/">https://www.zenhub.com/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da46ce7aff9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chingu/zenhub-101-the-essential-guide-da46ce7aff9d">Zenhub 101: The Essential Guide</a> was originally published in <a href="https://medium.com/chingu">Chingu</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Redux Middleware]]></title>
            <link>https://medium.com/chingu/understanding-redux-middleware-5d8fe63aabfb?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d8fe63aabfb</guid>
            <category><![CDATA[redux-middleware]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[middleware]]></category>
            <category><![CDATA[applymiddleware]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Thu, 16 May 2019 16:21:35 GMT</pubDate>
            <atom:updated>2019-05-26T21:32:05.825Z</atom:updated>
            <content:encoded><![CDATA[<h3>Middleware</h3><p>Simply put middleware is a software component which provides services to integrate disparate system together(<a href="https://en.wikipedia.org/wiki/Middleware">Wikipedia</a>). Middleware can also be functions that have access to the <a href="https://expressjs.com/en/4x/api.html#req">request object</a> (req), the <a href="https://expressjs.com/en/4x/api.html#res">response object</a> (res), and the next function in the application’s request-response cycle as stated on <a href="https://expressjs.com/en/guide/writing-middleware.html">Expressjs</a>. See the screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WX3dI2rTieilwLbJebhNhw.png" /><figcaption>Express middleware</figcaption></figure><h3>Redux Middleware</h3><p>Redux middleware is a snippet of code that provides a third-party extension point between dispatching an action and the moment it reaches the reducers.</p><p>See this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXvfJLM7DzJ8uxxC5xRDYg.png" /><figcaption>Note: All these happen within the store( the redux single source of truth). Every middleware has next() that calls the next action in the line.</figcaption></figure><p>It is a way to extend redux with custom functionality. <em>They let you wrap the store’s dispatch method for fun and profit</em>. There are a number of them available to you. They include redux-logger, redux-thunk, redux-promise etc. The redux-thunk extends the functionality of a normal redux action to return a function instead of an object of the new state. Redux-logger extends redux native functionality by introducing a logger to log actions when dispatching them before reducers reduce the state. See the screenshot below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_ZCujxXSolxWWE9vnO62Q.png" /><figcaption>Note: In the left-hand side of the above screenshot, the store dispatches an object ({type: “SOME_EVENT}) while in the right-hand side, the store dispatches a function (() =&gt; {}).</figcaption></figure><h3>ApplyMiddleware</h3><p>This is a function packaged with redux that accepts one or more middlewares and returns a function. It is a store enhancer usually place after every other store enhancer you may use. The screenshot below shows how the applyMiddleware can be used to apply a number middleware to the store dispatch function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9TrJsKR73wUOqxGvw-lzPg.png" /><figcaption>Note: the applyMiddleware enhancer applies middlewares(c, d and others) to the store dispatch function</figcaption></figure><h3>Snippet of Code</h3><p>The snippet of code shown below shows how the applyMiddleware combine two redux middleware(Redux-logger and redux-thunk) and passed into the createStore function to wrap the store’s dispatch.</p><pre>import { createStore, applyMiddleware } from &#39;redux&#39;<br>import rootReducer from &#39;./reducers&#39;<br>import reduxLogger from &#39;redux-logger&#39;<br>import reduxThunk from &#39;redux-thunk&#39;<br><br>const store = createStore(rootReducer, applyMiddleware(reduxLogger, reduxThunk))</pre><p>In Conclusion, redux middleware is a means of extending the redux native functionalities. It wraps the store’s dispatch method for fun and profit. With the help applyMiddleware enhancer, you can apply a number of middlewares to redux store. Here is a block of code by <a href="https://codesandbox.io/s/8k8413v3l0">radutz-san</a> on <a href="https://codesandbox.io/s/lxxx8jj687">Sandbox</a> that briefly demonstrates how middleware, store’s dispatch, applyMiddleware and reducer connect together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d8fe63aabfb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chingu/understanding-redux-middleware-5d8fe63aabfb">Understanding Redux Middleware</a> was originally published in <a href="https://medium.com/chingu">Chingu</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adapting to Boot Camp Challenges]]></title>
            <link>https://medium.com/@abuduabiodunsulaiman/adapting-to-boot-camp-challenges-f5fab52416cd?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5fab52416cd</guid>
            <category><![CDATA[andela-bootcamp-nigeria]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 16:08:59 GMT</pubDate>
            <atom:updated>2018-08-05T07:54:41.899Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*s-driJHEHgw3DEiaYTa1kg.png" /><figcaption>Image source: <a href="https://thesaurus.plus/img/synonyms/147/adaptability.png">https://thesaurus.plus/img/synonyms/147/adaptability.png</a></figcaption></figure><blockquote>“It is not in the still calm of life, or the repose of a pacific station, that great characters are formed. The habits of a vigorous mind are formed in contending with difficulties.” <strong>-Abigail Adams</strong></blockquote><p>According to Gandhi, “Adaptability is not imitation. It means a power of resistance and assimilation.” Managing a crisis situation requires the ability to know which actions to pursue and which one to avoid. Boot camp is a training camp for learning various types of skills. It is designed to make participants ready for a course(most likely jobs). The skills in boot camp are first-hand skills. They are not obsolete. They are skills that the majority lacks. Most of the participants of boot camp are novice one way or the other. They need to learn, unlearn and relearn. Simply put, they need to adapt to the challenges in boot camp. I am a participant of Andela boot camp and here is how I have been adapting.</p><p>Andela boot camp skill set can be categorized into technical skills and soft skills. The technical skills are software development related. They are skills needed by anybody who wants to touch the sky in the IT world. They are Test Driven Development, Code Syntax, Github Repository, Code Understanding and Database Management. While the soft skills are the skills everybody needs as a person. We need them to live a peaceful life. They are Motivation, Commitment, Speaking to be understood, Openness to feedback and progress attempts. As an aspiring Andelan, I needed to learn, unlearn and relearn the skill set in two weeks. The boot camp is so immersive that I have to fully immerse myself in the whole process. I mean I have to strictly follow the dos and don’t of Adaptability.</p><h3>Situation Awareness and Response</h3><p>The biggest secret to being adaptable is understanding the situation or the context of the change(s). In every situation of changes, there are more or less important factors to be considered. Ability to identify them is key to such situations follows by the quick response.</p><p>Recently in the boot camp, I partook in a group activity on Agile methodology where we were asked to demonstrate our understanding of scrum within few hours. The activity was presided by peer learning skill session where we were made to understand the agile methodology (scrum), the situation surrounding it, what a scrum team is and who are the people in a scrum team. When the activity started, we discovered that we could not deliver what the product owner wanted from us as at that time. That is a calamity if money was involved. What we did to resolve that is to communicate the situation to the product owner this to the understanding of the scrum principle and prompt response.</p><h3>Awareness of Strengths and Vulnerabilities</h3><p>One’s strengths are what make him strong and his vulnerabilities are what make him weak. Simply put, the ability to identify oneself is crucial to adapt to changes. Also, part of the awareness of strengths and vulnerabilities principle is to identify who your team or colleagues are. Implementation of this principle can go a long way in the time of confusion.</p><p>I implemented this principle when I was designing my User Interface. My first deliverable, from my own point of view, was terrible. I tried all my possible best, but it did not work. There is a friend of mine who is very good in User interface who later taught me how to use chrome dev tool (inspect.). He actually helped me.Thinking about this, I have a lot of friends but I only met with the right one at the right time.</p><h3>Keep Learning, Developing and Exploring</h3><p>No challenges have been set up to break you but to make you stronger. One who approaches learning with the right mindset would appreciate challenges. Every challenge comes with the lesson(s), it is the challenged who has to learn the lesson, develop his understanding of the challenge and explore more. An adaptable person should be open to new information, ask questions and search for answers where possible.This has been my practice even before the boot camp.</p><p>In conclusion, change is inevitable and adaptability is very important to every human being. When I find myself in the position to adapt, I have my plan approaching the changes, open to new information and always hopeful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5fab52416cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience in the Bootcamp so far]]></title>
            <link>https://medium.com/@abuduabiodunsulaiman/my-experience-in-the-bootcamp-so-far-16060a14878a?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/16060a14878a</guid>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 16:00:44 GMT</pubDate>
            <atom:updated>2018-07-26T16:14:47.392Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*TkUG1BIhnIYgqZFo_3eY1g.png" /></figure><p>The challenges keep on growing on a daily basis, so many things I have to learn and so much effort required from me to put in, I am feeling the pressure and stretches. Ordinarily, I would not engage myself with all the exercises. There is one thing that keeps me moving and that is the statement that says “<strong><em>My efforts will pay</em></strong>”. Failure or success, I would not be the same person I was yesterday. That sounds scary. Does it? You just need to accept that the Software Development unlike every other professions changes every now and then. Yes ! !! !!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*Sik7CzcEqdrkBCbIEh7Mog.png" /></figure><blockquote>So much has not changed about the andela Bootcamp curriculum but the standard of the deliverable has changed. The project rubric contains four challenges. Before the first week of bootcamp, an aspiring andelan should have finished the challenge one and two. These challenges entails the design of the frontend and the backend of an application(My-Diary) without data persistence. An aspiring andelan needed to know how to use Pivotal Tracker, integrate CI tools and what have you.</blockquote><p>So far, the experience has been very fantastic. I am keeping up with the pace. I finished the challenge one and two of the project rubric before the bootcamp started. I have been able to implement the feedback received from my awesome Learning Facilitator Assistant(Funsho Balogun). In the challenge three, I have been able to write the user’s stories and deliver four of the stories.</p><p>However, the challenges are there to spices it up. Among all, receiving and implementation of feedback is the icing on the cake. Ones mind needs to be in the right state to receive feedback. Feedback can be constructive or destructive. Either of them is not meant to destroy you. It is easier said than done. I am actually still coping.</p><p>In conclusion, Andela’s Bootcamp Experience is interesting. I have gained so much that I could not imagine what the next face of the bootcamp has for me.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16060a14878a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beautiful Winston: A Simple and Universal Logger]]></title>
            <link>https://medium.com/chingu/beautiful-winston-a-simple-and-universal-logger-6a2d38c01a69?source=rss-c4b3bd64c255------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a2d38c01a69</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[andela-bootcamp-nigeria]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Sulenchy]]></dc:creator>
            <pubDate>Wed, 25 Jul 2018 11:35:25 GMT</pubDate>
            <atom:updated>2019-05-27T10:44:50.712Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/311/1*LU3RNfJOvQBEohHnUoDMQg.png" /></figure><p>Andela bootcamp like any other coding bootcamps is an intensive program of software development. There are deliverable of required standards bootcampers are required to deliver. One major requirement is that a code base with console.log statement or any commented line of code should not be deployed to production. A node.js application needs a server that can serves files on the go. When a server is started there should be a message confirming the start of the server. The common way developers use to display such message is by using console.log. Having the requirements established, how appropriate can one displays the server start message? Winston came to my rescue.</p><p>Winston is a logger for just about everything. It is designed to be a simple and universal logging library with support for multiple transports. Transport is a storage device for your logs. Each winston logger can have multiple transport configured at different levels (Logging levels). Winston aims to decouple parts of the logging process to make it more flexible and extensible. Using winston logging library is very easy.</p><p>There are ways one can use the library:</p><ol><li>The recommended way to use winston is to create your own logger. The simplest way is to use winston.createLogger</li><li>One may also log directly via the default logger exposed by import winston from &#39;winston&#39; //es6</li></ol><p>Let us explore the second option, using the default logger. The default logger is accessible through the winston npm module directly. Any method that you could call on an instance of a logger is available on the default logger.</p><pre>import winston from &#39;winston&#39;;<br>winston.log(&#39;debug&#39;,&#39;Now my debug message are written to console!&#39;);</pre><p>By default, no transports are set on the default logger. You must add or remove transport via the add() and remove() methods.</p><pre>const files = new wisnton.transports.file({filename: &#39;conmined.log&#39;});<br>const console = new winston.transports.console();<br>winston.add(console);<br>winston.add(files);<br>winston.remove(console);</pre><pre>or do it with one call to configure();</pre><pre>winston.configure({<br>   transports:[<br>      new winston.transports.file({filename: &#39;somefile.log&#39;})<br>   ]<br>});</pre><h3>Hands on Keyboard</h3><p>1. Clone the repo</p><pre>git clone <a href="https://github.com/sulenchy/WinstonGettingStarted">https://github.com/sulenchy/WinstonGettingStarted</a></pre><p>2. Change direction into the winstongettingstarted folder</p><p>cd winstongettingstarted</p><p>3. Install the required dependencies</p><pre>npm install</pre><p>4. Run npm start</p><p>Note: The server starts and displays the start message Example app listening on port 3000using console.log</p><p>5. Press ctrl + c to halt the server running</p><p>6. Run npm run lint</p><p>Note: the eslint flags 1 no-console error</p><p>7. Run npm i wisntonto install winston library. Confirm the installation in your package.json under dependencies object.</p><p>8. Refactor the code in server/app.js as follow:</p><pre>import express from &quot;express&quot;;<br>import winston from &quot;winston&quot;;</pre><pre><strong>const</strong> app = express();</pre><pre>app.get(&quot;/&quot;, (req, res) <strong>=&gt;</strong> res.send(&quot;Hello World!&quot;));</pre><pre>app.listen(3000, () <strong>=&gt;</strong> {<br>winston.log(&quot;info&quot;, &quot;App listening at localhost:3000&quot;);<br>});</pre><p>9. Run npm run lint</p><p>Note: eslint is no longer flagging no-console error</p><p>10. Run npm start</p><p>Now the codebase is ready for production</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a2d38c01a69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chingu/beautiful-winston-a-simple-and-universal-logger-6a2d38c01a69">Beautiful Winston: A Simple and Universal Logger</a> was originally published in <a href="https://medium.com/chingu">Chingu</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>