<?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 Alex oladele on Medium]]></title>
        <description><![CDATA[Stories by Alex oladele on Medium]]></description>
        <link>https://medium.com/@dragid10?source=rss-5fd014cfab79------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*A06V3x_K41sm6h3U5FqYDA.jpeg</url>
            <title>Stories by Alex oladele on Medium</title>
            <link>https://medium.com/@dragid10?source=rss-5fd014cfab79------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:47:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dragid10/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[How I learned to Think! (Week 1)]]></title>
            <link>https://medium.com/@dragid10/how-i-learned-to-think-week-1-1dbe38608fff?source=rss-5fd014cfab79------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dbe38608fff</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[ibm]]></category>
            <dc:creator><![CDATA[Alex oladele]]></dc:creator>
            <pubDate>Tue, 29 May 2018 21:39:39 GMT</pubDate>
            <atom:updated>2018-05-29T21:39:55.949Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cj2J1VDRdG0u90nXB-_jKw.jpeg" /><figcaption>A random IBM image I got from online</figcaption></figure><p><em>Warning: Pretty long post</em></p><p>For over a year now, while finding out about all of the cool opportunities and internships my friends were getting, I’ve been constantly saying</p><blockquote>“Document your progress. Let the world see what you’re doing, how you’re growing and what you’re learning”</blockquote><p>I’ve always enjoyed reading blogs by my peers because i always made me feel like I was apart of their internship experience. Well the time has finally come for me to my words into practice. I’ll be documenting my summer at IBM, likely on a weekly basis as I don’t think I have the energy to do a daily update. With that I’ll start with my first week!</p><h3><strong>Day 1:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1b8GZDVaLRM9vV6CQlPZXQ.jpeg" /><figcaption>How I was picturing everyone during the onboarding process</figcaption></figure><p>The first day of any new job is always nerve-racking because you never know what to expect. I didn’t know too much about the company culture, nor did I really know anyone working at our campus besides my roommate, and the other 2 interns that were hired (whom I’ve only briefly communicated with through email). I had also made sure to ask my roommate (who started a week before I arrived) <em>at least</em> 10 times what proper dress code would be. After repeatedly assuring me that what I was wearing was fine, we went on our way to work.</p><p>The first day was mostly about company culture than anything else. As interns, they wanted to make sure that we got the right experience, and to do so, we’d have to learn and understand how the company functions. The first thing they did with us Interns was put us all in a room together, and discuss IBM’s values and beliefs. We learned all about the 1–3–9 initiative (One purpose — 3 values — 9 Practices), and how we as new IBMers will need to adopt these values into our everyday work. What we did next really threw me for a loop; Instead of just talking about the values and practices or even just quizzing us, we made an activity out of it. The goal of the activity was to create a story that demonstrated one of the 3 values (without writing any words as part of the story) in a team of 9. It took my team less than 10 minutes, but we were able to pump out two stories that demonstrated two values. The way my team and I were able to communicate ideas after barely knowing each other, was a pretty nice feeling. This nice activity, was immediately followed by a fairly intense game of Jeopardy (which my team lost).</p><p>After all the company introductions, we were given our workstations and sent off to lunch. The cafeteria was so much cooler than I could have anticipated. In the cafeteria are multiple food stations, each containing a variety of very tasty looking food. The way to order at any one of these stations is to use the kiosk next to the designated stations; after you’ve completed any order customizations, you send in your order and have the option to pay straight at the kiosk, or at one of the lines (I promise you that it looks much cooler than I’m describing it). During lunch was also laptop setup time, and let me tell you that setting up a Macbook for IBM use is a <strong>VERY, VERY</strong> long process. Like close to 4 hours long. Either way, while my laptop was setting up, I had the opportunity to meet the rest of the CIO teams in what I believe was my very first meeting. I was extremely glad to have met everyone, and after hearing a little bit about some of the work we’d be doing, I got even more excited about the internship.</p><p>The last task of the day was finally meeting the rest of my team and finally seeing our workspace. The area where my team is located is described as Agile. Imagine a collection of stand-up desks put together in various fashions across an extremely large room, and you basically have the space where I work (again its <strong>MUCH</strong> cooler than I’m making it sound). I was finally able to see where all the developers were in the building, and I knew that they were developers because of the arrangement of their tables. There were some areas with dual-monitor setups and others with curved monitors, while others still, had triple-monitor setups! I was and still am in awe of the entire workspace. I walked over to where my team was located on the floor and took my seat down at the table cluster where I was introduced to the rest of the team as well as my boss. I ended up spending the remaining hour and a half hours of work just setting up my Macbook and conversing. The conversations that flowed were along the lines of “Wow this place is HUGE” and “Did you notice the (insert really cool thing here) in (insert location here)”. Typical newcomer stuff really. After 5 hit, I packed up my belongings and my roommate and I went home, talking about how excited we were about our future work the entire way.</p><h3>The Rest of the Week:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*NA3bJC7vYO8SGPvlh9ZXXg.png" /></figure><p>On the first day, by boss decided that the intern team could learn a little bit more about the project by sitting in on meetings and listening to the conversations that flowed. This would happen for the remainder of the week from when we came in until it was time to leave. As someone who had only actually been in one meeting thus far, I was pretty darn <strong>stoked</strong>! Just the very idea of meetings made me feel very professional. So I walked into those meetings with my mind ready to learn anything and everything. The result of these meetings was a little disappointing. In-between all of the acronyms used and after the initial fascination of attending meetings wore off I learned quite a few things:</p><ol><li>Everything I’ve learned in my Software Engineering major thus far, has been relevant. Which means that the $25k+ that I’m paying in tuition has been worth it.</li><li>In most cases, asking for forgiveness instead of for permission is preferred. Like seriously, I heard this phrase <strong><em>at least</em> </strong>5 times a day.</li><li>Even when you’re the one that scheduled a meeting, most people dislike meetings that run long.</li><li>In that hour that is scheduled for lunch, only a quarter of it is really used for eating, the rest of the time is used to decompress from work and converse. It sounds like something that should be very obvious, but I learned that most don’t like to talk about work during lunch.</li><li>Keeping one’s personal and professional life separate is <strong>very</strong> important to most employees. No one wants to do work stuff outside of work.</li></ol><p>Midway through the week, the interns were scheduled for an IBM agile workshop in which we learned how IBM approached the agile methodology, and let me tell you that this workshop was amazing and informative! I thought I had a grasp of Agile beforehand, but after this workshop, I truly understood how it worked and how and we were going to use it. All requirements meetings after attending this workshop made significantly more sense to me! I can tell you what a Product owner is, and I can tell you what the backlog is, and I can definitely tell you what a showcase is. The workshop put a lot of the things I learned in class in perspective as well, and really changed the way I should be approaching most if not all projects in life.</p><p>My roommate and I decided this week that we were also very sick of traffic on the way home, so we decided that the best way to beat traffic was by going to the gym right after work. That way we’d be killing two birds with one stone! After being a lazy, unmotivated, butt for the entire school-year and never going to the gym when I said I would, it was a real struggle to get into it. I was introduced to the stepper (which is by far my favorite machine), and it definitely kicked my butt in the first 5 minutes of using it, though I’ve definitely been getting better at it. Somehow I had forgotten to bring gym shoes for my first day at the gym (foolish mistake) .I re-learned how to lift and I was reminded to always stretch before working out. So far the plan has been working, as whenever we’re done there’s never any traffic to sit through.</p><p>So far the experience at IBM has been absolutely amazing, and I’m extremely glad I’m here to experience it. All the individuals I’ve met have been wonderfully fantastic and I’ve already learned so much in the just the first week!</p><h3>Thanks for reading!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dbe38608fff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Git is the most important thing you need to learn as a Student]]></title>
            <link>https://medium.com/@dragid10/why-git-is-the-most-important-thing-you-need-to-learn-as-a-student-210a7ff6ddd2?source=rss-5fd014cfab79------2</link>
            <guid isPermaLink="false">https://medium.com/p/210a7ff6ddd2</guid>
            <category><![CDATA[bitbucket]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[university]]></category>
            <category><![CDATA[version-control]]></category>
            <dc:creator><![CDATA[Alex oladele]]></dc:creator>
            <pubDate>Sat, 27 May 2017 03:13:37 GMT</pubDate>
            <atom:updated>2017-05-30T17:25:52.840Z</atom:updated>
            <content:encoded><![CDATA[<p>You know those Medium articles that exaggerate a given topic in order to pull readers in? Yeah, this isn’t one of those (hopefully). As a University Student going into my third year of college, I’ve depended on git more than any other development tool. Before I begin though, let me tell you my history with Git.</p><h3><strong>The Beginning (aka The Wrong):</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*mKEz_dJ6Vb-rvrsjBQM6Jg.png" /><figcaption>Life Without Backups</figcaption></figure><p>My first year of college whenever we’d do any sort of programming in class, it’d get saved to your desktop / laptop, and that was the end of that. There was no backing up your files, there was no rolling back changes to a file. Even when the professor mentioned his “No Lack of Backup excuse” policy, we, being naive college students assumed that nothing would ever happen to our precious data; and for the most part we were right! There might have been the occasional “Write a large amount of code to realize we were doing the entire assignment wrong anyways” issue, in which we’d just start over completely; but there were no backups. No one thought that data loss would happen to them, including me.</p><p>Unfortunately I paid the price during a linux installation gone wrong (read: misread words and installed it over windows when I meant to install it on a separate partition). Of course I didn’t make any backups of my hard drive like LITERALLY EVERY SINGLE TUTORIAL had mentioned, and I instantly regretted it.</p><p>I lost all of my files. Not that I particularly cared about most of them, but I definitely lost all of my assignments too. I had made plans to study my code throughout the summer and improve it, in order to improve myself. Any and all hope of that was gone. Upon reinstallation of Windows 10 on my laptop, I decided that this would be a great time to actually back up my coding assignments; and here’s where the mistake comes in.</p><p>Google Drive, the cloud storage solution, was my backup idea. Since Drive has the desktop app that would sync files to the cloud for you, I figured that it was a great idea! I setup a folder dedicated to all of my coding files and implemented the Google Drive backup solution for a few months. It all worked well, until I started my first Internship and worked on Android Applications. It was then I learned that Android Studio dislikes when you mess with a file (in any way, shape or form) that its protecting. And since Google Drive would constantly back up, it was always messing with files. I would often get failed builds, and runtime errors on seemingly unrelated files generated by Android Studio whenever Google Drive was backing up. My solution was a bust, and Google Drive was a failure (in the sense of being a permanent backup solution for my code)</p><h3>You’re a nice one Mr. Git:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*Tqtx02aoC3ZRfNCaVEg56w.png" /></figure><p>I’ll skip the attempt to try and symlink everything in a crazy self-hosted backup idea (If that doesn’t make sense, then good, because thinking of it now, it didn’t make much sense to me either). After all the planning phases of the <a href="https://play.google.com/store/apps/details?id=com.discoverylabglobal.cyberguide&amp;hl=en">Android App</a> the team would be making, we finally had to build it! The only problem was trying to figure out how we would both work on different aspects of the code at the same time. Luckily, our team advisor had the solution; <strong>GIT.</strong></p><p>Git was a life-changing solution, though complicated at first. To be quite honest, I was using it very blindy at first. I understood that committing and pushing got the file onto Bitbucket as a repository, which was all I really wanted, and I was fairly content with that for a majority of the summer! <a href="https://www.sourcetreeapp.com/">SourceTree</a> made it <em>extremely</em> easy to use Git, and I still believe that it’s the best, most beautiful Git client available to date even if it’s not on available for linux. SourceTree made things significantly easier when we adopted the <a href="https://www.atlassian.com/git/tutorials/comparing-workflows">Gitflow workflow</a>! In short, SourceTree help bring an internship project to life by simplifying merge conflicts, presenting commits in a very visually appealing way and gave me the newfound confidence to start using git regularly.</p><p>Fast-Forward (ha.) to the start of my second year in college when I took an Intro to data-structures course. My Professor was / is a very hip Professor, and was all about teaching his students more than was just required. In order to submit any assignment we had to turn it in with, you guessed it, GIT! Imagine my excitement when I heard that and knew exactly what to do! Although I do not at all consider myself an expert in Git, I was definitely the Git guru for my class. It was even in that class that I learned that Git was a lot more than just a backup solution. Git was a way to quick fix any mistake, Git was the easiest and honestly most efficient way to share code with teams, and Git repositories were basically an accepted form of resumes in the CompSci world. Git is a life-changer that every student should adopt as soon as possible!</p><h3>The One Where It’s the Present :</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9IeSr3dEbUIqkZmjvWXRQ.png" /></figure><p>Now going into my third year as a university student, I can say that I use git daily. With multiple assignments, and projects, it’s easy to just push them all to <a href="https://bitbucket.org/product/education">Bitbucket</a> (my preferred hosting site) ; that way I never have to worry about not being at my own computer, pull my code from any machine and get right to work! Bitbucket makes using Git even better because, I don’t know if you know this but Bitbucket’s parent company, Atlassian, makes some of the most popular production products used in industry. Bitbucket allows for <em>insane</em> repository customization, such as adding useful integrations to make managing code easy and simple! Why reserve a meeting room with a team member, when we communicate via <a href="https://www.hipchat.com/">HipChat</a>. I’m a sucker for cool integrations like that, and that is exactly what has kept me hooked! I think the biggest thing to pushed me to Bitbucket though, was being able to have unlimited private repositories while still being a free-member; which is extremely wonderful for projects that I’m either too ashamed to show, or that I have not finished yet but think will be amazing! I think that Git is an amazing skill (am I allowed to call it a skill?) that every developer should learn, and I think that Bitbucket does a great job of making developers productive, and their projects feel production-level.</p><h3>Top 5 Tips for new Go-Gitters (another ha.):</h3><ol><li><a href="https://www.hipchat.com/"><strong>Commit Early, Commit Often</strong> — There’s nothing worse than when you finish an entire class full of complicated methods, then you make small changes somewhere and break the class. If you commit often, you will know exactly where the class broke, and you’ll have a much easier time fixing it</a></li><li><a href="https://git-scm.com/book/en/v2/Getting-Started-Git-Basics"><strong>Learn how Git works Under The Hood</strong></a> — Even if you’re like me and hate the idea of black-box magic being unmasked, the internals of how Git works is actually pretty cool! Learning how it works will definitely allow you to avoid some problems such as trying to commit two identical files.</li><li><a href="https://www.codecademy.com/learn/learn-git"><strong>Start by Learning Git in the command-line</strong></a><strong> </strong>— You know how when you learn the harder version of something first, it’s much easier to learn the simpler version? I know that I mentioned how wonderful SourceTree is, but beginners should really be able to work Git from the command-line so that you know exactly what commands SourceTree is calling under-the-hood. When you think you’ve got the hang of it, feel free to go ahead and switch to a graphical client</li><li><strong>Beware of Merge-Conflicts </strong>— Seriously merge-conflicts suck. Dealing with merge-conflicts sucks even more. Learn what merge-conflicts are and how they come about, then learn how to effectively squash them. Sometimes they’re accidental, and sometimes they’re completely unavoidable. I would recommend to always deal with merge-conflicts in a visual editor, personally.</li><li><strong>Always add meaningful commit messages </strong>— I know that at 4 AM it can be tempting to just type random stuff as a commit message, because you’re almost tired and you just want to sleep. I promise you that having meaningful (and sometimes funny) commit messages is beneficial in the long-run, because there will come a day where someone else has to root through one of your repo’s in order to understand your code, and they will not understand what “Fixed the thing that was broken” meant. Always develop as if it were another human’s eyes, that includes creating commit messages.</li></ol><p>6. (Bonus Tip)<strong> Eliminate Google Drive as a potential backup / version control system</strong> — If you see any of your friends do it, stop them and tell them of the glorious VCS that is Git. Save them and yourself a lot of heartbreak and frustration by switching to using Git now. (Let it be know that I have absolutely no issues with Google Drive, it’s an amazing service! I just don’t think it’s the best place to store code)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*Hv2jBYQBVlk7EJcW0F5M-w.png" /><figcaption>Now Go and Prosper!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210a7ff6ddd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>