<?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 Pelumi Aleshinloye on Medium]]></title>
        <description><![CDATA[Stories by Pelumi Aleshinloye on Medium]]></description>
        <link>https://medium.com/@aleshinloyelukmony?source=rss-6d8600761381------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*U-XSLQRkeo-4ltAXHYMxgQ.png</url>
            <title>Stories by Pelumi Aleshinloye on Medium</title>
            <link>https://medium.com/@aleshinloyelukmony?source=rss-6d8600761381------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:23:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aleshinloyelukmony/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[Building World Class features]]></title>
            <link>https://medium.com/@aleshinloyelukmony/building-world-class-features-2bd1afb34c98?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bd1afb34c98</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Sun, 23 Jun 2019 20:20:00 GMT</pubDate>
            <atom:updated>2019-06-23T20:20:00.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A7ESxCA2bycImu2moIf0FQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@emilep">Émile Perron</a> on <a href="https://unsplash.com/photos/xrVDYZRGdw4">Unsplash</a></figcaption></figure><p>As a programmer, if your code needs to be refactored or debugged before other developers can understand or contribute to the project, then your code sucks and the developer needs to work on him or herself.</p><p>During my boot camp and deferral program at Andela, We were required to build world-class features, codes that any developer can easily onboard on without any need to refactor or debug before they start contributing.</p><p>If you were to build a feature to let an admin add a book to an online library, to make the feature a world-class feature, the first step is to write a test for the feature, then write the validations and authentications before building the endpoint, the code should be well structures as well.</p><p>A good example of a world-class feature I worked on during the deferral program at Andela is a feature that lets admin add a book to the library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yu2e6BgfY7xnlBqi5zOryA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-DKdE5WgaGT34NWGDS1QvA.png" /><figcaption>Screenshot showing test written for a feature</figcaption></figure><p>The endpoint was properly tested for all possible scenarios of errors and validations, this makes your code easier to debug because when anything goes wrong, you can easily point it out through your tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N9qxPSCJ7toiZ_P1qQWsnw.png" /><figcaption>Screenshot showing validation for a feature</figcaption></figure><p>Then the validations for data sent to the endpoints should be tested as well, this makes the endpoint secured so unwanted or unsupported data would be filtered out and the error would be sent back to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpoS-8IjiyFontAqxtcFEA.png" /><figcaption>Screenshot showing the endpoint controller class</figcaption></figure><p>A well structured static method using OOP, employing OOP in your feature means your code might need little to no refactoring in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WNDFtDmpZG8nWJ93xDjitQ.png" /><figcaption>Screenshot showing documentation for a feature</figcaption></figure><p>The code documentation is the backbone of every application. Documentation makes other developers understand and test your code easily. Without documentation, it would take developers extra hours trying to figure out the purpose of your code.</p><h4>Conclusion</h4><p>A world-class feature must be well structured, has a clean and consistence formatting, well documented and must be secured.</p><blockquote>The quality of your code is a critical measure of your competence as a developer</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bd1afb34c98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code Refactoring and Bug Fixing]]></title>
            <link>https://medium.com/@aleshinloyelukmony/code-refactoring-and-bug-fixing-8e6fe51bda1a?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e6fe51bda1a</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[debugging]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Sun, 23 Jun 2019 19:12:47 GMT</pubDate>
            <atom:updated>2019-06-23T19:12:47.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UhMenje98oBY3RffrafjZg.jpeg" /></figure><p>When most people hear the word <strong>bug</strong>, they think about the little insects like beetles or cockroaches. These are actually bugs too, but in software development bugs is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.</p><p>Both the insect bugs and software bugs are not pleasant. People are actually scared and pissed when they find any of them. But Software bugs are your mistakes and can easily be corrected by you, they might be a pain in the ass but can be fixed with patience and understanding.</p><p>Whenever I get a bug, I either use a NodeJs npm package called <a href="https://www.npmjs.com/package/debug">Debug</a> or the Visual Studio code debug tool. The <strong>debug </strong>works just like console.log but it better because it does not affect production, and it would not log anything onto your user’s console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wSWeDHqsDYsoxEjK_z1mHw.png" /><figcaption>A screenshot of debugging with the Debug package</figcaption></figure><p>By using the debug package, you can specify when to log a data and when not to, which makes it acceptable for production.</p><h4>Code refactoring</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_PFmY9w7nEeTZZy6QIa2Q.jpeg" /></figure><p>Refactoring code is the process of improving an existing code without changing its external behaviour. Most times after your code works the way you want it to work, you might have to refactor it for a couple of reasons, either to improve the functionality or make the code easily readable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IlDKDd6fqofzecoYmnB-8Q.png" /><figcaption>Screenshot of refactoring</figcaption></figure><p>In the screenshot above, there was a lot of cases where <em>books </em>were repeated in the URL, I had to refactor the code to avoided repetition and make the code easy to read. This doe’s not affect the external behavior of the code but instead makes the code better for the programmers.</p><h4>Other debugging tools for Javascript</h4><ol><li><strong>Pastebin</strong><br><em>Pastebin</em> is a website where you can store text online for a set period of time,It is also a good collaborative debugging tool that allows you to share and modify code snippets while chatting on IRC, IM or a message board.</li><li><strong>The JSON Formatter<br></strong>The JSON Formatter was created to help with debugging. As data expressed as JSON is often written without line breaks to save space, it became extremely difficult to actually read it. This tool hopes to solve the problem by formatting the JSON into data that is easily readable by human beings.</li><li><strong>Blackbird Javascript debug helper</strong><br>Alert()s are widely used to create checkpoints in JavaScript development. Blackbird offers a stylish console to log, view and filters messages in JavaScript, which quickens the development process by eliminating the pause at every alert and analyzing each better.</li><li><strong>Javascript debug tool kit</strong><br>JSDT is software that can debug JavaScript in IE, Firefox, Safari, Chrome, Opera, mobile IE browser and mobile Opera browser. It works in all browsers that support Ajax.</li></ol><h4>Conclusion</h4><p>Code refactoring makes debugging easier and also increase productivity because you program faster when the code is clean and can be easily understood.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e6fe51bda1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Communicating update and seeking clarity]]></title>
            <link>https://medium.com/@aleshinloyelukmony/communicating-update-and-seeking-clarity-85e96aa72333?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/85e96aa72333</guid>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Sun, 09 Jun 2019 21:52:50 GMT</pubDate>
            <atom:updated>2019-06-09T21:52:50.111Z</atom:updated>
            <content:encoded><![CDATA[<h4>Seeking clarity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*cDBKxgRD30TjEgDe0g877A.jpeg" /></figure><p>Seeking clarity is a key and something you should put on the top of your list because making assumption is bad. You should always ask to clarify from the product owner or fellow developer or whomever it is you need to clarify something from.</p><p>According to <a href="http://fierceinc.com/">Fierceinc,</a> reasons why some people avoid seeking clarity, is because they having the mindset that</p><ul><li>The person I need to talk to can’t handle criticism</li><li>Maybe the situation will get better on its own</li><li>This conversation may open up a can of worms that I’m not prepared to handle</li><li>It’s not my job to say something</li></ul><p>This thoughts are almost normal but should be the thoughts in the mind of someone that wants the best for his team and company in a whole because when everyone has different thinking towards something, this would cost time to and reduce productivity between the team members.</p><p>Always ask and clarify no matter the situation you are in.</p><h4>Communicating Update</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGYSA15LxtgkyzTdRXKr3w.png" /></figure><p>Communicating updates help keep everyone on the same page, communication is a crucial part of development. Always make sure to let your team members know what is new and every update because without communicating updates there would might be an incidences of collision, where two or more team members are working on the same output.</p><p>Communicating updates does not only boost teamwork, but they also increase team relationship and productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85e96aa72333" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building effective relationship with my your team]]></title>
            <link>https://medium.com/@aleshinloyelukmony/building-effective-relationship-with-my-your-team-ab3da73603e2?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab3da73603e2</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Sun, 09 Jun 2019 21:25:43 GMT</pubDate>
            <atom:updated>2019-06-09T21:25:43.052Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M82JJ3f10xitXnDUmarhMw.jpeg" /></figure><p>Every developer at one time or the other must have gotten a bug or have to do extra work due to lack of effective communication and relationship between team members, I was also a victim of this, working with a remote team is not that always easy at first, but with the right guidance and support it would eventually be fun.</p><p>When I started Andela’s deferral program, I was to work on a project with a remote team of five members, the first sprint didn’t go so well, everyone was kinda on a different path and not fully aware of what others are doing.</p><p>My team communication was not good enough, but it was made much easier and better by the relationship I had to build with the team. I never assume anything, I always ask to make sure I’m sure of what am doing, had frequent zoom calls to fix bugs together and keep everyone on the same page.</p><p>The second sprint had a lot of improvement and we had a very good increase in productivity, communication and relationship, all these things were not that easy, so how do you make sure that you build an effective relationship with your remote team?</p><h4>How to build an effective relationship with your team</h4><p>Everyone knows communication is a way of building an effective relationship, so I would not be mentioning communication here, but by following these tips, it would actually boost communication as well.</p><ol><li><strong><em>S</em>ocialize your schedule with your team/clients:<em><br></em></strong>Make sure your team member knows you are working and when you are away, socializing your schedule with your team members makes it easy for them to know when to reach out to you, and your commitments. Always let them know when you are away, busy or available.</li><li><strong>Never assume something, always clarify:</strong><br>Making assumptions is the biggest relationship killer, do not assume anything about a person’s identity, their priorities and motivation, or coding conventions and rules, just to name a few.<br>Instead, always ask a question and clarify assumption, because the assumptions would surely reduce communication and therefore a relationship between the team members.</li><li><strong>Discuss outside the box:</strong><br>Let your team members know who you outside your work and codes, share funny stories of each others, talk about how your weekend went, because granting your clients and coworkers little glimpses into your personal life helps them to get a better picture of the multi-dimensional person that you are, building their trust and comfort with you.</li><li><strong>Video call over conference call:</strong><br>From time to time, your team members should opt for a video call instead of a conference, Even make it optional for people to turn on the video, this actually aids relationship and make everyone feel connected.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab3da73603e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The TDD way]]></title>
            <link>https://medium.com/@aleshinloyelukmony/the-tdd-way-acd0a303403a?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/acd0a303403a</guid>
            <category><![CDATA[pelumi]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[andela-bootcamp-nigeria]]></category>
            <category><![CDATA[test]]></category>
            <category><![CDATA[tdd]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Sun, 09 Jun 2019 20:40:29 GMT</pubDate>
            <atom:updated>2019-06-09T20:40:29.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*N1ZqWOCnI5Yg9WaTX5Zsag.png" /><figcaption>TDD lifecycle.</figcaption></figure><p>What is TDD? well TDD is the acronym for Test-driven development, Test-driven development is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests, only.</p><p>In a more friendly way without the vocabularies, Test-driven development can simply be defined as a software development approach in which a test is written before writing the code. Once the new code passes the test, it is refactored to an acceptable standard.</p><p>At first, TDD might seem like a task but I can assure you that the benefits and advantages of writing a test before writing the actual code are bigger than you think.</p><h4>Benefits of Test driven development</h4><ol><li><strong>Forcefully planning ahead:</strong><br>You can not write the test without understanding what you are testing against, so indirectly Test-driven development forces you to first understand and plan what you want to do before writing any code.</li><li><strong>Setting acceptance criteria:</strong><br> When writing some new code, you usually have a list of features that are required or acceptance criteria that need to be met. So after writing your code, you can rest safely in the knowledge that you haven’t missed any work.</li><li><strong>High productivity:</strong><br>Test-driven development keeps you more productive while coding and helps keep that productivity high by narrowing your focus. You’ll write one failing test, and only focus on getting it to pass. It forces you to think about smaller chunks of functionality at a time rather than the application as a whole.</li><li><strong>Safe refactoring:<br></strong>You refactor easier and faster without breaking your code or others code because TDD keeps track of the success of your code. After refactoring any piece of your code, all you need to do is run your test again to confirm you are still on track.</li></ol><p><strong>Conclusion</strong></p><p>Test-driven development can help avoid a lot of needless headaches caused by unknown bugs or someone else mistakenly changing someone else’s code. The organizations following the TDD approach can easily make changes to current applications without disturbing the daily operations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acd0a303403a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips on How To Onboard a Large Codebase]]></title>
            <link>https://medium.com/@aleshinloyelukmony/tips-on-how-to-onboard-a-large-codebase-5d24bbd3f66f?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d24bbd3f66f</guid>
            <category><![CDATA[codebase]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Fri, 31 May 2019 22:22:35 GMT</pubDate>
            <atom:updated>2019-05-31T22:22:35.315Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wnw6C4LJyv7RvStTj1X2aQ.jpeg" /><figcaption>Image Credit: Andela</figcaption></figure><p>Onboarding onto a large codebase might seems tedious if you approach it in a wrong way, which would affect how fast you start contributing to the team. I would state the tips I use in onboarding onto a large codebase.</p><h3>Tips for onboarding onto a large codebase.</h3><ol><li><strong>Do not expect to know everything: </strong>The very first tip I feel you should know is that you can not understand all the whole codebase especially if it is a very large codebase, so it is perfectly nice if you do not understand 100% of the codebase. But you should at least understand 100% of the part you need to start contributing to.</li><li><strong>Understanding the app/project: </strong>You should know what you are working on, you should understand what the app or project does and the features. You can not work on the app/project without knowing exactly what the app is doing. So I would advice to first understand the purpose of the app and what it is used for.</li><li><strong>Read the documentation:</strong> The next place you would want to go is the documentation of the project, some project’s documentation might be outdated or not well written, but you would at least gain one or two more information about how the app works.</li><li><strong>Run/Writing Tests: </strong>Try writing test for the project without any help, run and make sure your test pass. Writing test makes sure you understand what is going in.</li><li><strong>Communication with developers </strong>familiar<strong> with the codebase: </strong>You should ask for clarification on anything that seems confusing from developers that worked on the project before you.</li></ol><h3>Conclusion</h3><p>The 5 tips stated above would help you make the process of onboarding onto a codebase easier. As time goes on, you will be able to read and understand other people’s code more easily.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d24bbd3f66f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Teamwork: It takes two flints to make a fire.]]></title>
            <link>https://medium.com/@aleshinloyelukmony/teamwork-it-takes-two-flints-to-make-a-fire-24e0b03c89bd?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/24e0b03c89bd</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Fri, 31 May 2019 21:46:32 GMT</pubDate>
            <atom:updated>2019-05-31T21:46:32.660Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t__N7op7nY-9423TGsNz7g.jpeg" /></figure><p>Andela’s Deferral program started on the 20th of May, and I was privileged to be part of a good team that consists of bright minded people. We used the Scrum framework for managing our software development.</p><p>We had daily standup every morning at 10 am to discuss what each of us did in the last 24 hours, what each of us plan to do or work on in the next 24 hours and any blockers we are having, so everyone can be on the same page and to prevent someone else from doing another person’s task.</p><p>The whole team uses Slack as the main tool for collaboration and asking questions to get clarifications on what we are working on, I am very much active on <a href="https://open-andela.slack.com/archives/CJU7M0SAZ/p1558959681056200">slack</a> and actively answering and helping team members, a very good example is <a href="https://open-andela.slack.com/archives/CJU7M0SAZ/p1558959681056200"><strong><em>this</em></strong></a><strong><em> </em></strong>and<em> </em><a href="https://open-andela.slack.com/archives/CJU7M0SAZ/p1559295520013400"><strong><em>this</em></strong></a><em>.</em> we communicate on Github through <a href="https://github.com/emp-daisy/HelloBooksLib/pull/18#issue-284135377"><strong><em>Pull Request </em></strong></a>messages and by writing <a href="https://github.com/emp-daisy/HelloBooksLib/pull/4/files#r287872561"><strong><em>comments</em></strong></a> on Pull Request of other members to communicate suggestions or point out errors and also by commenting on Pivotal tracker, I integrated Pivotal Tracker with our slack channel so to get notification for every update, stories started, finished and comments.</p><p>My team’s workflow was a little bit shaky, though I learnt a lot from it. We had several issues like someone writing with different convention different from others, and after delivering your feature, you have to re-pull the updated code and edit again because the workflow was not strict or rather good enough to make things work out easily. This really affected us and the solution I proposed was to have more communications and discussions concerning the workflow and by asking for clarification on the workflow.</p><p>My team required everyone to follow the Eslint Airbnb Javascript coding convention to make sure everyone code well written and is of high quality.<br>By using Eslint, it makes it very easy for any of the team members to contribute faster to other codes and help fix other team member’s bug faster since everyone codes are written in the same style and convention. I also setup HoundCi for the project, that checks if every Pull Request made follows the Eslint Airbnb style</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24e0b03c89bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adaptability is your ability to adapt to changing situations and expectations makes you more…]]></title>
            <link>https://medium.com/@aleshinloyelukmony/adaptability-is-your-ability-to-adapt-to-changing-situations-and-expectations-makes-you-more-6dec2414e44e?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dec2414e44e</guid>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[adaptability]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 16:02:19 GMT</pubDate>
            <atom:updated>2019-04-24T16:11:13.116Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I demonstrated Adaptability at Andela’s Bootcamp.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fz1leVKCwwI3dMmNZuhUOw.jpeg" /></figure><p>Adaptability is your ability to adapt to changing situations and expectations makes you more valuable to a current or prospective employer.</p><blockquote>According to Wikipedia <strong>Adaptability</strong> is a feature of a system or of a process. This word has been put to use as a specialised term in different disciplines and in business operations.</blockquote><p>I have been at Andela Bootcamp for two weeks now, a lot of things have changed about me, and without being adaptable, I probably won’t be writing this blog post today.<br>Adaptability in workspace or anywhere in life is very important, it is a necessary quality in an ever-changing work environment.</p><p>Here at Andela, you are expected to do things fast and they must be in the highest standard, without being adaptable, you can’t cope.<br>Since I started my Andela journey there are couple things i have learnt to adapt to:</p><ol><li><strong>No Sir/Ma </strong>as a Yoruba boy and a teenager, this was very difficult at first and sounds very weird, calling adults by name, but I adapted because it is needed and that shows I’m adaptable.</li><li><strong>Multi-tasking </strong>here at Andela, you are not expected to be just an ordinary coder, you actually have to be a good writer(exactly what I’m doing :). )and also be of good character, you are expected to learn and deliver different things at the same time, I actually thought I was not at multitasking at first, but showing adaptability and growth mindset, I discovered that it was achievable.</li><li><strong>Traffic and late night walk</strong> since I started coming for the bootcamp, I have got used to getting stuck in traffic at nights and also getting late at night, I had always hated getting home or even walking at night, but being able to adapt means you can change anything.</li></ol><p>If I keep going, I would probably write 5 pages of things I got adapted to. Being able to adapt has a lot of benefits as it helps you at the workplace and anywhere in life.</p><h4>Benefits of being Adaptable:</h4><p>1. <strong>Adaptability increases engagement:</strong> Communication plays a crucial role in performance. Adaptive teams are more self-aware: everyone has a turn to speak up, no one dominates the conversation.</p><p>2<strong>. Adaptability reduces procrastination:</strong> Adaptive teams don’t resist reality; they accept it and focus their energy on understanding it. Rather than wasting their time complaining or resisting change, they jump into action.</p><p>3.<strong> Adaptability increases speed:</strong> Not wasting time resisting change or taking care of tasks that are not a priority, allows teams to move faster. The adoption of <a href="https://hackernoon.com/why-the-best-decisions-are-not-perfect-8fd9fce47d6c">safe-to-try decisions</a> helps teams be more agile.</p><p>In conclusion, being adaptable is a necessary quality in an ever-changing work environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dec2414e44e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My love for TDD.]]></title>
            <link>https://medium.com/@aleshinloyelukmony/my-love-for-tdd-9f903b2d566c?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f903b2d566c</guid>
            <category><![CDATA[test]]></category>
            <category><![CDATA[mocha]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 12:21:51 GMT</pubDate>
            <atom:updated>2019-04-17T12:23:39.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJiQgXTj07mXTm_0lwxLVQ.jpeg" /></figure><p>During my preparation for the Andela’s Bootcamp, I learnt about writing a test for your project and how testing makes projects better. At first, the whole idea sounds stressful and useless, you already know why? because why should you waste your time writing a test and also write the whole application again, when the application would not need the test to run.</p><p>I would tell you how I fell in love with writing tests especially writing tests first (TDD) before even building your project, but first let me tell you what Mocha is, Mocha is a JavaScript test framework for Node.js programs, featuring browser support, asynchronous testing, test coverage reports, and use of any assertion library.</p><p>For Andela’s Bootcamp, you can either use Mocha or Jest. But I had to go with Mocha, because of its popularity. I watched a couple of tutorials on youtube, and it was very easy to understand what was going on. I almost did not use Mocha at this time until boot camp’s project.</p><p>Bootcamp project came in, I finished my UI and was ready to start challenge 2. I had to read about how to write good tests and the standard way of writing tests. Then I came across TDD which was actually the Andelan way, TDD is basically a process writing tests first before even building your application, and then building your project to pass the test in the simplest way and keep refactoring while it still passes the tests.</p><blockquote>TDD according to Wikipedia: Test-driven development is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests, only.</blockquote><p>Prior to the boot camp, I’d never really built a full Restful API that does crud operations, Authentications and all, But I made sure I learnt everything in separately which was a not a good idea, but time wasn’t on my side.</p><p>How TDD helped me was that, before jumping straight into writing codes, I had to write test, and before writing any test, I had to understand what I’m testing (which was my project). I took my time to study, then picked up a pen and paper, opened the project spec email. And I started sketching everything down, what request you would make to get what response back and all that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qfg9WdUiUc92Gi08l6Foag.png" /></figure><p>When I was done writing all my tests, I was already feeling like a superhero, because I learnt most people find it difficult writing tests first. But what point am I trying to drive out? Writing the code for the main project was very easy, all I had to do was pick up my sketches and worked with my tests. Checked a couple of articles online, and I finished earlier than I expected. I also made sure I advised people to do the same. <br>Discovering the superpower of TDD was a great thing for me, and would always embrace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f903b2d566c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It is my second day at Andela’s Bootcamp, and I can already say my soft skills has increased…]]></title>
            <link>https://medium.com/@aleshinloyelukmony/it-is-my-second-day-at-andelas-bootcamp-and-i-can-already-say-my-soft-skills-has-increased-e35657247804?source=rss-6d8600761381------2</link>
            <guid isPermaLink="false">https://medium.com/p/e35657247804</guid>
            <category><![CDATA[integrity]]></category>
            <category><![CDATA[epic]]></category>
            <category><![CDATA[passion]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Pelumi Aleshinloye]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 10:57:38 GMT</pubDate>
            <atom:updated>2019-04-16T10:57:38.177Z</atom:updated>
            <content:encoded><![CDATA[<h3>My reflection on Andela’s EPIC values</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QrmEL_m1heZ-gHPAu-my4A.jpeg" /></figure><p>It is my second day at Andela’s Bootcamp, and I can already say my soft skills has increased almost by over 200% compared to before boot camp.<br>Here at Andela, soft skills are valued a lot and they are as relevant as having good tech skills. Andela’s soft skills code is <strong>EPIC </strong>which stands for <strong>E</strong>xcellence <strong>P</strong>assion <strong>I</strong>ntegrity <strong>C</strong>ollaboration, I would break this down for you.</p><h4>EXCELLENCE</h4><p>Andelans values excellence so much and importantly the difference between excellence and perfection. Andelans are always willing to finish what they started and ensure it meets the highest standard. By being excellent you must always thrive to be better than yesterday and know learning never stops.</p><blockquote>Excellence according to Andela is when you aspire to be the best possible version of yourself. You know that your work is a representation of who you are, and you hold everything you do and everyone you interact with to the highest standards.</blockquote><p>At Andela, I learned the difference between excellence and perfection, and I have always chosen excellence.</p><h4>PASSION</h4><p>Passion is when you have a desire for something so much, that giving up is not an option. Passion is different from desire, desire ends once you achieve or get something, Meanwhile passion never ends, That is why Andela values passion a lot. Passion is like the fuel that keeps you going even when things are getting tougher.</p><blockquote>Passion according to Andela is when you believe you can change the world and you act accordingly. You constantly seek to inspire and to be inspired. You approach every goal with unwavering energy and conviction; You embody grit and persistence.</blockquote><p>At Andela, I learned to follow my passion and be ready to work hard to achieve it. The road to success is not easy to navigate but with hard work and passion, everything is possible.</p><h4>INTEGRITY</h4><p>Just two days spent at the boot camp, I can say integrity is valued so much at Andela. All Andelans I had to chance to meet are very honest and showed a consistent and uncompromising adherence to strong moral and ethical principles and values. Integrity is a must-have soft skill at Andela. Everything you say and do must show integrity.</p><blockquote>Integrity according to Andela is when you live in accordance with your values. You know that all you do is a reflection of the values you profess. You embrace the added responsibility of leading by example and want others to hold you accountable.</blockquote><p>I learned to come out plain in everything you do, and the most important part is I learned how to own up to imperfections and speak out when you need help. No one is perfect, learning never ends.</p><h4>COLLABORATION</h4><p>Collaboration is when two or more people work together through idea sharing and thinking to accomplish a common goal. Collaboration is important at Andela and even in every other aspect of life. Andelans trust in WE more than ME.</p><blockquote>Collaboration according to Andela is when you will be able to have a greater impact by joining forces with others. You will know how to effectively collaborate with individuals from different backgrounds, with different beliefs and personalities, in order to achieve our goals.</blockquote><p>Andela thought me how to communicate and collaborate efficiently, and help others while you also receive help from others irrespective of race, beliefs or background.</p><h4>Conclusion</h4><p>Andela is a great place because you would find people with great characters. Where respect and equality are found and everyone treats each other with dignity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35657247804" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>