<?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 Arerosuoghene Wisdom on Medium]]></title>
        <description><![CDATA[Stories by Arerosuoghene Wisdom on Medium]]></description>
        <link>https://medium.com/@itswisdomagain?source=rss-5454fdb188e7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*keOV2oKZRSPHb0yMqw3j9g.jpeg</url>
            <title>Stories by Arerosuoghene Wisdom on Medium</title>
            <link>https://medium.com/@itswisdomagain?source=rss-5454fdb188e7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:11:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@itswisdomagain/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[Git & GitHub — for Newbies]]></title>
            <link>https://medium.com/series/git-github-for-newbies-369950aaee0c?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/369950aaee0c</guid>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 23:29:08 GMT</pubDate>
            <atom:updated>2018-09-01T23:31:28.476Z</atom:updated>
            <content:encoded><![CDATA[<p>Article 1</p><h3>Git 101 — Introduction to Git for Newbies</h3><p>Read: <a href="https://medium.com/@itswisdomagain/git-101-introduction-to-git-for-newbies-bb14f6f9fc1">https://medium.com/@itswisdomagain/git-101-introduction-to-git-for-newbies-bb14f6f9fc1</a></p><p>Article 2</p><h3>GitHub 101 — Introduction to GitHub for Newbies</h3><p>Read: <a href="https://medium.com/@itswisdomagain/github-101-introduction-to-github-for-newbies-efaf46c88406">https://medium.com/@itswisdomagain/github-101-introduction-to-github-for-newbies-efaf46c88406</a></p><p>Article 3</p><h3>Git + GitHub 102 — Working with Branches</h3><p>Coming Soon…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=369950aaee0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub 101 — Introduction to GitHub for Newbies]]></title>
            <link>https://medium.com/@itswisdomagain/github-101-introduction-to-github-for-newbies-efaf46c88406?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/efaf46c88406</guid>
            <category><![CDATA[repositories]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[newbie]]></category>
            <category><![CDATA[version-control]]></category>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 23:24:18 GMT</pubDate>
            <atom:updated>2018-09-01T23:32:30.851Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is the second in a <a href="https://medium.com/series/369950aaee0c">series of articles</a> to explain Git and GitHub in an easier-to-understand manner. <a href="https://medium.com/@itswisdomagain/git-101-introduction-to-git-for-newbies-bb14f6f9fc1">The previous article</a> gave a gentle introduction to Git for Newbies. If you’re not familiar with Git, do us both a favor and check out <a href="https://medium.com/@itswisdomagain/git-101-introduction-to-git-for-newbies-bb14f6f9fc1">the first article</a> before reading this. It’s just about 5 minutes.</p><p>Up to speed? Yas!!! Now, let’s get to the matter. In a hurry? <a href="http://medium.com/p/efaf46c88406#2716">The meat of this matter is here</a>.</p><p><a href="https://medium.com/@itswisdomagain/git-101-introduction-to-git-for-newbies-bb14f6f9fc1">In the last article</a>, we said you can share your “git-tracked” folders (AKA local git repositories) with friends, colleagues and even strangers. What we didn’t say was that GitHub makes that a ton easy.</p><blockquote>Oh oh. Let’s pause for a moment. While this article is primarily focused on GitHub, the same principles apply for any other git hosting platform or service out there. Examples of such other platforms/services are <a href="http://gitlab.com/">GitLab</a> and <a href="http://bitbucket.org/">Bitbucket</a>.</blockquote><p>Okay, let’s continue.</p><p><a href="https://guides.github.com/activities/hello-world/#what"><strong>Github </strong>defines GitHub</a> as “a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere.”</p><p>Simple enough? I hope so. But just in case…</p><blockquote>GitHub helps you keep your “git-tracked” project folder (AKA local git repositories) and all its contents in the cloud so you or anyone else you permit, can access it from anywhere, anytime. Well, basically.</blockquote><p>The most common use of GitHub and other git hosting platforms/services is simply keeping copies of local git repositories in the cloud, so if/when you lose your PC or some other sh*t happens, you don’t have to bite your finger.</p><p>Aside that, there is yet another benefit such platforms/services provide — collaboration! The ability to have others join you in a project either making direct changes to the files or reviewing your work and suggesting improvements, reporting bugs etc. In a subsequent article, we’ll look at how to use GitHub for effective collaboration.</p><p>For now, let’s look at how to synchronize your local repository with GitHub. As you know, synchronization is a 2-way thing. Your local repository sends updates to the remote repositories whenever there’s a change locally (called <strong>pushing</strong>), and you can fetch updates from remote repositories if there’s a change in the cloud that you do not yet have locally (this is called <strong>pulling</strong>).</p><h3>Getting Started with GitHub</h3><p>Head over to <a href="http://github.com/">GitHub</a> and create an account — or login if you already have an account. Then create a new project (or repository). It’s usually better to create new projects without initializing the repository with a README.md file.</p><p>When done, you’ll be given a unique URL for the project that looks like what we have below. Copy it! No, I don’t mean copy the URL below. Copy the URL given to you 😉.</p><pre><a href="https://github.com/itswisdomagain/firebase-auth-secure-way.git">https://github.com/itswisdomagain/firebase-auth-secure-way.git</a></pre><p>Return to your terminal/command prompt and tell Git you want to synchronize your local repository with GitHub. Remember to navigate to your project directory on the terminal/command prompt before executing any git commands. The command you need to connect your local git repository with the cloud repo hosted by GitHub is:</p><pre>git remote add origin <a href="https://github.com/itswisdomagain/firebase-auth-secure-way.git">https://github.com/itswisdomagain/firebase-auth-secure-way.git</a></pre><p>2 things to note. First, the origin keyword you see is just an <strong>identifier</strong>. Git allows you to connect more than 1 <strong>remote</strong> <strong>repository</strong> to your local git setup. Git requires you to give each remote repo (repo is the same thing as repository) a <strong>unique ID</strong>. Its’s common practice to use origin as the identifier for the default remote repository.</p><p>The second thing to note should be obvious, but I’ll just say it. The URL! The command should end with the URL you copied earlier and not the one I used in that example.</p><p>Alright, once you’ve executed that command, Git knows that there is a remote repository that it should sync with. But Git does not automatically sync whenever you make a commit. You have to specifically instruct Git to do so before it does.</p><h4>PUSHING to the cloud</h4><p>To upload your local changes to the remote repository <strong>for the first time</strong>, enter the following instruction on your terminal/command prompt:</p><pre>git push -u origin master</pre><p>The keyword origin in this command is the unique identifier of the remote repository you want to send updates to. The unique ID you set earlier, remember?</p><p>The keyword master indicates the branch in the remote repository you want to push updates to. The default branch is master. Just leave that untouched for now. In the next article, we’ll talk about Branches in Git and GitHub.</p><p>The flag -u stands for set-upstream. It tells Git that it should remember this remote repository ID and branch name for subsequent pushes.</p><p><strong>After that first time</strong>, you can just use the following command to subsequently push local changes to the remote repository:</p><pre>git push</pre><h4>PULLING from the cloud</h4><p>We did say synchronization is a 2-way thing. There are times when the project repo on GitHub contains updates that we do not have locally.</p><p>Maybe you worked on the project from the office and pushed the changes you made to GitHub. And now you want to continue working on the project from your personal PC and you realize you don’t have the latest update in your PC. Oh please, stop copying project files in a flash drive from the office PC to your personal PC and back 🙄🙄.</p><p>Or maybe it was your colleague that pushed the last update to the project repository on GitHub.</p><p>So, fine, someone pushed to GitHub or whatever, point is, you don’t have the latest updates on your current PC. But you have an older update. And your project folder is connected to the remote GitHub repo. No problemo. Let me show you how to update your local repository with changes from GitHub.</p><p>Quite simple really. Just execute the following command in terminal/command prompt:</p><pre>git pull</pre><p>If that doesn’t work out of the box, try:</p><pre>git pull origin master</pre><p>As usual, the origin in this last command is the unique ID of the remote repo while master is the name of the branch we’re pulling from.</p><p>And voila, you now have the updated copy of the project, along with the entire commit history!</p><blockquote><strong>Important note:</strong></blockquote><blockquote>Before you can successfully <strong>push</strong> to, or <strong>pull</strong> from a remote repo, your local repo must have gotten the latest updates in the remote repo. If there’s an update in the remote repo that you had not <strong>pulled</strong>, you’d need to <strong>pull</strong> before you can <strong>push</strong>.</blockquote><p>That’s GitHub in a nutshell. As you might have guessed, Git and GitHub have even more exciting features. Subsequent articles of this series will give attention to them…</p><p>In the meantime, do leave some claps if you enjoyed reading this article. Do not hesitate to drop any thoughts or questions you may have in the comments section.</p><p>Yours truly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efaf46c88406" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git 101 — Introduction to Git for Newbies]]></title>
            <link>https://medium.com/@itswisdomagain/git-101-introduction-to-git-for-newbies-bb14f6f9fc1?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb14f6f9fc1</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[newbie]]></category>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Sat, 01 Sep 2018 23:17:04 GMT</pubDate>
            <atom:updated>2018-09-01T23:32:14.245Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the first in a <a href="https://medium.com/series/369950aaee0c">series of articles</a> to explain Git and GitHub in an easier-to-understand manner. <a href="https://medium.com/@itswisdomagain/github-101-introduction-to-github-for-newbies-efaf46c88406">This is the next article in this series</a>. If you’re in a hurry to get to the meat of this article, <a href="http://medium.com/p/bb14f6f9fc1#61c3">you can skip the preamble</a>.</p><h3>Preamble</h3><p>Over the past 2 years or so, I’ve been actively involved in helping dozens of folks get started in Programming; from organized trainings to post-meetup/event follow-ups. I’ve often had to take out time to explain to many of these ones how to setup Git and get started with GitHub. You see, so many “git getting started” articles I’ve seen seem to complicate things for newbies. So I can’t just direct them to an article and say, go read that and you’ll be good.</p><p>I recently had to explain Git and GitHub to someone and thought, why not put this into an article that I can always refer others to. Anyways… here we are!</p><h3>Git? Is that another name for GitHub?</h3><p>Nope.</p><p><strong>Git</strong> is a <strong>software</strong> that helps you <strong>keep track of changes to files</strong> in a folder on your PC. After making some changes to files in this folder, you can <strong>“commit”</strong> the changes to <strong>Git</strong> for safe-keeping. These changes could be creating, renaming, deleting a file or subfolder; or editing the content of a file.</p><p>You can also share this folder you’re “git-tracking” with others (via a local computer network, for example) and they can also make changes to files in the folder and <strong>“commit”</strong> their changes into the mighty hands of Git for safe-keeping.</p><p>Then, you can turn back the hands of time whenever you need to and view the content of those files <em>as they were</em> at that time in the past. God forbid one of the friends you shared your files with messed things up for you! Oh wait, it was you and not your friend that messed things up! Oh well, we have Git, don’t we?</p><p>Yeah, that’s about it for Git for today. If you want to learn more, you can <a href="https://en.wikipedia.org/wiki/Git">read about Git on Wikipedia</a>.</p><h3>Getting Started with Git</h3><p>We did say Git is a software, so go ahead and <a href="https://git-scm.com/downloads">grab the executable file for your Operating System</a>, install it and come back here to continue gisting with me. Don’t worry, I’ll wait. I’m patient.</p><p>Installed Git? Awesome! Nope? Err, I really recommend you follow each step religiously so you don’t confuse yourself or me. Thanks for understanding.</p><p>If you have Git installed, open terminal (if you’re using Linux or Mac) or command prompt (if using Windows). Please keep your terminal open, we’ll be using it for a while…</p><p>Now let’s tell git 1 or 2 things about you — your name and email really. Git needs those info so it can confidently tie your identity to any commits you make; and then when someone comes asking, <em>who made those changes?</em>, Git can say, oh it was this guy or that lady. Ready to introduce yourself to Git? You’d only have to do it this one time. Punch the following <strong>TWO</strong> instructions into your terminal/command prompt:</p><pre>git config --global user.name “Your Name Comes Here”<br>git config --global user.email you@yourdomain.example.com</pre><p>Done that? Aren’t you just nice! Alright, let’s do what we came here to do — tell Git to track <strong>that folder</strong> that houses our project files. We need to get the path to that our project folder. Sorry, won’t tell you how to do that. But once you have it, send the following command into your terminal/command prompt:</p><pre>cd &lt;path-to-project-folder&gt;</pre><p>You guessed right, that command changes the working directory of your terminal/command prompt to your project directory. Done?</p><p>Okay, command Git to track this folder/directory we just navigated to and watch for file/subfolder changes. Doing so officially turns your project directory into a <strong>local git repository</strong>. <a href="https://medium.com/@itswisdomagain/github-101-introduction-to-github-for-newbies-efaf46c88406">In a subsequent article</a>, we’ll look at how to connect this repository to an <strong>online/cloud/remote repository</strong>. What is a repository you say? <a href="https://www.google.com/search?q=repository+meaning">Ask Google</a>!</p><p>Use the following command to convert your project folder into a local git repository:</p><pre>git init</pre><p>Yay!!! Git is now watching our project folder for changes. But we ain’t done just yet. It is true that Git can now tell us when there’s a change to this folder, but it doesn’t save the changes to the <strong>git repository</strong> automatically. Git is smart, you know. It knows that some file changes are just plain irrelevant and need not be saved. So the onus is on us to tell Git when we’ve made a relevant change and then Git will save the changes to its history bank (the repository). If we don’t tell Git, Git won’t save nothing.</p><p>Before we learn how to instruct Git to save changes, it’s worth pointing out at this time, that you can continue working on your project files. Use your IDE, code editor, file manager or what-have-you to make changes to the files and subfolders in your project directory. When you’ve made important changes, remember to save (or <strong>commit</strong>) them. We’ll talk about how to do that shortly.</p><p>Also worth noting at this point, is that, if you restart your PC or for some other reason, your terminal/command prompt is closed, you do not need to re-execute the git init command.</p><blockquote>I repeat, do not execute git init more than once in a project folder.</blockquote><p>Nothing bad will happen, but it’s just pointless. <strong>You initialize your project directory as a local git repository once and only once</strong>. Subsequently, you can perform other git actions such as committing changes which (I remember) we’ll look at in a bit.</p><p>Final note: always remember to execute git commands in your project directory. If for some reason, your terminal/command prompt is closed, reopen it and navigate back to your project directory before executing git commands. If you try to execute a git command without navigating to your project directory, you’ll get the following error:</p><pre>fatal: Not a git repository</pre><p>Alright, where were we? Ah, I remember… How do we tell Git to save relevant changes? Simple, really. Just like when you want to send multiple files via Bluetooth, you mark/select the files, then you send; we likewise tell Git to mark the files we want to save, then we save.</p><p>You can tell Git to mark certain files for saving. The git add command is responsible for this. At the end of the command, enter the path to the files you want to mark (relative to the project folder), separating each file’s relative path with a space.</p><p>The command below tells git to MARK 2 files for saving (changed_file_1 and changed_file_2 in the subfolder named folder1):</p><pre>git add changed_file_1 folder1/changed_file_2</pre><p>You can also tell Git to <strong>MARK ALL CHANGED/EDITED </strong>files for saving. The code below does just that:</p><pre>git add .</pre><p>There are times when you want to use the git add . command to MARK ALL edited files. <strong>Actually, most times that’s what you should do.</strong> But there may be some files and folders that have no business whatsoever in a git repository. Such files may include IDE autogenerated files/folders and <strong>sensitive configuration files</strong> which you and I know is <strong>not</strong> meant to be seen by everyone. You can tell Git that:</p><blockquote>Hey Git, whenever I say mark all files, what I actually mean is that you should mark all files except <strong>these files</strong>”</blockquote><p>If Git was not smart, it would have replied:</p><blockquote>Say what now? <strong>What files</strong> do you want me to <strong>ignore</strong>?</blockquote><p>But Git is smart. It’s smart enough to know that <strong>there’s a file it can check to find out which files and subfolders you want it to ignore</strong>. So, create that file directly inside your project directory. Do not place that file inside a subfolder! The name of the file should be <strong>“.gitignore”</strong>. If you give it any other name or put the file in a subfolder, Git will just be looking at you like 🙄🙄</p><p>Assuming you’re still with me up to this point, open your .gitignore file and start to enter the name(s) of those files and subfolders you want Git to always ignore even if you tell it to mark all files. Each file/subfolder name should be in a line of its own. When you’re done, remember to save the .gitignore file. (Control + S, anyone? Or is it Cmd + S? Whatever works for you!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*dZVl2IjSo-ZEQPRNWODyXA.png" /><figcaption>Sample .gitignore file</figcaption></figure><p>Whether using a .gitignore file or not, remember that you must always MARK the files you want Git to save before you finally save.</p><p>To finally save the MARKED files to the local repository, enter the following code in your terminal/command prompt:</p><pre>git commit -m &quot;short descriptive message&quot;</pre><p>Did you type that exact code in your terminal/command prompt 🤦‍♂️? I wanted to explain to you that you should change the text in quote to any message that actually briefly describes the changes that you’re about to commit. Oh, just so you know, the write word is <strong>commit</strong>, not save. If we’re all gonna become Git experts, we might as well start using the right terms, shouldn’t we?</p><p>What commit message did you use? This is an example:</p><pre>git commit -m &quot;change login page background color&quot;</pre><blockquote>Just a passing mention, there are conventions (standards) for how to properly write git commit messages. <a href="http://who-t.blogspot.com/2009/12/on-commit-messages.html">Here’s one way to write good commit messages.</a></blockquote><blockquote>Of course, no one’s gonna beat you if you write whatever message you like, but at some point in the future, when you start working on projects in “organized” organizations or with other pros, you’re gonna <strong>need</strong> to write <strong>proper commit messages.</strong></blockquote><p>And that’s it! Git has “saved” <em>(yeah, I know, won’t use it again, I promise)</em> our latest changes to the local repository. Later in the future, we can come back to view these files, as they are right now.</p><p>While Git is in itself a marvel, it is often paired with special kinds of cloud hosting platform like GitHub to enable you keep copies of your local git repositories in the cloud. Doing so enables you to access your project files anytime, anywhere. It also enables you to allow others view your project files, make and commit changes or just review your work.</p><p>You can learn more about such git hosting platforms and how to connect your local repositories to them in the next article: <a href="https://medium.com/@itswisdomagain/github-101-introduction-to-github-for-newbies-efaf46c88406">GitHub 101 — Introduction to GitHub for Newbies</a>.</p><p>That’s it for now. Gracias mucho. If you enjoyed the article, don’t forget to leave some claps.</p><p>Thoughts? Questions? Drop ‘em in the comment section or <a href="/service/mailto:wisdom.arerosuoghene@gmail.com">shoot me an email</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb14f6f9fc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[forLoop Port Harcourt Second Developers’ Meetup]]></title>
            <link>https://medium.com/forloopph/forloop-port-harcourt-second-developers-meetup-b0381bc4cdb8?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0381bc4cdb8</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[for-loop]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[port-harcourt]]></category>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Thu, 23 Aug 2018 21:46:04 GMT</pubDate>
            <atom:updated>2018-08-24T20:24:30.647Z</atom:updated>
            <content:encoded><![CDATA[<p>ForLoop Port Harcourt held her second developer’s meetup five days ago, on Saturday, August 18, 2018.</p><p>The event was lit 💥, the speakers and sessions, intoxicating, and the outcome, thunderous! With over 200 developers and developer-wannabes gathered in one hall for a whole day, the hall suffered from (stack) overflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKEAYJFbfRn4mZp0JdoGNw.jpeg" /><figcaption>The hall was (Stack Overflow), sorry over-filled</figcaption></figure><p>I’d love to tell you all about the event, the sessions, the speakers, the food, the VR (yas!!!! there was VR. Oh wait, what does VR mean? Virtual Reality. If you still don’t get it, <a href="http://www.google.com/search?q=virtual+reality">google it</a>).</p><p>But permit me to first take a minute <em>(hope ya not counting)</em> to give you a little background for this event.</p><h3>Leading up to the event</h3><p>You see, the Port Harcourt tech ecosystem (as with any other tech ecosystem, you’d agree) has a ton of newbies — persons who are just getting into the game. It’s easy for these new ones to get lost when they find themselves in the middle of a technical conversation with more advanced fellows regardless of where the conversation occurs (WhatsApp, Slack or at Meetups).</p><p>So when I was approached by <a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a>, official organizer of forLoop Port Harcourt, <a href="https://medium.com/u/a3c43b80b324">Precious Chukundah</a> and others from the local tech community to champion the organization of a second forLoop event, I wasn’t gonna turn down the opportunity to nurture upcoming artists (sorry, developers 😉).</p><p>Armed with the aforementioned knowledge, and with experiences from previous meetups and events, I proposed that the event be designed to target entry-level to intermediate-level developers in the community. Proposal carried. And Meetup 2.0 — “Newbie to Expert”, was born.</p><p>The event was to cover <strong>Career Choices</strong> in tech, how to use and contribute <strong>Open Source</strong> regardless of whether a developer is an expert or not; and finally the <strong>Tools and Patterns</strong> one must know if he’s to become an expert.</p><p>So let’s modify the event theme a bit. <strong>Newbie to Expert — Career Choices, Open Source, Tools and Patterns.</strong> Gbam! We now have a direction; let’s get a team of volunteers to pull this off.</p><p>Word got out that forLoop Port Harcourt needed volunteers to help organize an event. You guessed right. A ton of folks from the community came forward to join hands and resources to make the event a looping success 😁. These friends went above and beyond for this event. They spared nothing. They withheld nothing.</p><p>For refreshment, we had <a href="https://medium.com/u/7afbc9314260">Daniel Ekpo</a> taking care of the jollof ministry as <a href="https://medium.com/u/bd8c40d3de5e">Sokari Gillis-Harry</a> and <a href="https://medium.com/u/a3c43b80b324">Precious Chukundah</a> piped the drinks into the stream (if you know, you know).</p><p><a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a> and <a href="https://medium.com/u/21c31ec08af1">Damilola Kawojue</a> imported VR magic into the script, <a href="https://medium.com/u/d7d8b229deb1">AYAOSI GODFREY</a> prepared the event budget.</p><p><a href="https://medium.com/u/8dd72ab05803">Praise Sunday</a>, <a href="https://medium.com/u/d892fc9f4a2a">Itolima Esther</a> and almost everyone else took it upon themselves to <a href="https://twitter.com/hashtag/forloopph">tell everyone</a> <a href="http://www.facebook.com/hashtag/forloopph">about the event</a>.</p><p>Victor Ibim, <a href="https://medium.com/u/8afe61d0ee3a">Richard Tamunotonye</a> and <a href="https://medium.com/u/247470ade89b">Peace Ojemeh (Perrie)</a> provided exhilarating promotional graphics at every turn.</p><p>Quite a few others contributed one thing or the other to make forLoop PH Meetup 2.0 a resounding success. Thanks a million everyone! If I didn’t mention your name, nor vex. You know, the brain is not to be trusted sometimes 😉.</p><h3>Event-day, yay!!!</h3><p>Let me start by saying this. This is the first event I’m familiar with where attendees arrived at the venue before the organizers and speakers. Yes, you read that right! Event was to start by 9 AM, before 9, the hall was already half full!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*q9kSr2nRuqr5K0n252xaeQ.jpeg" /><figcaption>Event has not started. Hall was already half-full.</figcaption></figure><blockquote>This is the first event where attendees arrived at the venue before the organizers and speakers!</blockquote><p>Event was supposed to begin with an Introduction to Career Paths by <a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a> but he had to go and make sure that our VR gears will not lose track of their way. So our MC of the day, <a href="https://medium.com/u/d7d8b229deb1">AYAOSI GODFREY</a>, opted to begin the event with talks on <strong>Tools and Patterns</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WvWFZw6qHlzhbBtGxTcxbw.jpeg" /><figcaption><a href="https://medium.com/u/d7d8b229deb1">AYAOSI GODFREY</a> set to kick the off the game</figcaption></figure><p><a href="https://medium.com/u/a9a81c42da8f">Tiku Okoye</a>, a Front end Developer with just a couple months of experience under her belt, took center stage excited to help others just getting into Front end Web development appreciate the need to build faster websites. <a href="https://medium.com/p/my-first-speaking-engagement-from-the-corners-to-center-stage-52fcb31b28c0?source=user_popover">She wrote about her speaking engagement here</a>, but suffice it to say, she effectively demonstrated why a developer should be concerned about page load time and how to improve same. There wasn’t someone who couldn’t relate!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W15RYsBr346hZ7sWAs4gOQ.jpeg" /><figcaption><a href="https://medium.com/u/a9a81c42da8f">Tiku Okoye</a>, buiiilding fire to unleash unto the attendees</figcaption></figure><p><strong>Next up was Obinna Odirionye.</strong> Microsoft Student Partner, Ingressive Ambassador, Github Campus Expert 🙌🙌. Obinna built upon the previous talk and took the attendees through a magnificent <strong>Tool</strong> for site optimization: Webpack. He patiently showed everyone present how to setup and use Webpack in developing awesome Web applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A_bkkKUEzwvtQQUNnC7Slw.jpeg" /><figcaption>Obinna Odirionye, lighting the Webpack Path</figcaption></figure><p><a href="https://medium.com/u/a78b50beb64b">Nsikak Thompson</a>, Lead Android Developer at Start Innovation Hub, Uyo and Co-lead, Google Developer Group, Uyo stepped up to show the way for Android Developers in the house. He talked about how to architect Android apps so they are easier to maintain. He also showed the attendees <strong>Tools and Patterns </strong>they have to be familiar with if they’re to become expert Android developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ilJer-G62qLuHHS_5iFQQ.jpeg" /><figcaption><a href="https://medium.com/u/a78b50beb64b">Nsikak Thompson</a>: So you want to be an expert eh 😂😂😂</figcaption></figure><p><a href="https://medium.com/u/7bf17c234e97">Lawrence Agbani</a> was the last speaker we had for the section on <strong>Tools and Patterns</strong>. <a href="https://medium.com/u/7bf17c234e97">Lawrence</a> came all the way from Lagos, where he works as a Software Team Lead for Konga (yes, the Konga you know!). Aside leading a Software Team at Konga, Lawrence is also a Microsoft Certified Professional! Lawrence clearly explained to all present the difference between Front end and Back end as Career Paths in Web development. He went further to show the <strong>Tools and Patterns</strong> one would need to learn and master in order to start and grow as a Back end developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yDRkiV2U0myQ5_8l9vo_og.jpeg" /><figcaption><a href="https://medium.com/u/7bf17c234e97">Lawrence Agbani</a>: Want to be an expert? Don’t say I didn’t tell you how!</figcaption></figure><p>And then it was time to give the attendees a proper orientation. <a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a> was on hand to efficiently highlight various <strong>Career Paths</strong> tech offers. He took time to explain several, several buzz words flying around in the tech space that sounded like blood-sucking mosquitoes to the newbies. He practically took the attendees by the hand and told them: this is the way, walk in it.</p><p>Everyone in the hall were so thrilled about what they were learning that when asked if they wanted to take a break and do some justice to the food we had, EVERYONE SAID NO! I mean, who does that to our favorite Jollof? Jollof, please accept our sincere apologies. But then, we were only doing what we wanted to do: make sure everyone that came left with the knowledge of how to get started (if they haven’t already) and grow to become experts in their various fields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BTQdpPGnCVj0zWZYcuL9eQ.jpeg" /><figcaption><a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a>: Hehehe, so you people are denying Jollof abi</figcaption></figure><p>Just in case you didn’t notice, that talk by <a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a> was the first of 3 talks on Career Paths. The other 2 would come after the break. But first, let’s talk about what happened during the break…</p><p>Attendees were treated to a plate of remarkable Jollof rice (or fried rice) which was serviced with sizable beef and sprinkled with fried plantain. Hope I didn’t tantalize your intestinal and gastric elements 😁😁. Oh, there was an <em>array</em> of soft drinks to grease the tongue and throat and allow everyone <em>push</em> the food to their stomach <em>repo</em> seamlessly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdpdj8tI9-pWsDV3wvfHnQ.jpeg" /><figcaption>No tech event is complete without jollof</figcaption></figure><p>Still on the break matter, many attendees were given their very first VR treat onsite. Attendees were obviously extremely elated, playing different VR games. Shhh, come closer, bring you ear. Don’t tell anyone I told you, but some persons literally thought they could fly 😂😂😂.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_x2pyBGLP9uqyfRApRFsw.png" /></figure><p>Okay, break over. It haf do. I know say you nor want make the break finish 😂😂😂. But on a more serious note, some would think that a lot of persons will be heading home after eating this kain sweet Jollof rice. Some others would think it’s gonna take a lot of work to get the attendees to gather back in the hall with VR games actively going on just outside the door.</p><p>Shocker! We only had to announce once that it was break over. And gbam! everywhere was full again. Yup, nothing’s wrong with your eyes, you read that correctly. THE HALL WAS FULL! These guys really mean this business, no joke!</p><p>Our first speaker after the break was <a href="https://medium.com/u/a3c43b80b324">Precious Chukundah</a>, a member of the Node.js Africa board and CEO of Unicorn.ng. He took on from where <a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a> left off, showing attendees what they must do if they really, really want to become experts: <strong>Volunteer!!</strong> In a talk titled, Volunteer, Learn, Grow, <a href="https://medium.com/u/a3c43b80b324">Precious</a> shared with the attendees how volunteering in various organizations such as IONS Group, GDG Port Harcourt, Tech Port Harcourt, and more helped him to grow personally. He encouraged all in attendance to highly value volunteering opportunities if they are to become experts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Q3HoW9TYdaaP7f_0aUe7w.jpeg" /><figcaption><a href="https://medium.com/u/a3c43b80b324">Precious Chukundah</a>: You don’t want to volunteer, but you want to grow eh. Brother, bhet why?</figcaption></figure><p>When we were sure that the excitement from the VR “session” had cooled down a little (I mean, that’s as much as we can expect), <a href="https://medium.com/u/21c31ec08af1">Damilola Kawojue</a> bounced to the stage to show all of us the enormous potential and applications of VR tech. In his section, he exposed how VR technology can be used in various industries and more importantly (I guess?), how developers can build VR solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RjYttiEKFrsog5y2zHwviQ.jpeg" /><figcaption><a href="https://medium.com/u/21c31ec08af1">Damilola Kawojue</a>: UNREAL . IS . REAL</figcaption></figure><p>The event concluded with a no-nonsense talk on Open Sourcing hammered on by the host and organizer, <a href="https://medium.com/u/5454fdb188e7">Arerosuoghene Wisdom</a>. In his talk, .. (oh wait, that’s me 🤦‍♂️). Let’s go again… In the last talk, I helped everyone in attendance to understand the role Open Source can play in a developer’s career. I also explained that one need not be an “expert” or “world class” to contribute to Open Source. It was during this session that I mentioned a quote that has <a href="https://twitter.com/techcreekng/status/1031465083925417984">pretty much gone viral</a>:</p><blockquote>Done is better than perfect</blockquote><p>Attendees were encouraged to worry less about being perfect, worry more about getting things done and not shy away from sharing the little they know — in the form of contributions to Open Source projects and in the form of article writing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJw-dz_TdNtg1FvE47vWXQ.jpeg" /><figcaption><a href="https://medium.com/u/5454fdb188e7">Arerosuoghene Wisdom</a>: Studying Open Source codes can help you grow</figcaption></figure><p>Aside from those talks, the attendees were also treated to 2 panel sessions where they had the opportunity to speak with experts in the room and ask them questions based on the various talks and well, anything else.</p><p>The panel sessions had all the speakers as panelists with 2 other guest panelists in the persons of <a href="https://medium.com/u/247470ade89b">Peace Ojemeh (Perrie)</a>, Open Sourcerer and Designer at SugarLabs and <a href="https://medium.com/u/d88987fc94cb">Agiri Abraham</a>, another solid Open Sourcerer and Chairman of Node.js Africa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brItBZnpHiGRNgIzLK8pPw.png" /><figcaption>Panel Session on Career Paths and Open Sourcing. L-R: <a href="https://medium.com/u/a3c43b80b324">Precious Chukundah</a>, <a href="https://medium.com/u/13377e874ef1">Lucas Bruce</a>, <a href="https://medium.com/u/d88987fc94cb">Agiri Abraham</a>, <a href="https://medium.com/u/5454fdb188e7">Arerosuoghene Wisdom</a>, <a href="https://medium.com/u/247470ade89b">Peace Ojemeh (Perrie)</a>, <a href="https://medium.com/u/21c31ec08af1">Damilola Kawojue</a></figcaption></figure><p>I could go on and on and on about the event. But we both know we don’t have forever to spend here. So let’s leave it at this: forLoop PH Meetup 2.0 was terrific! 🔥🔥🔥 everywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-1MZEpkvLVfsZHM28FEOg.jpeg" /><figcaption>Excitement in the air as the event ended</figcaption></figure><h3>After the event</h3><p>Shortly after the event ended and even days later, speakers and attendees stormed social media to applaud the magnificence of the event. Just in case you don’t believe me, just look at those pictures. If you still don’t believe me, <a href="https://twitter.com/hashtag/forloopph">ask twitter</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YuxKAjoWCUxdy0sbafUoA.png" /><figcaption>What people had to say about the event…</figcaption></figure><p>It still hasn’t ended o. Just when we thought the fire would start burning low gradually, we got a surprise! The excitement had spread so far that someone in Lagos who was supposed to speak at the event but could not make it for 1 or 2 reasons, sent in a message.</p><blockquote>Please permit me to give an attendee a year free subscription on <a href="http://egghead.io/">egghead</a> worth more than $250</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*I-NYkNOcs5C0VBkTwyeNZg.png" /></figure><p>Like seriously!!!? Isn’t this just the best news ever! Almost immediately, I fired up gmail, sent an email to all attendees asking them to write about their experience at forLoop PH Meetup 2.0 for a chance to win this prize.</p><p>As I write this article, some attendees <a href="https://medium.com/@kennethmichael11/my-experience-with-forloop-portharcourt-2-0-ed68b3f485ad">have</a> <a href="https://medium.com/@godspowercanyaogu/forloop-2-0-the-journey-and-the-experience-b5de6cf99a08">published</a> <a href="https://medium.com/@bigpreshy/how-forloopph-motivated-me-bc0533c834b3">exhilarating</a> <a href="https://medium.com/@ayodejisokan/my-first-tech-meet-up-92ed7908b7a3">articles</a> <a href="https://medium.com/@obiomaobijiaku/my-forloopph-meetup-2-0-experience-7de6cc76ae0">already</a> and others are still cleaning theirs up, getting ready to publish. Sooner than later, we’ll have all these articles on the <a href="http://medium.com/forloopph">forLoop PH medium publication</a>. You can check them now (and/or later) to read these articles.</p><p>If you attended the event, and you’re wondering how to snatch this price, check out <a href="https://twitter.com/forLoopPH/status/1031685015917273090">this thread on Twitter</a>.</p><p>Alright!!! That’s it from me for now. Were you at the event? Did this article touch you? Leave your thoughts in the comment section. And don’t forget to clap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0381bc4cdb8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/forloopph/forloop-port-harcourt-second-developers-meetup-b0381bc4cdb8">forLoop Port Harcourt Second Developers’ Meetup</a> was originally published in <a href="https://medium.com/forloopph">ForLoopPH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Firebase Authentication — The secure way]]></title>
            <link>https://medium.com/front-end-weekly/firebase-authentication-the-secure-way-a5d135c22b41?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5d135c22b41</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[firebaseauthentication]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Sun, 15 Oct 2017 20:53:37 GMT</pubDate>
            <atom:updated>2017-10-15T20:53:37.818Z</atom:updated>
            <content:encoded><![CDATA[<p>Authentication is a very important feature of sensitive applications — web, mobile or desktop. Authentication often goes hand in hand with Authorization; whereas the former is used to <em>VERIFY THE IDENTITY</em> of a user of a platform, the latter is used to permit or reject <em>ACCESS</em> to resources based on the identity of the entity requesting the resource.</p><p>Firebase helps developers to easily and quickly implement authentication logic in their applications, giving them time and room to focus on other more platform-specific logic. Every productive developer should want to take this approach.</p><p>The default approach to using Firebase Authentication though has a security risk which can be mitigated. What is this default implementation approach and what is the risk associated with it? What can be done to mitigate this risk?</p><h3>The default approach</h3><p>AUTHENTICATION is implemented using the client SDKs for Android, iOS or Web client SDKs.</p><p>AUTHORIZATION is done on the server using the Firebase Admin SDK for Node.js, Python, Java or GO.</p><h3>The security risk</h3><p>The aim of authentication is to <em>AFFIRMATIVELY</em> VERIFY THE IDENTITY OF USERS. This aim can be easily defeated in client applications. Client applications can be easily modified; and when you entrust the entire AUTHENTICATION process to a client application, you expose your authentication logic to the world and it doesn’t require a lot of smarts to weaken the authentication layer by modifying the client application.</p><p>With Firebase, one need not <em>modify</em> the client application; just grab the keys and you’re good to go. And your server could be easily fooled into serving requests for and permitting resources to a user that was not properly authorized.</p><h3>Mitigating the risk</h3><p>Move core authentication logic to your server!</p><h3>How can this be done?</h3><p>This is actually an abstract for a talk I intend to give at GDG DevFest 2017 in Aba and Ibadan 😃 . I’ll update <a href="https://github.com/itswisdomagain/firebase-auth-secure-way">this repo</a> with slides, guides and perhaps sample codes subsequently.</p><p>In the meantime, feel free to examine <a href="https://github.com/ThisIsRudigo/firebaseauth">this library</a> for implementing firebase authentication on a node js server environment.</p><h3>Extras</h3><p>Learn how to use Firebase REST to extend the power of Firebase Authentication to yet officially un-supported server-side languages like PHP and ASP.</p><h3>Why I’m an authority on this topic</h3><p>I’ve delved pretty deep into Firebase Authentication</p><ul><li>Contributor to <a href="https://github.com/step-up-labs/firebase-authentication-dotnet">Firebase Authentication for .NET SDK</a></li><li>Wrote <a href="https://github.com/ThisIsRudigo/firebaseauth">Server-side Firebase Authentication for Node.js SDK</a></li><li>Currently building a Server-side Firebase Authentication for Java SDK with a friend and colleague (<a href="https://medium.com/u/bd8c40d3de5e">Sokari Gillis-Harry</a>) as part of a project: n<a href="https://admin.nearbuy.ng/">earbuy.ng</a></li></ul><h3>About me</h3><p>I’m an avid learner, and a fervent teacher.</p><h3>I call myself a</h3><ul><li>#ChangeArchitect because I can’t stay somewhere without seeking to improve matters;</li><li>#WideStack Developer because I spent the better part of my last 4–5 years gathering knowledge and experience on various programming languages, technologies, tools and stacks.</li><li>No one who knows me debate those titles 😏</li></ul><h3>I build for</h3><p><strong>The web</strong></p><ul><li>Front end with Bootsrap, jQuery and Angular</li><li>Back end with PHP, ASP and Node js (Node js is my personal favorite)</li></ul><p><strong>Android</strong></p><ul><li>Primary language — Java</li><li>Primary IDE — Android Studio</li><li>Also build with Xamarin and Android Studio</li><li>A big fan of Kotlin but I don’t use it much yet</li></ul><p><strong>iOS</strong></p><ul><li>With Swift and Xcode</li><li>With Xamarin and Visual Studio</li></ul><h3>I’ve built apps for</h3><ul><li>Blackberry 7.1</li><li>Windows Phones</li></ul><h3>Disclaimer</h3><p>Thoughts and opinions shared are solely mine. This article was inspired by a conversation with the fireman himself, <a href="https://medium.com/u/bd8c40d3de5e">Sokari Gillis-Harry</a> on this topic. Supporting and/or contrary thoughts are most welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5d135c22b41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/front-end-weekly/firebase-authentication-the-secure-way-a5d135c22b41">Firebase Authentication — The secure way</a> was originally published in <a href="https://medium.com/front-end-weekly">Frontend Weekly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech talent in Port Harcourt — A wake up call]]></title>
            <link>https://medium.com/techphc/tech-talent-in-port-harcourt-a-wake-up-call-2830b7db4ce1?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2830b7db4ce1</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[port-harcourt]]></category>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Mon, 24 Jul 2017 13:15:07 GMT</pubDate>
            <atom:updated>2017-07-24T13:15:07.492Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tech talent in Port Harcourt — A wake up call</h3><p><strong>There are a surprisingly good number of professional and expert developers in Port Harcourt.</strong> I’ve been part of the Port Harcourt tech and startup ecosystem (please let’s not get into the debate of whether or not there really exist an ecosystem) for only about 2 years now. And I’ve heard about, and met a handful of great developers and software engineers (yes, I mean <strong>Software Engineers</strong>).</p><p>There’s been a problem however: <strong>Visibility</strong>. There’s no platform for these great and wonderful fellows to connect, interact, network and train younger ones. There are what I prefer to call clusters but no consortium exists to drive engagement amongst these clusters. But that’s just one manifestation of the visibility problem.</p><p>Another area this problem of visibility rears it’s very “un-beautiful” head is in business/job attraction. I’m tired of people getting surprised at what I can do “<em>in Port Harcourt</em>” (as if nothing good can come out of Bethlehem, I mean, Port Harcourt). And to think that there are folks with even more magical skills here! An unfortunate consequence of this problem is that most local businesses 1) do not think <strong>first</strong> to patronize local tech solution providers and/or 2) do not have confidence in what we can do here! SMH.</p><p>Not surprisingly though, a lot of us developers, startup founders and entrepreneurs are bothered with this visibility issue and have independently sort ways to address the challenge.</p><p>This was what brought some developers from a number of tech communities (the Google Developer Group, Microsoft User Group, PH Dev Connect and others — new and pro alike) and startup founders together on Saturday June 24, 2017.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLGcs5ViT4QQ7HhNzeJAew.jpeg" /><figcaption>Developers, newbies and entrepreneurs discussing the ecosystem</figcaption></figure><p>The meetup was a follow up of a conversation on the GDG PH whatsapp group around the topic of boosting tech visibility in the region. Although the initial conversation was geared towards the organization of a pivotal tech event, the discussion that ensued at the meeting exposed other avenues to help us achieve our goals.</p><p>But first. What is the goal? <strong>“Why do we need an event?”</strong>, asked Sokari Gillis-Harry, founder of <a href="http://www.mabiri.com/">Mabiri</a>, a startup that helps shoppers find and purchase items from shops around them.</p><blockquote>Joshua Joshua, a Microsoft Student Partner and the face behind most Microsoft-related happenings in the South South region of Nigeria, hinted at the need for <strong><em>consolidating the fragmented tech ecosystem</em></strong> in Port Harcourt. In one of his comments, Joshua suggested that we hold a round table meeting of key tech figures in as many tech clusters in Port Harcourt.</blockquote><blockquote>Blessing Anthony, an upcoming developer recommended that provisions be made to accommodate the younger, less experienced breed of developers; to assist them in their quest to becoming world class. Her comments exposed the need to <strong><em>constructively engage younger developers</em></strong> in our plans.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q5TtQQ2DGsAU72U9hNvl1A.jpeg" /><figcaption>Lawrence Agbani (Konga) executing sense.toString();</figcaption></figure><blockquote>Lawrence Agbani, a Software Engineer at Konga proposed that we organize an hackathon, that could span days, possibly a week; at the end of which, we invite businesses together and demonstrate the works of our hands in a bid to <strong><em>redirect the focus of Port Harcourt businesses towards home-grown tech talent</em></strong>.</blockquote><p>These and other thoughts that were aired during the meeting were discussed at length. All in attendance agreed that our common goal should be to</p><ol><li>Consolidate the different clusters of developers — newbies and pros</li><li>Attract the attention of local businesses towards home-grown tech talent</li></ol><p>With that consensus, our convergence acquired direction. We know what we want to do, what we will like to see happen. What next?</p><blockquote>Wisdom Arerosuoghene of <a href="https://www.rudigo.com/">Rudigo Limited</a> , a programming talent accelerator and incubator suggested that we return to our various destinations and clusters; and think of ways we can achieve our common objectives. We recognize that there is no simple solution; there is not necessarily a right or wrong approach; and others have been down this road with limited success. We also know that as individuals and groups, some of us had given thoughts to these challenges and have concocted possible redresses.</blockquote><p><strong>TAKE HOME</strong>: Everyone in attendance was encouraged to ponder over what was discussed and send in their ideas on how best they think we can accomplish our goals. Such suggestions would be most appreciated if the sender goes further than just dropping his suggestion. Including <strong>the rationales behind each proposal, the perceived pros and cons of each suggestion</strong> will better equip us all to think along with the sender and better appreciate how the suggestion helps to address our goals.</p><p>A web/mobile platform is currently being designed by volunteers, for this purpose; to enable us share thoughts and ideas virtually till we next converge. If you’d like to be added to this brainstorming arrangement, please drop a comment below or send an email to wisdom@rudigo.com or danitto88@gmail.com.</p><p>I’ll update this article with links to progress reports as we continue this journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2830b7db4ce1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techphc/tech-talent-in-port-harcourt-a-wake-up-call-2830b7db4ce1">Tech talent in Port Harcourt — A wake up call</a> was originally published in <a href="https://medium.com/techphc">techphc</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing Better Android Apps]]></title>
            <link>https://medium.com/@itswisdomagain/writing-better-android-apps-bfac8b8a921e?source=rss-5454fdb188e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfac8b8a921e</guid>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[udacity]]></category>
            <category><![CDATA[alcs]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Arerosuoghene Wisdom]]></dc:creator>
            <pubDate>Tue, 04 Jul 2017 10:38:38 GMT</pubDate>
            <atom:updated>2018-08-29T06:41:56.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iEmSjQk6DUR2hBKMLXnr3A.jpeg" /><figcaption>How cool is your app?</figcaption></figure><p>If you’ve been writing android apps for a long time or you just begun the learning process, you’ll no doubt find that there are always new things to learn; better, smarter ways of doing the things you already know how to do.</p><p>That’s what I’ve learnt from just my first project that is part of the <a href="https://medium.com/u/2929690a28fb">Udacity</a> <a href="https://www.udacity.com/course/associate-android-developer-fast-track--nd818">Associate Android Developer Fast Track Nanodegree Program</a>; thanks to <a href="https://medium.com/u/a4d81c24b23">Andela</a>’s ALC initiative.</p><p>The submitted source code for the project is <a href="https://github.com/itswisdomagain/Popular-Movies-Stage-1">hosted on github</a>. To get the app working on your device or emulator, read the todo instructions in the strings.xml file.</p><p>Now, onto the lessons from <a href="https://review.udacity.com/#!/reviews/586870/shared">the review</a> of my submitted project. You may have known these before but never really used them. Or you may be learning about some of these tips for the first time. Whatever the case, I hope this read is worth your while. I tried to make these points as concise as possible so I don’t bore the PROs and still offer enough information to carry newbies along.</p><ol><li>Making UI changes with code for different screen orientations.<br>You can override the onConfigurationChanged method of the Activity class to handle changes in device orientation.<br>To stop such changes from restarting your activity, add this property (android:configChanges=”orientation|screenSize”) to your activity declaration in your app’s manifest.<br>You can also accomplish your objectives directly in the onCreate method without overriding the method mentioned above.</li><li>Define AsyncTask classes in separate files. Makes your code more readable, as against nesting an AsyncTask in another class (say an activity class). <a href="http://stackoverflow.com/questions/15487807/android-development-having-an-asynctask-in-a-separate-class-file">More on stackoverflow</a>.</li><li>About making network/API calls with AsyncTask: not the best idea for production apps, particularly for complex projects. Here are some <a href="http://blog.danlew.net/2014/06/21/the-hidden-pitfalls-of-asynctask/">why</a> and <a href="http://simonvt.net/2014/04/17/asynctask-is-bad-and-you-should-feel-bad/">why</a>.<br>Libraries exist that handle the heavy-lifting required to make proper, efficient network/API calls like <a href="http://developer.android.com/training/volley/index.html">Volley</a> or <a href="https://github.com/square/retrofit">Retrofit</a>. I’ve used <a href="https://github.com/jaksab/EasyNetwork">EasyNet</a> recently.<br>You can find other discussions around this topic <a href="http://www.truiton.com/2015/02/android-volley-vs-asynctask-better-approach/">here</a>, <a href="http://instructure.github.io/blog/2013/12/09/volley-vs-retrofit/">here</a> and <a href="http://stackoverflow.com/questions/16902716/comparison-of-android-networking-libraries-okhttp-retrofit-volley?lq=1">here</a>. Ever heard of <a href="https://github.com/ReactiveX/RxAndroid">RxAndroid</a>? It’s based on a concept called Reactive Programming. Learn about it <a href="http://www.andreamaglie.com/rxjava-android-where-to-start/">here (where to start)</a>, <a href="http://blog.danlew.net/2014/09/15/grokking-rxjava-part-1/">here (part 1 of several articles, links to other parts)</a>, <a href="http://blog.feedpresso.com/2016/01/25/why-you-should-use-rxjava-in-android-a-short-introduction-to-rxjava.html">here (why use it)</a>, <a href="http://blog.stablekernel.com/replace-asynctask-asynctaskloader-rx-observable-rxjava-android-patterns/">here (comparison with AsyncTask and AsyncTaskLoader)</a>, and <a href="http://fedepaol.github.io/blog/2015/09/13/testing-rxjava-observables-subscriptions/">here (working with unit testing)</a>.<br>Go <a href="https://medium.freecodecamp.com/rxandroid-and-retrofit-2-0-66dc52725fff">here</a>, <a href="https://www.captechconsulting.com/blogs/a-mvp-approach-to-lifecycle-safe-requests-with-retrofit-20-and-rxjava">here </a>and <a href="http://randomdotnext.com/retrofit-rxjava/">here</a> to learn how to use RxAndroid with Retrofit.</li><li>Do you use the <strong>design support library widgets</strong>? They can make your UI really nice and improve the user experience. Yes! There are articles about them <a href="https://developer.android.com/training/material/index.html">here</a>, <a href="https://guides.codepath.com/android/Design-Support-Library">here</a> and <a href="https://android-developers.googleblog.com/2015/05/android-design-support-library.html">here</a>. #smiles.</li><li>Never, ever do this at home! Lol. Yeah, I’m joking. But really, <strong>there is a safe way to store API keys</strong>: using build.gradle, not strings.xml. Stackoverflow has discussions about this <a href="https://stackoverflow.com/questions/33134031/is-there-a-safe-way-to-manage-api-keys">here</a> and <a href="https://stackoverflow.com/questions/35722904/saving-the-api-key-in-gradle-properties">here</a>.</li><li>You can make use of the library <a href="http://jakewharton.github.io/butterknife/">ButterKnife</a> for <strong>view injection</strong>. This helps in reducing a lot of boilerplate code (eg. the repetitive findViewById calls). Learn how to use it <a href="https://guides.codepath.com/android/Reducing-View-Boilerplate-with-Butterknife">here</a>.</li></ol><p>Okay, that’s mostly it from me. Did you learn something new?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfac8b8a921e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>