<?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 Favor Oriabure on Medium]]></title>
        <description><![CDATA[Stories by Favor Oriabure on Medium]]></description>
        <link>https://medium.com/@favoriabs?source=rss-8c948b303319------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*D5Yci2QQA5BXs-nDjPY7JQ.jpeg</url>
            <title>Stories by Favor Oriabure on Medium</title>
            <link>https://medium.com/@favoriabs?source=rss-8c948b303319------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:52:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@favoriabs/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[The art of arriving.]]></title>
            <link>https://medium.com/@favoriabs/the-art-of-arriving-e8fa4d0044eb?source=rss-8c948b303319------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8fa4d0044eb</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[choices]]></category>
            <category><![CDATA[journey-of-life]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Favor Oriabure]]></dc:creator>
            <pubDate>Sat, 25 May 2019 09:46:33 GMT</pubDate>
            <atom:updated>2019-05-25T09:46:33.320Z</atom:updated>
            <content:encoded><![CDATA[<p>The art of arriving.</p><p>From the Moon to Planet Mars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*afIQrxKPZUnKEAA5" /><figcaption>Photo by <a href="https://unsplash.com/@taynicole0630?utm_source=medium&amp;utm_medium=referral">Taylor Nicole</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You have always wanted to move to New York, see its tall buildings, the statue of Liberty, Maddison Square Garden, and the likes. All resources you have are geared towards this move, energy levels, money and time. A stroll into your room, exposes your “obsession” with New York, the pictures on the wall give you away. You finally get to New York and after some time there, New York is no longer enough for you, now you’ve got some Casino locations of Las Vegas on your walls now. Sounds familiar?</p><p>It would be the weirdest of experiences to keep traveling and never arrive, the thought of it might make you go nuts. Imagine going from Portugal to Spain and from Spain to France, France to Switzerland and then to Italy and going on like that (I had to look up the map of Europe to at least get a logical sequential direction). Yet, irrespective of how much time is spent at these locations there is not just a feeling of arrival or a “long term” decision.</p><p>What’s worse will be one who keeps moving his destination every time he reaches it. Either he is not satisfied by that location or he wants to see more destinations like his dream one.</p><p>Yet it seems like this is how we live life, journeying day to day to a destination we believe and hope will bring ultimate satisfaction for us, yet when we get to that destination, we discover we are not satisfied for a couple of reasons. Maybe the destination isn’t as great as you thought it would be, or the people there are not as receptive as your previous settlement. For whatever reason we just keep moving. You get the job in the city after living in that small town for most of your life, your dreams have come true but after two years, we want to move back because we do not like the noise of the trains or the buzz or maybe the night life.</p><p>This “phenomenon” can be seen in every sphere and in billions of humans. The truth is, <strong>very few have mastered the art of arriving</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*erQlA_i7n_atJJf0" /><figcaption>Photo by <a href="https://unsplash.com/@eutahm?utm_source=medium&amp;utm_medium=referral">Eutah Mizushima</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Arriving </strong>is not a stop in that sense, or a lack of movement, but a place of <strong>satisfaction</strong> and <strong>purpose</strong>. Do not misunderstand this for been lukewarm or mediocre, this is a situation where irrespective of the location you are making the best use of the experiences you are gaining and processes you are going through.</p><p><strong>A destination doesn’t always give you the satisfaction you want</strong>. So you can’t base your happiness on a place. It’s how we are wired, Man went to the moon in 1969, now we are planning on going to Mars. That finish line will always be shifted.</p><p>Irrespective of where your journey leads you, you can be satisfied, knowing that the process is as important as the destination, maybe more important.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8fa4d0044eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2+ Years of  Software Development and Lessons i have learnt.]]></title>
            <link>https://medium.com/@favoriabs/2-years-of-software-development-and-lessons-i-have-learnt-9f03815c7deb?source=rss-8c948b303319------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f03815c7deb</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Favor Oriabure]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 12:06:08 GMT</pubDate>
            <atom:updated>2019-03-18T12:06:08.089Z</atom:updated>
            <content:encoded><![CDATA[<h3>2+ Years of Software Development and Lessons I have learnt.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y_OK300o__Bo_dT6" /><figcaption>Photo by <a href="https://unsplash.com/@dre0316?utm_source=medium&amp;utm_medium=referral">Andre Hunter</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It has been almost 3 years of professional software development and it has been a fun journey so far. It has had its “highs” and “lows” which has contributed to this rich journey I am still on.</p><p>I have a CS degree from a “prestigious” Nigerian Federal university, but I never learnt how to code there. I was always interested in programming though, did well in all my programming courses, but the environment wasn’t suitable to learn that. I got a computer in my third year, still i didn’t have as much drive to learn on my own. In my service year (a 1 year compulsory activity where fresh graduates are posted to other states to serve the country), I was blessed to serve in a hub which gave me the opportunities I needed to start a career in Software Development.</p><p>I have learnt a ton of code and engineering practices in this time (obviously there is still tons to learn), but what has stuck with me the most, are the life lessons I have learnt in this process. Here are a few:</p><h4><strong>Stick to the Process</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jv8M3iT1mjoyqqKt" /><figcaption>Photo by <a href="https://unsplash.com/@ar_shad?utm_source=medium&amp;utm_medium=referral">Arshad Pooloo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The process stage of a product is one of the most boring stages that product goes through. It seems like it doesn’t really know what it was going to be. It is just here and there, going through the heat from the furnace, and pains from the hammer. What we tend to forget though, is that in that process, that product learns a lot about its abilities and use. The finished product always looks great and spotless, but the process contributes fully to what the product becomes. There is no easy way to become a great software developer. You are not going to become a <a href="https://medium.com/u/d694c31ce941">Taylor Otwell</a> in a year. It takes time to arrive at that finished product you are looking to be. The process is learning. It never stops, and you must never get tired of it. Your process might be painful, or boring, but in all, stick to it.</p><h4>Stick to something</h4><p>One mistake I see many people make is jump around new technologies, frameworks or even languages. Your quest for learning should not drive you to jump from language A to B to C, because you feel that A is the most talked about on social media or B is quite boring. Learning won’t happen like that, in fact it sets a precedence for you to move again when any of your previous “conditions” come up. Once you master a technology, grabbing a new one is far easier. Apart from few concepts, programming languages are more similar than different. Instead of jumping on the bandwagon of learning everything and becoming a master at none, take some more time with that language or framework and master it before you move.</p><h4>Learn From Mistakes.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rHqBRA2_Ppwc__WA" /><figcaption>Photo by <a href="https://unsplash.com/@chuttersnap?utm_source=medium&amp;utm_medium=referral">chuttersnap</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Nobody likes mistakes, yet nobody does without them. You will make mistakes, and you must be ready to handle them properly. You will make ridiculous ones too, ones that might make you look dumb, but you can’t be fazed by little bumps on the journey. In my first month as a programmer, I was just learning the Laravel framework. I remember I was in a team of three on a School Management System, and we couldn’t understand why our migration would not run. We had spent hours on this issue when someone told us that the foreign key we defined in a table didn’t even have a base table. We felt so ridiculous, but it did make sense, and we learnt from that. The most important thing you can do when you make a mistake is learn from it and improve yourself. It is also important to note that you don’t have to learn only from your mistakes, you should learn from the mistakes of others too.</p><h4>Be Patient With yourself.</h4><p>As a follow up, you must give yourself time. When you feel dumb, or you feel you are taking so much time, remain patient. Life is a journey, not a sprint. The importance of being patient with yourself is that you are ready to give yourself another go at a task, a concept or even a company. Give yourself time to grow. No plant grows to maturity in one day. It takes time, takes weeding, takes nurturing, sunlight, water etc. One day eventually, the plant brings forth fruit. Growth takes time, give yourself time.</p><h4>Experience is important.</h4><p>One major bullet point seen in every job ad, is the years of experience the individual has before he can get that job. Why is this important? It is obviously a big deal that it appears in all job ads (especially software development ones). It is actually not about the time you have been developing, it is about the amount of work you have done in that time. It why it is called experience, they basically want to know how much you have experienced in that field. What differentiates a senior developer from a junior one, it is not skill necessarily, its that fact that the senior dev can lead and direct the junior dev properly because that senior dev has experienced what the junior developer is currently experiencing.</p><h4>Have a community around you.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EJOf7RECwKvkpRAD" /><figcaption>Photo by <a href="https://unsplash.com/@daanstevens?utm_source=medium&amp;utm_medium=referral">Daan Stevens</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>How important this is. It doesn’t have to be the open source or a forLoop community, just have a community. It might be 2 friends going through the same process as you, or a programming club or whatever, just have people around you who are ready to help any time you are stuck. Of course, it is a two way street, you must also be ready to help. If you think you will never get stuck, I assure you, you will. Communities exist online also, with many people ready to help every time. <a href="https://stackoverflow.com/">Stackoverflow</a> has been an important part of any programmers life. If you are a Laravel developer, <a href="https://laracasts.com/">Laracasts</a> would help a lot too.</p><p>This journey is not done yet, there is still a lot more to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f03815c7deb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Composer Install vs Composer Update]]></title>
            <link>https://medium.com/@favoriabs/composer-install-vs-composer-update-3737357c35a7?source=rss-8c948b303319------2</link>
            <guid isPermaLink="false">https://medium.com/p/3737357c35a7</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[composer-package]]></category>
            <category><![CDATA[composer]]></category>
            <dc:creator><![CDATA[Favor Oriabure]]></dc:creator>
            <pubDate>Sat, 11 Aug 2018 06:29:14 GMT</pubDate>
            <atom:updated>2018-08-11T06:29:14.166Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P21miU5LZk6XMleU" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When should we use the composer install or the composer update?</p><p>I have done some basic research and found out the following:</p><p>The major talking point is actually about composer.lock and composer.json.</p><h4>Scenario 1: Without composer.lock</h4><p>The assumption is that you just crafted a fresh PHP project, created a composer.json file and required some packages. For this article, we can assume this:</p><pre>{<br>    &quot;require&quot;: {<br>        &quot;monolog/monolog&quot;: &quot;1.0.*&quot;<br>    }<br>}</pre><blockquote>Point to note: monolog/monolog:1.0.* means get the latest monolog release that is between 1.0 and 1.1. In this case, i get 1.0.2.</blockquote><p>On the composer install command, because there is no composer.lock file yet, composer uses the composer.json file and installs the monolog package(creates a vendor folder with the package installed). Simple right?composer update actually does the same thing in this scenario.</p><h4>Scenario 2: With composer.lock</h4><p>The assumption is that there is already a project on ground and composer install or update has been run one or more times.</p><p>Running the composer install uses the composer.lock file, which now has the “lock” on all packages you have installed on the project. The advantage of this is that, 3months down the line, if this project is picked up by anyone and composer install is run, you can be sure that no dependency will break., because the versions have been locked to what you have in the composer.lock file.</p><p>Another advantage is that say you are in a team of 6, with composer install we can be sure that every one has the same version/release of each package at any given period of time until composer update is run.</p><p>In the case of composer update, it does not use the lock file, instead it uses the composer.json file and updates the packages(if updates have been released in the last 3 months). Which gives us one problem, what if a package has broken code in its latest release?</p><p>There are definitely use cases for both, and we should know what to apply to our different cases.</p><p>References</p><p><a href="https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies">https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3737357c35a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Twitter Stateless Social Login/Sign Up]]></title>
            <link>https://medium.com/@favoriabs/twitter-stateless-social-login-sign-up-eea73bc3bb1d?source=rss-8c948b303319------2</link>
            <guid isPermaLink="false">https://medium.com/p/eea73bc3bb1d</guid>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[stateless]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Favor Oriabure]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 06:30:04 GMT</pubDate>
            <atom:updated>2018-04-29T06:30:04.400Z</atom:updated>
            <content:encoded><![CDATA[<p>Social logins basically eases the process of sign up or log in within your application. Instead of the traditional flow of signing up with an email, password, username etc, you can easily sign-up through a social network like Facebook and get the users details returned from Facebook’s API.</p><p>Implementing this with most social networks on the server side right is quite easy. I’ll give some examples with Laravel Socialite.</p><pre>    public function redirectToProvider($provider)<br>    {<br>        return Socialite::driver($provider)-&gt;redirect();<br>    }<br><br><br>    public function handleProviderCallback($provider)<br>    {<br>        $user = Socialite::driver($provider)-&gt;user();<br>    }<br>//where $provider can be facebook or github etc.</pre><p><strong>So what’s stateless??</strong></p><p>A stateless app is one that doesn’t have a session. So say you have an SPA communicating with a back-end. There’s basically no session. In these cases you would use something like JWT. Because most of the social networks uses oauth2, this is very easy to do. Infact i know Facebook and LinkedIn have Javascript SDKs.</p><p>If you want to implement stateless login with Laravel, this piece of code should do it.</p><pre>    public function redirectToProvider($provider)<br>    {<br>       return Socialite::driver($provider)-&gt;stateless()-&gt;redirect();<br>    }<br><br><br>    public function handleProviderCallback($provider)<br>    {<br>       $user = Socialite::driver($provider)-&gt;stateless()-&gt;user();<br>    }</pre><p>Unfortunately, Twitter still uses oauth1.0a which means they do not provide a stateless flow…in fact they advice against it. Which means the above code won’t work for twitter.</p><p>So this is a hack…and i think it worked well. First i use<a href="https://twitteroauth.com/"> Abrahams</a> PHP twitter library.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/238196a3a888ee4c53711d77e72654f7/href">https://medium.com/media/238196a3a888ee4c53711d77e72654f7/href</a></iframe><p>Basically an Ajax request comes from the client and hits this method in a controller. We create a random string for every request that comes in and store it in the cache, keyed to the random string for a minute and then return the redirect url to the client.</p><blockquote>Something to note:</blockquote><blockquote>I concatenate a user parameter which holds the $tempId created, to the redirect url, this means that when twitter redirects with that url, it will arrive with the same $tempId which can now be picked up easily by the request object.</blockquote><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9214e79d9ebd6ae0cf4963e0204172a2/href">https://medium.com/media/9214e79d9ebd6ae0cf4963e0204172a2/href</a></iframe><p>This is where the redirect points to.</p><p>Here i can now get a complete connection with the client_id, client_secret, oauth_token which comes with the request object and the $tempId which was stored in the cache, keyed to the oauth_token_secret.</p><p>At the end of this $content should contain the user credentials gotten from the twitter API.</p><p>Let me know if this works for you…or i missed something.</p><p>References</p><ul><li><a href="https://github.com/abraham/twitteroauth">abraham/twitteroauth</a></li><li><a href="https://github.com/SocialiteProviders/Providers/issues/43#issuecomment-295501055">Twitter Stateless Session store not set on request. · Issue #43 · SocialiteProviders/Providers</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eea73bc3bb1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Beauty of Mistakes]]></title>
            <link>https://medium.com/@favoriabs/the-beauty-of-mistakes-fb9c6ad94a0a?source=rss-8c948b303319------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb9c6ad94a0a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Favor Oriabure]]></dc:creator>
            <pubDate>Sun, 04 Dec 2016 19:17:52 GMT</pubDate>
            <atom:updated>2016-12-04T19:17:52.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*27smnV65Nv8l0Eemgvib8A.jpeg" /></figure><p>I am a programmer…i love to write codes, solve problems and make things easy. I like to be in the thick of the battle…challenging ones at that. I like the pressure…i learn fast under it. Unfortunately, this doesn’t work out as planned every single time.</p><p>This past week, a task came up at work. It was a bulky one, one that if done manually, could take a week…even with a team of 5. I knew right from start that the manual approach wouldn’t be a good idea, especially for a programmer. So i went in search of a tool to automate the process.</p><p>Long story short, i messed with a crucial part of the code base to suit that temporary need. The Boss found out, and was totally pissed. Luckily for me, it didn’t cause a major damage. But still, it was damage.</p><p><strong>Lesson learnt</strong>, do the right things. Don’t drop the <em>standard</em> of the code for a need. More importantly, i have the opportunity to be more effective the next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb9c6ad94a0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>