<?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 Zainab Aiyeleso on Medium]]></title>
        <description><![CDATA[Stories by Zainab Aiyeleso on Medium]]></description>
        <link>https://medium.com/@zainab.aiyeleso?source=rss-d0a564abf561------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uaErcJD7lVTMsAkIfQCR5Q.jpeg</url>
            <title>Stories by Zainab Aiyeleso on Medium</title>
            <link>https://medium.com/@zainab.aiyeleso?source=rss-d0a564abf561------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:40:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zainab.aiyeleso/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 Engineering Manager’s Dilemma— To code or not to code]]></title>
            <link>https://medium.com/@zainab.aiyeleso/the-engineering-managers-dilemma-to-code-or-not-to-code-d09029ca0ee0?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/d09029ca0ee0</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Sat, 10 Mar 2018 08:02:42 GMT</pubDate>
            <atom:updated>2018-03-12T08:43:40.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*E-OoOb_LUtDFTuYg_QCcGQ.png" /></figure><p>This is about some of my learnings as a new Manager struggling to make time to write code. Most of these learnings happened a few years back but I am only now able to articulate them. I believe it will help people on this path.</p><p>When you start out on your engineering management path, you understand that you’ll have to do less as an individual contributor. A lot of us are however unprepared for how far away we will have to step from the code to be able keep a manager’s schedule. I summarise a manager’s schedule as a mesh of meetings, process management, people development, planning, follow ups and communication.</p><p>A colleague who recently became a manager complained how he hadn’t done anything productive in X days. He had not written a line of code throughout the week. He had been running around getting things sorted across so many areas. He was wrong though. He was being productive, only in a different way. As a manager, you do not immediately see the outcome of your work. As a new manager still transitioning from a maker’s mindset, you’re are likely to believe you are not being productive unless you are creating something immediately tangible.</p><p>The first question is, how much code, If at all any, can you realistically contribute. Indeed is there a need to continue to code? After all, there are successful managers out there who do not contribute to the code base.</p><p>I do not believe managers should stop coding. I believe you manage better when you have full context of the constraints your team is working with. It is one thing to keep abreast of new improvements in your space that can improve how your team works. But it is another thing to understand the current constraints of your code base and how to introduce changes and improvements within it.</p><p>Do it for yourself as well. You keep the path to going back to an individual contributor open by honing your skills. You keep your skills and knowledge updated to prevent rot and decay over time as your platform evolves. Plus who doesn’t like to put on a headset and hack away all day. Sometimes you just want the peace and quiet of retreating into the code.</p><p>And I did try do this, to continue submitting PRs, leading the charge from the code. In the beginning, it was downright impossible. I just couldn’t make enough time. I’ll spend weeks on tasks that should take a few days as it was extremely difficult blocking out a chunk of time. I quickly realised that something needed to give. I could not code as much I wanted and still manage effectively. Reading a few thoughts here and there about people facing this helped. My line manager, the VP of Mobile Engineering, also helped a lot in helping to define what the primary mandate of the role was. To paraphrase him, “Your goal is to guide and enable your team do their best work in the best way”.</p><p>So I had to stop all dreams of contributing code for a while to focus on team building. There was a lot to do as this was a team of people including myself who had no prior agile development experience.</p><p>I’ll say team cohesion is inversely proportional to time spent managing said team. There is a cohesion point that a scrum team achieves where everybody understands exactly what they need to do and the goal was to inch closer to this point after every sprint. When you have a highly cohesive team, you are able to focus on other parts of management and you gain yourself some time to spend on the code. By winning and losing together sprint after sprint, you gradually inch towards this cohesion.</p><p>As the team grew better at working together, I started to pick up code tasks again. Never like before though. I chose to focus on quick bugs, improvements and optimisations that were not part of any immediate sprint goals. This way, I didn’t block a task because I was unable to make out as much time for it. My team is much smaller now though which means I can focus on the code again.</p><p>My conclusion, as a manager remember your primary mandate is enabling others do their best work. Do not sacrifice that mandate for the code. In the long run, you are only one person and can only do so much. A much more impactful goal is to focus on people and team building. This way you have a team that can build so much more than you could have ever done burying yourself in the code. As you succeed in your primary goal, you can then gradually step back into the code and hopefully find a working balance between coding and managing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d09029ca0ee0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to cook Spaghetti Code — A recipe]]></title>
            <link>https://medium.com/@zainab.aiyeleso/how-to-cook-spaghetti-code-a-recipe-cd9242a85245?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd9242a85245</guid>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Sun, 10 Sep 2017 10:48:30 GMT</pubDate>
            <atom:updated>2017-09-10T12:05:25.387Z</atom:updated>
            <content:encoded><![CDATA[<p>First time you saw the brief, you gave a rough estimate of 6 months. You are told to deliver it in one month or else …</p><p>So you go into a hyper human phase. All nighters multiple times a week. Weekends? They are a thing of fairy tales. There is work to be done. You are fighting with every bone and matter in you to do the impossible. You mentally correct yourself, “No!! , It’s hmm-possible”.</p><p>For the 5th time this week, you are interrupted in the middle of your <em>dynamo</em> training for a meeting with Oga patapata. Oga had a dream last night. It was revealed that the only way the project will succeed is if you make the shiny bird do a galala while in flight. Never mind that you spent all last night perfecting the algorithm to make it dance azonto which Oga said was the holy grail of this project a week ago. Anyway, 5th revelation of the week made. Threats about being released back into the talent pool are flying all around. You don’t want any of them landing on you.</p><p>You go back to your desk, put your cowboy hat on and get back to work. If you add dreads to the azonto algorithm then it’s practically galala.</p><p>It’s now 2 months after the original delivery date. Oga’s Ogas are fuming. Pressure is mounting. Everybody is on edge. Arguments and subtle finger-pointing everywhere. You’ll do whatever it takes to get it done including bad habits you swore off. You have to deliver. Everything else takes the back seat. And really what is clean architecture? So long as it works, right? No users will be peeking under this hood anyway. Plus <strong>Tests</strong> are for sissies that live in fear of their own code. Sissies that can’t even trust their own work. lol. In the sense-giving words of <a href="https://medium.com/u/9e13edbcb55f">Prosper Otemuyiwa</a>, you can’t have failing tests if you don’t write tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*h0cg0aiV0xVCB5giRJdesg.png" /><figcaption>Evangelist <a href="https://medium.com/u/9e13edbcb55f">Prosper Otemuyiwa</a></figcaption></figure><p>And so you resolve: By fire, blood and all that is dirty, you will get it <strong>DONE</strong>.</p><p>That night, You have a nightmare where Uncle Bob is circling around you while throwing teared out pieces from <em>Clean Code</em> at you and screaming “Shame!! Shame!! Shame!!”</p><p><strong><em>Lingo</em></strong></p><p><em>Oga — Your Boss</em></p><p><em>Oga Patapata — Top Boss. Usually, in the calibre of a CEO or MD</em></p><p><em>Galala — An African dance made popular by a musician called Daddy Showkey. He is known for his tradmark dreads.</em></p><p><em>Azonto — An African dance style.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd9242a85245" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Am Legacy — To Refactor or Rewrite]]></title>
            <link>https://medium.com/@zainab.aiyeleso/i-am-legacy-to-refactor-or-rewrite-7c856d3f4508?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c856d3f4508</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Sat, 01 Jul 2017 09:37:35 GMT</pubDate>
            <atom:updated>2017-07-02T14:10:28.664Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“The electric light did not come from the continuous improvement of candles.” — <strong>Oren Harari</strong>.</blockquote><p>A blank slate. A blank slate is a new opportunity. A blank slate can reignite lost passions, giving you new energy and drive. Wiping away the fatigue of patching up old things with a promise of greater things to come. Sometimes, you need to throw out all of the old in order to give true ingenuity the room to bloom. Sometimes, you need a blank slate.</p><p>Most times, you don’t get a blank slate.</p><p>If you had asked me 3 years ago about the best way to upgrade your legacy app, I would have hands down said by refactoring it bit by bit. I would have told you how your code isn’t your product. How the user doesn’t care what is underneath the engine. How surviving as a business was the most important thing. How customer needs matters more than your fancy codes and frameworks.</p><p>I would have warned you about the very real risk of underestimating the complexity of the current system. How easily you could rope yourself into a very expensive project, tying down teams for months thereby reducing the pace at which your product adapted to the ever dynamic market needs. How you would have had to actively work on 2 code bases as you needed to keep the first app up to date while building the new app. I would have screamed blue murder and I probably would have been right. Rebuilding a product from ground up is a very very expensive undertaking.</p><p>Today my answer will be significantly different because of 2 key experiences.</p><p>One, maintaining a legacy app(Konga Android app) that was built a gazillion years ago. It still serves its purpose to the business and users quite well. The code is dated and was built back when the android community hadn’t agreed what an android app architecture looked like. It also doesn’t help that it was built under tight deadlines, changing requirements and all the usual constraints that birth bad code. Sprinkle in building new features on top of all that debt and you have the perfect legacy crap code. Something needed to change.</p><p>We were clear about what our priorities were and knew we couldn’t rebuild the android app especially since it still served business and user needs. So we started to bite a little at a time, gradually decoupling and modularising the different layers, updating the code to use more modern practices, switching out dated libraries and practices, adopting MVP, moving all our apis to graphql and behind a gateway. We focused mostly on the core java code and I am pleased so far. Gradual refactoring is a less expensive approach to an upgrade. You get the best of both worlds. You bite a little bit at a time while still being able to attend to upcoming business requests.</p><p>The second thing that has changed my outlook is building KongaEZ. We got a clean slate. Over 50% of traffic came from mobile web but conversion was abysmal. We were obviously leaking revenue and needed to do something. We totally scrapped what was our mobile web and started afresh. It took a long time to finally be up and running. Deadlines were missed. Reset. And missed again. It was very expensive and it was the one the best decisions we’ve ever made. Conversions went up over a 1000% on some browsers and we were seeing orders from the most remote areas of the country. It was totally worth the cost. Building KongaEZ made me understand that sometimes to truly build great things, you need to completely throw out the bad and start afresh. Sometimes, You need a clean slate. A clean slate to try out new ideas and methodologies.</p><p>We had to adopt 2 different approaches for the different platforms. For the native apps, we gradually refactored it while still serving business requests. For mobile web, we threw out everything and started from scratch. These 2 experiences have made me realise that there is no one answer to the refactor or rebuild question. The team, business, technology, market, platform and more determines what will be done. At the end of the day, you need to make a decision and see it through.</p><p>Today, If you ask me about the best way to upgrade your legacy app, I will smile slowly, like an old man reminiscing the good old days, and say with an expression that looks like wisdom — It depends.</p><p><em>Edit- Big thanks to Chief </em><a href="https://medium.com/u/cc3d654f79ce"><em>Victor Asemota</em></a><em> for pointing out some conclusion flaws.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c856d3f4508" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Founder, a Software Engineer does not a product make.]]></title>
            <link>https://medium.com/@zainab.aiyeleso/dear-founder-a-software-engineer-does-not-a-product-make-8ecfe8145290?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ecfe8145290</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Sat, 06 May 2017 08:50:58 GMT</pubDate>
            <atom:updated>2017-05-08T11:48:59.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAZ14w8HbK7fSFIjRUSPwA.jpeg" /></figure><p>There are many ways to structure a team for your product.</p><p>You can have the product owner/manager who crafts the vision of stakeholders, himself inclusive, into a product direction and journey. He’s the guy who knows the “whats and whys” of the product. Or more accurately he <em>should</em> be the guy that knows.</p><p>The Architects who determine how and if the moving parts will fit technically. They basically transform the product brief into technical structures.</p><p>The Engineering managers who oversee the process of building the product. Their job is to get to <strong>DONE</strong> in the most efficient way possible. They ensure best engineering practices are followed and they manage the time of the Engineers.</p><p>Then the Software Engineers(SEs). The creators of the products. They breathe life into the vision. Without them there is no product. We can bootstrap away every other person but not the Software Engineer. All other roles exist to ensure that the SEs are building the correct product in the right way and time. I’ll come back to this main character soon.</p><p>Depending on how big your product and pocket is, you can have Senior Software Engineers or Leads who other Engineers go to with problems, Devops who own the infrastructure, Software Quality Testers, User experience designers, UI and graphic designers etc. The nitty gritty of these roles vary from org A to B but I think you get the gist.</p><p>You can have the dream team. You can have all of these specialised roles who are the best at what they do all working towards the vision of the product. Your team can be the very soul of agile or any other world-shattering development methodology. You can have all of these things and still fail. In fact most software projects overshoot budgeted time and cost and many more fail outrightly.</p><p>Now to the point.</p><p>Dear startup founder, imagine how tough it is to succeed with all of the above, then imagine stripping all that away and putting it all on the Software Engineer(SE). They’ll be doing all of their own requirements fine tuning, architecting, devops, testing and still write code. Not to mention that your requirements are constantly changing. You interrupt them multiple times a day asking for updates. No buffer between you and their time whatsoever. You create the perfect recipe for failure and drop them in it. Even the most talented Software Engineer will struggle to deliver in this scenario. Writing code requires deep concentration for a significant period of time which just won’t happen here. Writing the correct code for the correct product is even more unlikely. How can you expect a successful outcome dear founder, how?</p><p>Yes, you are bootstrapped, have cash flow issues but at the very minimum, you should have a chief problem solver type of person who can manage everything else working with your software team, who can respect and protect the time and process of writing code.</p><p>In conclusion, Yes, Software Engineers are super heroes but they cannot save the world on their own. Give your startup a better chance by structuring it to enable them to deliver.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ecfe8145290" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No way you can do that….. Ok, Prove it.]]></title>
            <link>https://medium.com/athena-talks/no-way-you-can-do-that-ok-prove-it-609e8a8ff9e3?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/609e8a8ff9e3</guid>
            <category><![CDATA[women]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[international-womens-day]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Thu, 09 Mar 2017 08:26:20 GMT</pubDate>
            <atom:updated>2017-07-01T17:44:51.973Z</atom:updated>
            <content:encoded><![CDATA[<p>In the spirit of International Women’s day.</p><p>I have not experienced a lot of the prejudice women in STEM report in the workplace. There’s however one prejudice that I have faced in multiple work environments. I can’t quite conclude if it has to do with being female or if its my general demeanour that informs this treatment.</p><p>It’s that I have to prove that I can truly do what I say I can do as well as I say I can before I can be counted. I’ve faced this twice when switching jobs, a number of times when switching teams and working with people for the first time.</p><p>I’ll like to chalk it down to a general distrust of new people to the workplace but I see other people as new as I am have their voices heard above mine. They believe and trust the men without them needing to prove themselves first. I’ve seen my comments and suggestions dismissed without consideration. I’ve also seen my suggestions that were dismissed without a chance of scrutiny get accepted the very next day when another person<em>(man)</em> puts it forward. All of these and countless more examples. These things generally go away after working together for a while and ‘proving’ that I really do deserve a seat at the table.</p><p>Sure there are imes when I truly know nothing. BTW, I like being in a room where everybody else knows more than I do. It usually means I’m in the right place. I like to think of myself as a knowledge fleece. Always willing to attach myself to people who know and soak up what I can learn from them.</p><p>And so I acknowledge that sometimes I truly don’t know but a significant other number of times, I can see a different assessment of new men and women to the same team.</p><p>I hope that by not giving in and hiding in a corner for fear of being shutdown, I make the path for women coming after me easier. To all women that keep pushing through all prejudices and come out stronger, Happy International Women’s day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=609e8a8ff9e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/athena-talks/no-way-you-can-do-that-ok-prove-it-609e8a8ff9e3">No way you can do that….. Ok, Prove it.</a> was originally published in <a href="https://medium.com/athena-talks">Athena Talks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Native apps, 2017 and I]]></title>
            <link>https://medium.com/@zainab.aiyeleso/to-a-very-mobile-2017-abb4776924f6?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/abb4776924f6</guid>
            <category><![CDATA[native-app]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Sat, 31 Dec 2016 16:58:51 GMT</pubDate>
            <atom:updated>2017-01-29T17:43:04.375Z</atom:updated>
            <content:encoded><![CDATA[<p>I started this from a T<a href="https://twitter.com/Baniyaz/status/810098249122123776">weet</a>. My blog posts are almost always inspired by random tweets.</p><p>2016 is the year I learnt about <a href="https://www.google.com.ng/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=13&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwink7OwpZjRAhUcN1AKHespCaMQFghJMAw&amp;url=https%3A%2F%2Fdevelopers.google.com%2Fweb%2Fprogressive-web-apps%2F&amp;usg=AFQjCNGY_gH1EkXQ0bamFoprnG33zFgFiw&amp;bvm=bv.142059868,d.ZWM">Progressive Web Apps</a>. Progressive Web Apps otherwise called PWAs are a set of standards that help you marry the best of native apps and the web platform, bringing goodies like push notifications and offline functionality to the web. You can read more about PWAs <a href="https://auth0.com/blog/introduction-to-progressive-apps-part-one/">here</a> and <a href="https://bitsofco.de/bitsofcode-pwa-part-1-offline-first-with-service-worker/">here</a>. Needless to say, a PWA is currently the best way to provide the Mobile Web experience. You don’t even have to rebuild your whole web site, you can gradually implement these concepts one after the other. And in a a country like Nigeria where we are abundantly blessed with slow and flaky networks, PWAs fits perfectly.</p><p>2016 is also the year we at <a href="http://cyberomin.github.io/engineering/2016/07/30/pwa-and-konga.html">Konga</a> undertook the journey to rebuild our Mobile Web experience. For the longest time, using our mobile website was very expensive. Getting to the home page alone cost about 2MB and there were so many other experience issues. After numerous considerations, we came to the natural decision to build a PWA. We plan to share our journey on how that went soon(<a href="https://medium.com/u/c0b03dc5e50e">cO</a> I see your side eyes). From the very specific way to build for Opera mini, to getting things rolling on Safari, to flipping all of our work on its head. We have tales for decades. We still have quite a bit to do with our PWA and will continue to aim for the best experience in 2017. This has been the very rewarding focus of my 2016. All of these left me very little time for one of my long time passions, Android apps.</p><p>You see, 2016 is the year where I didn’t do any real native android development. It’s still hard for me to believe as Android had been the backbone of my career for the longest time. I was a native app person through and through. I truly believe the next billion users will be running Android in some form and so naturally thought Android apps were the ultimate truth. I no longer hold the latter to be true. Native apps are expensive to build and maintain and should only be done for specific use cases. Building a Native app should never be a case of <em>me too</em>. While native apps would continue to be able to deliver a unique experience and are not going anywhere anytime soon, I now see that they’re not the only way to connect to the next billion.</p><p>I still personally enjoy writing for android and will continue to do so. I recently cloned Google’s <a href="https://github.com/googlesamples/android-architecture/tree/todo-mvp-rxjava/">android-architecture</a> as a way to revamp my native ninja in 2017. It feels really good dusting off the cobwebs. It’s like an old pair of shoes. First it looks worn and dirty, but once you clean it up, you start to remember why they were your favourite pair of shoes.</p><p>I have always claimed to be able to change my stance when new information is presented. 2016 tested this claim and I am glad I was able to shift my perspective. My passion has now shifted towards the mobile platform as a whole. I now worry about the best way to connect to the user via that mobile device in his pocket. And it doesn’t matter if it is through native apps, PWAs or some other crazy top-secret tech still in development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abb4776924f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I expected a Buhari presidency to bring difficult times for Nigerians]]></title>
            <link>https://medium.com/@zainab.aiyeleso/why-i-expected-a-buhari-presidency-to-bring-difficult-times-for-nigerians-dd6fced2ffe9?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd6fced2ffe9</guid>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[buhari]]></category>
            <category><![CDATA[nigeria]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Sat, 30 Apr 2016 15:46:54 GMT</pubDate>
            <atom:updated>2016-04-30T15:55:09.221Z</atom:updated>
            <content:encoded><![CDATA[<p>Why I expected a Buhari presidency to bring difficult times for Nigerians</p><ol><li>Buhari will try to fight corruption. Of course corruption will fight back, guns blazing. You can’t expect people who have been living lavish lifestyles sponsored by government coffers to just roll over and give it all up. This points to an all out fight between the Govt and the Cabal. Nigerians will get caught in the middle.</li><li>Buhari appears to be quite strong minded and will not compromise on certain things he believes are right. Unfortunately, sometimes a compromise is what is needed in order to ease the pains of Nigerians. Buhari seems like the type of person to justify the plight of Nigerians as a sacrifice for the greater good. Is he right to believe this? Only time will tell.</li><li>Most Nigerian politicians have no plans on how to tackle the issues on ground when they come into their positions. Manifestoes have now become a collection of campaign slogans. Because that’s all they use it for, to campaign. And so when they win, they are unable to hit the ground running. How can they when they don’t even understand the issues on ground. When they finally do understand, they are overwhelmed by the magnitude of the issues they have to solve. Meanwhile, Nigerians stay suffering while the new government is trying to ramp up.</li><li>Our problems are so deep rooted and complicated that nothing but an innovative intellectual approach can tackle them without Nigerians paying the price. Electricity for example, tariffs have been increased to make the industry more attractive to investors. It’s very simple logic that might work eventually but will result in Nigerian tears in the meantime. Only deeper solutions can work and still spare Nigerians the hard times.</li></ol><p>I personally don’t mind the tough times so long as we come out on the other side as a better country. I however don’t believe Nigerians need to be offered up as sacrifice before this country can get to the other side but the limitations of our current ruling class is currently forcing it to be so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd6fced2ffe9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You do not want to be special anymore]]></title>
            <link>https://medium.com/athena-talks/you-do-not-want-to-be-special-anymore-205f51122b7?source=rss-d0a564abf561------2</link>
            <guid isPermaLink="false">https://medium.com/p/205f51122b7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Zainab Aiyeleso]]></dc:creator>
            <pubDate>Fri, 18 Mar 2016 11:48:45 GMT</pubDate>
            <atom:updated>2016-03-23T15:39:23.430Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s about a time that you envision. A dream of a future that seems closer with each new TechGirl group you see.</p><p>A time when you are not special.</p><p>When you can walk into that tech summit without turning heads. When you do not instinctively count the number of other Ladies present.</p><p>A time when you are just another Engineer in the room whose only differentiating factor is excellence.</p><p>A dream of a time when being techie ‘Female’ is not enough to get your name on the list. When that little voice that whispers in the corners of your head no longer wonders whether you got there solely because of your skills.</p><p>You are not as special as you were 3 years back. You count more Ladies in the room than you did last year. You feel hope. You can taste that dream now.</p><p>And so with each new list that you get on, excellence based or not, you no longer entertain that voice. You now understand that being put on a stage for the world to see is the first step to getting other Ladies to join you. You can see it working.</p><p>And you smile because you know. You know the generation that will never have to wonder if they deserve that accolade is rising. They’ll already know. They will no longer be special.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=205f51122b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/athena-talks/you-do-not-want-to-be-special-anymore-205f51122b7">You do not want to be special anymore</a> was originally published in <a href="https://medium.com/athena-talks">Athena Talks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>