<?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 Olawale Ogunibe on Medium]]></title>
        <description><![CDATA[Stories by Olawale Ogunibe on Medium]]></description>
        <link>https://medium.com/@olutola?source=rss-116af01ce99e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*StfvZIrsEzlWT4MZ.</url>
            <title>Stories by Olawale Ogunibe on Medium</title>
            <link>https://medium.com/@olutola?source=rss-116af01ce99e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:21:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olutola/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[Ronald Wayne; A story of Apples and Oranges]]></title>
            <link>https://medium.com/@olutola/ronald-wayne-and-the-apple-story-c4d31fa499a4?source=rss-116af01ce99e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4d31fa499a4</guid>
            <category><![CDATA[ronald-wayne]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[outcomes]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Olawale Ogunibe]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 14:33:38 GMT</pubDate>
            <atom:updated>2018-08-22T15:59:44.453Z</atom:updated>
            <content:encoded><![CDATA[<p>Apple recently became a 1 Trillion Dollar Company and the media is abuzz with this news. In the midst of this, I have been seeing a lot of talk about Ronald Wayne. Ronald Wayne is one of the co-founders of Apple who decided to sell his 10 percent stake when the company was in its infancy. A lot of stories centered around the premise that he made a terrible mistake by quitting on the company early because right now, he would have become a billionaire</p><p>This got me thinking. I disagree with the premise that suggests that Ronald Wayne made the wrong decision by choosing to sell early. I have two problems with this statement.</p><p>First, this is a classic example of outcome bias. Outcome bias is the tendency to judge a decision by its eventual outcome instead of based on the quality of the decision at the time it was made. An example is someone choosing to work in Microsft instead of being an early employee of Google. If you judge the financial payoff, working in Google will likely pay off more financially (especially after the IPO) but working at Microsoft would be a more reasonable choice at the time. Another example is a person winning the lottery grand prize after spending his whole life saving to buy tickets. This might look like a good idea because he won the lottery but we can all agree that spending all your money on lottery tickets is a bad financial decision. The only fair way to judge Ronald decision is to travel back in time and look at the variables available to him at the time he was making the decision.</p><p>Second, the premise suggests we all should or need to be clairvoyant. This is an unrealistic expectation, nobody could foresee Apple future in the 70s or 80s. Not Ronald, not Steve Wozniak and definitely not Seve Jobs who was even forced out of the company at some point. The events that led to Apple success today is like a black swan event. I can’t think of any other company with a similar trajectory today and it is very unlikely this would ever happen again. To say we could have predicted this is foolhardy at best. Also, remember so many companies that were formed around the same time failed. Nobody can predict the future, even Steve Jobs parent decided to give him up for adoption.</p><p>Also, we should be careful in judging Ronald’s success only by his net-worth. In other words, by how much money he has vs how much money he could have had. Judging success by money alone is one route to failure in life.</p><p>We make decisions every day, the best way to make good decisions is to look at the variables available to us at the time. Not assuming we have some kind of ability to foresee the future.</p><p>Judging Ronald Wayne on the decision he made decades ago with the current realities is like comparing apples and oranges</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4d31fa499a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Classic Ted Talks 1/2]]></title>
            <link>https://medium.com/@olutola/top-ted-talks-classic-1-2-6f4a7ddfd3ee?source=rss-116af01ce99e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f4a7ddfd3ee</guid>
            <category><![CDATA[tedtalks]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[ted]]></category>
            <dc:creator><![CDATA[Olawale Ogunibe]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 05:12:36 GMT</pubDate>
            <atom:updated>2018-07-31T05:26:34.996Z</atom:updated>
            <content:encoded><![CDATA[<p>I discovered TedTalks in 2008 and I became hooked immediately. Ten years later, TedTalks has become a cultural phenomenon and I have listened to thousands of Talks (yes thousands). While hundreds of new interesting TedTalks are added yearly, I still find myself listening to some old TedTalks from time to time. If you discovered TedTalks recently, you may not know some of these Talks but I bet you, they are worth watching. I want to share my list of 10 classic Talks you should listen to.</p><p>I have also included a quote from each of the Talk.</p><p><a href="https://www.ted.com/">TED: Ideas change everything</a></p><p>Enjoy.</p><p>P.S. I defined classic as any Talk before 2010.</p><h3><strong>Do schools kill creativity? by Ken Robinson.</strong></h3><p>This was one of my first Ted Talks and it literally blew my mind. I watched this some months after graduating from the university and it changed my mind about the whole educational system. I don’t want to spoil anything, watch this and understand why it has remained the most watched talk for over 10 years</p><blockquote>Picasso once said this, he said that all children are born artists. The problem is to remain an artist as we grow up. I believe this passionately, that we don’t grow into creativity, we grow out of it. Or rather, we get educated out of it. So why is this?</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fsir_ken_robinson_do_schools_kill_creativity&amp;display_name=TED&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fsir_ken_robinson_do_schools_kill_creativity&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Fpe.tedcdn.com%2Fimages%2Fted%2F6b6eb940bceab359ca676a9b486aae475c1df883_2880x1620.jpg%3Fh%3D421%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="421" frameborder="0" scrolling="no"><a href="https://medium.com/media/610611fef4db17b0988513f3bb706507/href">https://medium.com/media/610611fef4db17b0988513f3bb706507/href</a></iframe><h3>The politics of fiction by Elif Shafak.</h3><p>We usually associate with people that are like us; the more we do this, the more close-minded we become. This is a call to expand your world, experience other cultures and embrace different experiences. Also, Elif makes a case why fiction should not be taken too seriously.</p><blockquote>There is a gap between the mind and the tongue. And that gap is very intimidating but if we manage not to be frighten by it, it is also stimulating</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Felif_shafak_the_politics_of_fiction&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Felif_shafak_the_politics_of_fiction&amp;image=https%3A%2F%2Fpe.tedcdn.com%2Fimages%2Fted%2F184238_240x180.jpg%3Flang%3Den&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="315" frameborder="0" scrolling="no"><a href="https://medium.com/media/00380359ae18a4797a5540241cf49ff1/href">https://medium.com/media/00380359ae18a4797a5540241cf49ff1/href</a></iframe><h3>3 clues to understanding your brain by Vilayanur Ramachandran</h3><p>Ramachandran is a brilliant neurosurgeon, this talk is about how brain function discoveries are inferred from brain injuries. He talks about some strange neurological conditions and why some people are more artistic than others</p><blockquote>All of these questions that philosophers have been studying for millennia, we scientists can begin to explore by doing brain imaging, and by studying patients and asking the right questions.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fvilayanur_ramachandran_on_your_mind&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fvilayanur_ramachandran_on_your_mind&amp;image=https%3A%2F%2Fpe.tedcdn.com%2Fimages%2Fted%2Fdcab1e9cac303f4ed12de8ac86aaae4083782d97_240x180.jpg%3Flang%3Den&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="315" frameborder="0" scrolling="no"><a href="https://medium.com/media/52695ec793390a62f39fc5acc7ffb2d9/href">https://medium.com/media/52695ec793390a62f39fc5acc7ffb2d9/href</a></iframe><h3>Life lessons from an ad man by Rory Sutherland</h3><p>In this funny talk, Sutherland discusses important observations about perceptions. He talks about how we can effect changes by changing perceptions. Big problems can sometimes be solved by simple solutions, but we don’t find this often. Learn how to make a train trip more enjoyable or encourage cultural modernization in a society</p><blockquote>Now, here is another naive advertising man’s question again. And this shows that engineers, medical people, scientific people, have an obsession with solving the problems of reality, when actually most problems, once you reach a basic level of wealth in society, most problems are actually problems of perception</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Frory_sutherland_life_lessons_from_an_ad_man&amp;display_name=TED&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Frory_sutherland_life_lessons_from_an_ad_man&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Ftalkstar-photos.s3.amazonaws.com%2Fuploads%2Fde6ab41c-6944-4740-970a-58caf28c06b8%2FRorySutherland_2009G-embed.jpg%3Fh%3D316%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="316" frameborder="0" scrolling="no"><a href="https://medium.com/media/5d2a0217474343852f5e98f0d89098de/href">https://medium.com/media/5d2a0217474343852f5e98f0d89098de/href</a></iframe><h3>Laws that choke creativity by Larry Lessig</h3><p>In this age of technology, everybody breaks the law whether they know it or not. When you upload a video with a copyrighted material into Youtube or you download a new movie from a file sharing site, you are likely breaking a law. Larry Lessig explains why the law and new technologies don’t mix well and what we can do to ease the tension.</p><blockquote>…we need to recognize you can’t kill the instinct the technology produces. We can only criminalize it. We can’t stop our kids from using it. We can only drive it underground. We can’t make our kids passive again. We can only make them, quote, “pirates”.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Flarry_lessig_says_the_law_is_strangling_creativity&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Flarry_lessig_says_the_law_is_strangling_creativity&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Fpe.tedcdn.com%2Fimages%2Fted%2F01726ef3620b97fcc2a664e1339c6602785123f7_1600x1200.jpg%3Fh%3D316%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="316" frameborder="0" scrolling="no"><a href="https://medium.com/media/4184055ed983dcc07730c8426f90ad1f/href">https://medium.com/media/4184055ed983dcc07730c8426f90ad1f/href</a></iframe><p>To be concluded in the in my next post</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f4a7ddfd3ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working in VGG, A Retrospective]]></title>
            <link>https://medium.com/@olutola/working-in-vgg-a-retrospective-159a30729b1a?source=rss-116af01ce99e------2</link>
            <guid isPermaLink="false">https://medium.com/p/159a30729b1a</guid>
            <category><![CDATA[reminiscence]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[goodbye]]></category>
            <dc:creator><![CDATA[Olawale Ogunibe]]></dc:creator>
            <pubDate>Thu, 01 Mar 2018 02:46:17 GMT</pubDate>
            <atom:updated>2021-10-17T05:56:25.792Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*9tOUvxZ7Bhg38E9EcU5QRQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=159a30729b1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top Misconceptions about Agile Software Development]]></title>
            <link>https://medium.com/@olutola/top-misconceptions-about-agile-software-development-a148facb9b21?source=rss-116af01ce99e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a148facb9b21</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Olawale Ogunibe]]></dc:creator>
            <pubDate>Wed, 06 Apr 2016 10:33:37 GMT</pubDate>
            <atom:updated>2018-01-05T05:19:36.750Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever had this conversation with a Project Manager (PM) ­ “Wale, we need this project done with all these features complete. How long will it take to complete?” and you replied ”Ten (10) weeks”. The PM replies “Wow, the client can’t wait that long. Can’t we adopt Agile?” By suggesting we adopt Agile, he is hoping the timeline get reduced. Or maybe a PM has told you this “We don’t need to gather requirements, we are going to use Agile”. These statements reveal common misconception about Agile development. A lot of people are self-proclaimed experts on Agile methodology, yet they have not even read the Agile manifesto. I have highlighted the most common ones and will try to address it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*7QuXnRG34b_nOaD2.png" /></figure><p><strong>Agile means discarding processes, tools, documentations and planning.</strong></p><p>Most people claim this is straight out of the manifesto; they are right, but only partially. For example, the first line of the manifesto reads “Individuals and interactions over processes and tools”. To a casual observer, this may mean discard processes and tools in favor of individual and interactions, but the manifesto clarifies this at the end ­ “…That is, while there is value in the items on the right, we value the items on the left more.” Agile simply means there is more value in “Individuals and interactions” than “processes and tools”. Proper processes should not be discarded, it should be modified to work with the Agile framework.<br>Take planning as another example, Agile manifesto states that “Responding to change over following a plan”. This does not mean don’t plan, it simply means don’t let your plan interfere with accepting new changes. Our plans must be flexible enough to accommodate changes even late in the project. Documentation also remains important and there are so many agile tools out there that improves team’s productivity.</p><p><strong>Agile means faster.</strong><br>This is one of the most common misconceptions on agile and I guess this comes from the meaning of the word “Agile” which means to move quickly and easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*XBfA50BkD15ef5Dq.jpg" /></figure><p>Actually, it was not stated in the Agile manifesto that it guarantees speed. If you are adopting Agile because you think you will be faster, please stop! Agile emphasizes flexibility, not speed; it should allow you to adapt easily. Agile is time agnostics, it insists on collaborative development, regular meetings and customer interactions. Not speed.The closest to speed Agile proposes is develop and release in phases rather than waiting to deliver a complete software. So adopting Agile may mean you will get to see a working product sooner but this won’t be the complete product. This is one of the most frustrating aspects of new teams that adopt agile without proper understanding because they usually expects faster speed. Agile does not make your developers better or faster, it just allow them to work more coherently with the rest of the business team.</p><p><strong>Agile is just for software developers.</strong></p><p>When people think Agile, they usually think it is a way to manage software teams and by that, they mean developers. This thinking is fundamentally wrong and will only result in frustration. Agile involves all the people responsible for the delivery and usage of the software. From the requirement analyst to the clients, everyone must</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*2drtfMP-KSncBX9d.jpg" /></figure><p>be involved. It is not Agile if we have only the software developers or analyst involved. Believe me, I have tried this and it does not work. One of the core values that Agile promotes is that Agile teams must be structured to be able to work independently, this means everyone that have a say about the development and direction of the product being built must be part of the agile team. What if the CEO has some very crazy ideas on features to implement, the CEO should be part of the agile team and attend its meetings. Nobody should be outside; people directing the project from outside add latency and makes coherency difficult.<br>Please note this does not mean an Agile team cannot or should not accept contributions to the project by someone from outside. Any contribution from outside should not be binding until it is discussed and adopted by the agile team at the regular team meeting. Once you have someone outside the team contributing to the direction of the projects, we start having issues. One of the core strength of Agile comes from the team being independent and self organizing team, everyone that has an authority to make decisions about the project are present. Yes, I mean everyone.</p><p><strong>Agile means no need for software testing.</strong><br>Why do we need to test in Agile, everyone is involved and we can see the software as it progresses? This is a misconception of both agile and software testing. Agile does not insist on a set of processes ­ what must or not be done. As stated earlier, Agile does not take away core developmental processes likes requirements gathering, analysis, design and so on. Software testing, as an integral part of software development, must also be part of the Agile process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*0FNiMew8xs3swMLa.jpg" /></figure><p>Also, software testing extends beyond the regular product review done during Agile meetings. These two are not the same and cannot be interchanged. This applies not only to testing but to other processes such as deployment, client UAT and many more. Just like everyone must be present for Agile to work, all the processes involved in software development and delivery must be part of the Agile process. Nothing should be left behind.</p><p><strong>Agile guarantees good and successful products.</strong></p><p>No it doesn’t, what Agile guarantee is good and successful product development. The keyword here is development. Agile does not guarantee market or product acceptance. There are product management techniques and methodologies for that, such as lean product development. Agile is not a product management tool, it does not determine or try to predict the success of a product. Agile does not mean you will make more revenue or your user base will increase. These are gross misconceptions and over exaggerations of what Agile aims to achieve. Agile does not and cannot test the quality of a product idea. Agile aims to provide sustainable development where the whole team can maintain a constant pace indefinitely.</p><p><strong>Agile means MVP.</strong><br>Minimum Viable Product (MVP) is the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. This is a concept in product development and not a software development process. Agile aims to improve the software development process while MVP is a concept use to test the viability of a product or an idea before making substantial investments of time and money in developing a full blown product. These two aim to address vastly different problems. Also, an Agile sprint does not need have to produce an MVP. However, in developing a MVP, Agile methodology can be adopted</p><p><strong>Agile means DevOps.</strong><br>Most companies that adopt Agile usually adopt DevOps, hence the confusion between the two. DevOps is a culture or practice that emphasizes collaboration and communication of both software developers and other information technology (IT) professionals, while automating the process of software delivery and infrastructure changes. Software delivery is the process of making a developed software available for use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*hkWT09S82NB_aZvh.png" /></figure><p>This is a very technical and complicated process which usually involves people outside the core software development team. DevOps seeks to automate and simplify this process by bringing everyone together.<br>In other words, DevOps is the Agile of software delivery. The party usually involved in DevOps are developers, QA and IT Operations (infrastructure Engineer). It is also important to note that DevOps definitely enhances Agile, allowing teams to continuously deliver software in an automated and continuous manner. While it is encouraged to practise both methodologies together, one can definitely be used without the other.</p><p><em>Originally published at </em><a href="https://medium.com/venture-garden-group-technology-blog/top-misconceptions-about-agile-software-development-892b82ef287d"><em>techblog.venturegardengroup.com</em></a><em> on April 6, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a148facb9b21" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>