<?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 Taiye Salami on Medium]]></title>
        <description><![CDATA[Stories by Taiye Salami on Medium]]></description>
        <link>https://medium.com/@tsalami44?source=rss-7b88c35206ca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hwNCQWh3GPt_QU5skqyepg.png</url>
            <title>Stories by Taiye Salami on Medium</title>
            <link>https://medium.com/@tsalami44?source=rss-7b88c35206ca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:06:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tsalami44/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[Momentum and Software Development]]></title>
            <link>https://tsalami44.medium.com/momentum-and-software-development-38318338b654?source=rss-7b88c35206ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/38318338b654</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[skills-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[passion]]></category>
            <dc:creator><![CDATA[Taiye Salami]]></dc:creator>
            <pubDate>Wed, 18 Nov 2020 21:57:49 GMT</pubDate>
            <atom:updated>2020-11-18T21:57:49.114Z</atom:updated>
            <content:encoded><![CDATA[<p>In our world, momentum is an essential part of survival. And I don’t mean that in literal terms… momentum might be one of the most important things that keep people’s passion up. While this write-up is specifically targeted towards software developers (traditional students, bootcampers and grads), the lessons can be beneficial to those outside the tech field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*P0qzUSb795UAiWZ2MViGNg.png" /><figcaption>momentum is a product of mass and velocity</figcaption></figure><p>In physics, momentum is an important part of Newton’s second law of motion which states that “the time rate of change of <strong>momentum </strong>of a body is equal to the force acting on that body.” This might sound too technical for some people but for the purpose of this write-up, I’ll focus on the words “<em>force”</em> and “<em>change.” </em>Now, think of momentum as what you get when you’re walking, jogging or running during one of your cardio sessions in the morning. It’s easier for someone to “<em>push</em>” and “<em>change</em>” your direction when you’re walking up to them, not so easy when you’re jogging and a lot harder when you’re running towards them. When you’re not moving, it’s super easy to knock you over.</p><p>In the same vein, lack of activity can lead to deflection from previous interests. As grads, one of the most important things to do is keep up with our coding skills, learning new skills and doing side projects. Getting those github squares green is no easy feat, added to the already tough software development program we have had to go through. But I’ve figured that one sure way to lose steam is to stop doing everything else. The good thing is that momentum can stem from anywhere and can be carried on to other engagements. What I mean by this is that if you could begin something new and make it a stringent daily routine, it might be enough to spur you on to actually creating some time to code. In effect, when you lack momentum about something you used to love doing, it might well be that you just don’t have something else new that you dedicate time for daily. This is because being idle is the greatest way to lose passion or desire for anything else. Get busy on other new involvements today and you might see some renewed passion to code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*rJJKO3t2CRcGFsNypyRTmA.gif" /><figcaption>keeping up with coding needs some passion and drive</figcaption></figure><p>As grads, the goal is almost always to find some place to work and get paid. When this doesn’t happen in our own timeframe, we lose some steam and stop growing our coding skills altogether. On the other hand, when we dedicate some time to other daily routine, it’s less harder to actually plan on picking up coding from where we left off. I’ve seen this happen in my journey outside the bootcamp where some days I feel like actually working extensively on algorithms and data structures while on other days, after certain disappointing outcomes from interviews, I simply do not. I would wonder the need for constant practice when I haven’t seen the positive results. One day turns into days which then becomes one week and at that point I’m struggling to get back on track. Even when I adopted the mindset of “the journey is the goal, not the result”, I still struggled to find that drive. But when I pick up some new routine, I tend to carry that drive through to coding.</p><p>Activities like morning jogs, going fishing, meditation, being in nature, taking up a self-defense class, and sports can help to refocus and give a sense of drive which can be carried over to coding. Daily involvements in all of these can re-ignite interest in coding again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F1iy2LCqgXXGT7xnOuKneQ.png" /><figcaption>picking up new activities like being in nature can help refocus and reignite passion</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38318338b654" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full-Stack Developer Bits]]></title>
            <link>https://tsalami44.medium.com/full-stack-developer-bits-e6527e71ab48?source=rss-7b88c35206ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6527e71ab48</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[web-apps]]></category>
            <dc:creator><![CDATA[Taiye Salami]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 19:48:31 GMT</pubDate>
            <atom:updated>2020-08-10T19:48:31.728Z</atom:updated>
            <content:encoded><![CDATA[<p>This is one story that I’ve thought a lot about before I “qualified” to be remotely close to anywhere near a full-stack developer. In the build up to the commencement of my program at Flatiron school, I relished and also became a little pumped about the fact that in just under four months, I’d have had sufficient fundamental concepts required to be called as one. The responsibility of a full-stack developer in this period was a little overwhelming to me because I didn’t know much about how everything came together but also something I thought would be totally worth my while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EHvQbmuYMHf0gJkM3IWB8g.png" /><figcaption>full-stack developer tools</figcaption></figure><p>Shortly before my program completion, I tried to make the most of my new found knowledge and most importantly thought about how I could convince myself that I’m well on the way to a truly rewarding experience as a developer. I knew my choice of project would ultimately determine this. After a pretty lengthy period deliberating what I’d like to get working on, I decided to create an app called Studious, targeted at college students. The motivation for this is that as a college graduate myself, I’d seen first-hand how the lack of adequate support might break an otherwise level-headed student.</p><p>As a side note: this period made me realize immediately how seemingly easy programs require the most deliberate, precise and well thought-out plans. Before settling for an app targeted at college students, I had a whole variety of functionalities for a diverse group of people I was ready to incorporate into my project… or so I thought. Upon conversing with some of my more-experienced colleagues, I quickly realized this might be too intense for three weeks. The more we discussed, the more I saw I had to downsize… ultimately settling with Studious.</p><p>The Studious app would have two parts to it:</p><ul><li>A place where students could ask questions about difficult concepts they’re encountering in their school work and other students in the community could provide useful help to them, ultimately getting the question resolved.</li><li>An avenue for students to get matched with other students in the community that are looking to acquire certain skill sets but don’t feel motivated enough to go it alone. This means they’d be able to come together in a chatroom to discuss everything from their struggles to the progress they’re making… ultimately motivating each other all the way to skill acquisition completion.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*mvwFKHCx-v-tWqoTosg9AQ.jpeg" /><figcaption>Studious: a community of students helping students</figcaption></figure><p>The Studious app was created using Rails as server which renders JSON data to the client built using JavaScript’s React library. Also because I figured it would be nice to incorporate a chat functionality between students matched together, I opted for socket.io to manage bi-directional data flow and thus a node server to make this happen. Action-cable would have been ideal for the chat functionality given I already had a rails backend but I found a very straight forward node/socket.io setup tutorial which I loved a lot. A combination of different styling technologies and libraries such as bootstrap and material UI were then used to provide the design.</p><p>For the database, I used SQLite because of how easy I thought it was to use with Rails. Setting up the relationships was pretty straight-forward; it wasn’t until I began to expand my functionalities that I realized I’d need to add/change some columns in my tables every now and then. In rendering the database content to the client, I made use of the rails serializer and I’d say this single-handedly made my data structuring super straight-forward.</p><p>In my next blogpost, I’ll be going deep into the code that made my Studious app possible as well as some of the things I learned as I got down to work. Because this was something I enjoyed a lot and filled with different experience, I’d like to know what ideas some of you have per my question below:</p><p><strong><em>Question: What are some of the planning tools you use before, during and as soon as you’re about getting done with a project?</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6527e71ab48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web vs Native vs Hybrid Apps]]></title>
            <link>https://blog.devgenius.io/web-vs-native-vs-hybrid-apps-a63e4bc819e5?source=rss-7b88c35206ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/a63e4bc819e5</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[hybrid-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Taiye Salami]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 02:46:06 GMT</pubDate>
            <atom:updated>2020-07-08T16:58:38.949Z</atom:updated>
            <content:encoded><![CDATA[<p>As a tech newbie, you’re often drawn to think about what apps could be the coolest to develop or build your career upon. These thoughts often end up leaning towards questions about what the future holds for the current platforms through which people access the web. From findings made to better understand some of these concepts, I’ve seen that these questions do not have a definitive answer and as such, mostly comes down to finding a middle ground upon understanding the pros and cons of each platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*AUldhw5DwIYiGL5UjLnnIQ.jpeg" /></figure><p><strong>Web Apps:</strong></p><p>Web apps are built almost entirely of JavaScript, CSS and HTML5 and developers use and rely on frameworks to make this happen. Some of the most important web apps frameworks are: React, Angular, and Vue. Web apps are accessed via browsers, are comparatively much cheaper to build and have a major advantage in that browsers would most likely remain an ever-present resource for people all over the world. It’s a one-size-fits-all kind of app in that as long as the device (laptop or mobile phone) has a browser, it will run well. In terms of accessibility though, a business that has only a web presence is destined to miss out on the huge chunk of traffic available to mobile phone users. <strong><em>Random Question:</em></strong><em> How often do you use a browser in 24 hours compared to a mobile app?</em></p><p>In the mobile age where even toddlers have a mobile device of some sort to access the internet, one can say that deciding on web apps alone is tantamount to doing a big dis-service to a business. Furthermore, if you’re deciding on building a startup, think about how willing prospective users would be to getting on a browser to access your app. People these days hardly store websites and search for them on browsers and so there’s always the chance of web apps losing customers after their first visit. Doesn’t look like that would change anytime soon.</p><p><strong>Native Apps:</strong></p><p>Native apps are apps designed for a particular mobile platform and whose code cannot be shared by other mobile platforms. As the word implies, they are “native” to the platform on which they are built. They are designed to be installed through an app store for instance the play store for android phones and the iOS app store for iPhones. The major advantage of native apps over web apps is that there’s a much larger percentage of returning traffic.</p><p>Native apps are designed by developers using programming languages like Swift or Objective-C for iOS and Java or C++ for android and usually with an SDK (Software Development Kits) provided by their platform. An SDK is like what a framework is to a web app developer. XCode is an SDK for iOS app development while Android Studio is provided by google for android developers. Native apps are faster and more responsive than web apps and can use more device hardwares like camera, mic, compass upon authorization of the apps by phone owners, they can send push notifications to users (facebook, whatsapp, etc) guaranteeing a continued use… giving it an even greater edge over web apps. However, because of the difference in OS platforms between android and iOS, the biggest mobile technology brands, it means building native apps is more cost-intensive than web apps in that you’d have to hire out two different developers to work on the same project and thus startups would thus struggle to come up with funds for these apps.</p><p>There are some SDKs available for building apps across both platforms though, such as Xamarin, React Native, Titanium and Google’s Flutter and big brands such as Facebook, Walmart and Tesla are built using React Native, which combines JavaScript and React.</p><p><strong>Hybrid Apps:</strong></p><p>These apps are designed to function both as web and native apps. They are installed as native apps from app stores but run via “webview”, a simplified browser within the app., meaning they are web apps on the inside. The major advantage of hybrid apps would be that they can be used to study how well-received an app project might be, that is, to prepare a Minimum Viable Product (MVP). Before making huge investments on native apps, you can build an hybrid which has the advantage of being accessible via app stores and can send push notifications to users to see how they interact with the app on subsequent visits. This might give you an idea of whether to proceed with the project or make some adjustments to make it better. From my research, hybrid apps do not hold significant advantage over the other classes. There are frameworks out there that can give developers a head-start when building hybrids: PhoneGap, Ionic and Cordova are some of the popular ones.</p><p>Overall, there isn’t an ideal platform for building apps. One will see that the advantages are not outright for each platform. Mobile app development seem to be an interesting field but also because of the competition, nobody really knows what might be the end of the current big players in the industry. One decade ago, RIM built apps for blackberry phones and are nowhere today. The Symbian OS platform also built apps for Nokia, Motorola, Sony Ericsson, etc. and folded up circa 2010. With that said, no matter what happens, the future of web/mobile software development would sure remain an interesting one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a63e4bc819e5" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/web-vs-native-vs-hybrid-apps-a63e4bc819e5">Web vs Native vs Hybrid Apps</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HTML, Javascript, the DOM… oh and CSS]]></title>
            <link>https://tsalami44.medium.com/html-javascript-the-dom-oh-and-css-8f70d1c67d85?source=rss-7b88c35206ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f70d1c67d85</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Taiye Salami]]></dc:creator>
            <pubDate>Mon, 22 Jun 2020 13:21:44 GMT</pubDate>
            <atom:updated>2020-06-22T13:21:44.993Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to my third post on the series 😎! It’s only week 8 of 15 but feels like I’ve been at Flatiron for ages already. In this post, I’ll be touching on the trio of HTML, JS and the DOM, partly because it’s one of the areas I thought could be easily misunderstood by developers in training.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5GAPClpa09DmNcCslMA23Q.png" /></figure><p>The trio (along with CSS for styling) constitute what’s known as the front end of web applications… the part where the user communicates with the app. While the trio almost always go together, I’ll like to introduce them in parts:</p><p><strong>HTML (HyperText Markup Language): </strong>HTML is a markup language that tells browsers how to display code on the internet. Everything that a web browser renders, from simple texts to pictures, to forms (for login/signup) when a user visits a webpage comprises codes bounded by tags (&lt;&gt;). Each of these codes together with the tags is called an element. An example of an element is a paragraph element: “&lt;p&gt; I love coding &lt;/p&gt;” where the former is known as the opening tag while the latter is called the closing tag. In the case of a picture element, a file or web address of the picture is required to be provided as a source. Pictures are marked with “img” tags. An example of this is: &lt;img src=“example.jpg”&gt;. The browser translates all of these tags into meaningful displays. You can view the HTML code for this blogpost by just right-clicking anywhere on the page and clicking on “view page source”. The source in this case is the file or document sitting somewhere in the medium web application that contains all the HTML elements required to be loaded by the browser.</p><p><strong>DOM (Document Object Model): </strong>The DOM is a programming interface for HTML documents. It can be said to be a clone of the original HTML file, hence the word “model” in its expansion. Even though the DOM is a clone, its structure resembles that of a physical tree: As trees have branches that leads to other branches, the DOM clone of an HTML file arranges the HTML elements in such a way that one element originates from another which further births other elements. As a result, the DOM can be likened to a collection of several parent-offspring relationships / family tree. <strong><em>Through this document, the content displayed on the browser can be modified without the need to edit or change anything in the source HTML file from which it originates.</em></strong></p><p><strong>Javascript: </strong>For the purpose of this blog, this is simply the language used to make a webpage dynamic. It makes it possible to add special effects on webpages and to create a dynamic and interactive experience for the user. In the description of the DOM above, I mentioned that the content displayed on the page can be updated by modifying the DOM while leaving the source HTML unchanged. Javascript is what makes this possible. It is the language that is used to modify the DOM to achieve this purpose. One of the most interesting illustration of DOM manipulation to me is the google map: When you start out on a trip and cover a certain distance, the map adjusts automatically according to the position of your car, revealing some part of the distance yet uncovered. All of these happen without the map reloading to update the current car position. If you miss an exit, the map updates your position automatically and looks for the next exit to take. Without this ability, and if the map were to depend on the driver to physically reload the page to get the updated position, that will amount to a terrible user experience, not to mention the increased chances of accident due to device usage while driving.</p><p>HTML, JavaScript and DOM manipulation are awesome frontend packages that work together to make for a better user experience for our app… or at least that’s their goal. While these will produce the required content to be displayed on web applications, it’s ideal that developers also style their application using a style sheet language. The CSS (Cascading StyleSheet) is used to describe how documents written using a markup language like HTML are presented. Attributes like sectioning, color, fonts, special scrolling effects, etc. are made possible using CSS and it’s safe to say that without a proper CSS design in place, your web app will struggle to keep users or make any real impressions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f70d1c67d85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The MVC Framework]]></title>
            <link>https://tsalami44.medium.com/the-mvc-framework-cfa43889da7?source=rss-7b88c35206ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfa43889da7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[web-apps]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[mvc]]></category>
            <dc:creator><![CDATA[Taiye Salami]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 20:28:35 GMT</pubDate>
            <atom:updated>2020-06-02T20:28:35.485Z</atom:updated>
            <content:encoded><![CDATA[<p>For my second writeup in the software development series, I’d like to give some personal insights into what might be the most central concept to web applications development: the MVC structure. I’ll be giving some level of analogy as to how apps function using relatable real-life illustrations. I’d like to also say that the points expounded in this post wouldn’t be an in-depth analysis of everything MVC; think of it as an attempt to scratch the surface of an integral part of web apps development.</p><p>If you’re an outsider looking in, I know you’re definitely wondering: What is MVC? Well, it is simply what makes your various apps able to do everything you instruct it to do. Yeah, the facebook, instagram, twitter apps on your phones are basically exemplification of MVC at work. Everything from you logging in, checking a profile, making a post, booking a flight, paying for an item on amazon, etc. These all have something to do with the framework that is MVC</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dmXICCnEuM8toPGdwsJ-Xg.png" /></figure><p>MVC is an acronym for Model-View-Controller. An example which immediately comes to mind is a customer that goes to a restaurant for some food. He is in this case the view, he makes some request through the waiter (the controller) and the waiter informs the cook (model) of the request made by the customer. The waiter in turn delivers the food to the customer.</p><p>When you launch your app, you get back what we call the V (view) of the MVC. It is through this view you’re able to read the content of the page and/or “talk to”/communicate with the app. Talking to the app is essentially you sending information for instance “liking” a post on Facebook changes the button to blue. You get an immediate response in this case. In some other cases if you tell the app that you want to see the content of a facebook group, you’d wait a couple seconds for the group’s (view) page to load and you can do some more talking to the app about that group.</p><p>When you click on any content on the app, the Controller (“C” in the MVC) takes your request and directs it to the appropriate channel and the content within that channel is sent back as the view which you then see displayed. The controller fulfills the request by communicating with the Model, which in turn has access to a database that stores all of the information you’re requesting when you click on an item. This same logic applies to when you’re shopping on amazon: Through the view, you see for instance a footwear type you like, click on it and are directed to a page that contains more information about that particular footwear, including its price. If you want to buy, you push a button and the controller requests that a cart model be loaded, taking in that footwear and any other item you want to purchase.</p><p>To go a little bit into actually developing this, let’s write some of the simple parts of these code in the Ruby language. Assumption made here is that there are no Javascript / front end code, no CSS, and this particular amazon only sell shoes. Also, the various routes are assumed to have been pretty much handled by Rails, a framework for the Ruby language. Your typical amazon search bar looks like this (fig. 1):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1j_nnb28z1AclcE2NM1Law.png" /><figcaption>fig. 1: a typical amazon search bar</figcaption></figure><p>This is what the customer gets to see (the view in our MVC structure). The code that made the search bar possible looks something like the one given in fig. 2 below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vxa0nhpyxO39t0FvVU54Kw.png" /><figcaption>fig. 2: code that helps display the search bar in fig. 1</figcaption></figure><p>When the customer enters “air Jordan for men” in the search bar, a controller (C in MVC) action runs, asks some information from the shoe model and gets a response that displays all air Jordan shoes horizontally (fig. 3).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cKPZbqT_u646zBjp7dRYKA.png" /><figcaption>fig. 3: all air Jordan shoes available in database</figcaption></figure><p>This controller action is a single line of code (lines 3–5, fig. 4 below) that collects all shoes in the database (the controller actually calls on the “Shoe” model which in turn requests it from the database). Just imagine database to be a store house for data or information:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WliJRrOFJa8o6K6GlGM_bg.png" /><figcaption>fig. 4: some important controller actions for shoes</figcaption></figure><p>The customer then proceeds to select one of the shoes from all the options and this in turn fires another controller action (line 7–9 of fig. 4) which gets the particular shoe that was selected and sends it to the appropriate view page (fig. 5):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eMkTwDfx_V08uZ7u_duqWw.png" /><figcaption>fig. 5: displaying a particular shoe from a collection of shoes</figcaption></figure><p>Since this is a whole new page displaying just a single item, it means we must have had some code in some specific shoe’s page. The code that renders the above is something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wvcGYNldJnIjOK_Ua1Ekgw.png" /><figcaption>fig. 6: example of code that makes fig. 5 possible</figcaption></figure><p>Note that this code works for every shoe type selected. The code is written in such a way that it’s responsive and can adapt to whatever shoe is selected. The customer then can decide to add this to their cart and checkout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/1*NnOnyjRX-HB9uMn90ToXNg.png" /><figcaption>fig. 7: a typical “add to cart” button on amazon</figcaption></figure><p>The add-to-cart event is also made possible by an appropriate controller action which creates an instance of the cart-shoe “join” model (line 7–9, fig. 8):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mw8_YkfN3Qk9gUfffA9tdw.png" /><figcaption>fig. 8: controller actions for creating a cart and adding a selected shoe</figcaption></figure><p>When the customer pushes “checkout”, a form is displayed in which they can put in their payment information and pay for the shoe.</p><p>And just like that, a customer completes the cycle from search to purchase.</p><p><em>Overall this is a simple way to introduce the MVC structure. It’s intended to only make the reader flow with and understand how code runs together to make the customer experience hitch-free. There are also many different ways to write the same code so this is by no means some authority. Please feel free to let me know of comments, concerns or anything you like about this blogpost.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfa43889da7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life As Unusual — First Weeks Programming]]></title>
            <link>https://tsalami44.medium.com/life-as-unusual-first-weeks-programming-2a34d237bbb9?source=rss-7b88c35206ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a34d237bbb9</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Taiye Salami]]></dc:creator>
            <pubDate>Mon, 11 May 2020 11:20:22 GMT</pubDate>
            <atom:updated>2020-05-11T11:20:22.128Z</atom:updated>
            <content:encoded><![CDATA[<h3>Life As Unusual — First Weeks Programming</h3><p>Before I go into this story, I’d first like to welcome you to my medium page where I’ll be sharing my experience in the world of software development. This is going to go on for as long as it will so feel free to follow for updates upon new releases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/0*GW4KYJQ-EJsepsTJ.gif" /></figure><p>As a young kid growing up in Nigeria, I first heard of the word programmer when I was in elementary school. It didn’t make much sense to me of course but I was told they write a set of computer instructions.</p><p>“What is instructions?,” I’d ask in my mind. I became even more confounded. Now those were about the 2000’s when internet was largely a myth and the only mobile devices were handheld 2-way radios. The earlier I got my mind off this conundrum the better it seemed. Life went by, I came to the US for my masters education and I wanted to develop a skillset just for myself. And I thought… software development.</p><p>Now I had become a little more aware of what programmers do but I had no friend in the field and it was more of a novice outsider looking in. They say sometimes it’s better ‘not to look before you leap, else you look into nothingness’ but in this case, I wasn’t sure that would help in any way. It seemed like I actually needed to do a lot more looking and understand how complicated it was. Along the way, I searched for materials and found some people that claimed they self-practiced to become programmers, some stories were exciting and interesting and some actually challenged me. Anyways, I thought within myself that it was more about finding a skill for me and yes, I wanted to learn that skill. I also wanted a perfect match for a school; “A bootcamp having a great set of programs and activities should make this a possibility in few months”, I thought to myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*sMpcIvygfsyRGa8U.gif" /></figure><p>Then came Flatiron school. Seemed like they had a lot more good reviews and had been in the business for quite some time. “It would be nice to join some school of repute for this.” I enrolled in the cohort that started April 2020. I had opted for the in-person training which would take a total of 15 weeks for completion but because of the coronavirus pandemic that basically put everything on hold, it meant we had to move to online class reception until further notice. Great cohort colleagues and even better instructors who loved what they do, making communication (which is very necessary for novices like me) easier.</p><p>First few days in and it was smooth sailing. It was not until towards the end of the second week that I realized the true meaning of a bootcamp: get ahead of class and catch up when you fall behind… but knowing the meaning alone very nearly does nothing for you. It meant changing your lifestyle if necessary and planning far into the future since everything comes by fast. You have to get used to not having all the answers and you have to search for almost everything. Even experienced programmers in the real world never stop searching for information, we were told. As a student in the bootcamp, you have to maintain your focus, commitment, resolve and never despair during the rollercoaster rides of failing and passing code tests. Let me also mention here that within the first 3 weeks, I changed my work computer three times. With a stable and working laptop, you have a lot of challenges waiting at the door which can be easily overwhelming; changing your workstation is something you don’t want to have to do. Anyways, that’s story for another day.</p><p>I’m enjoying everything thus far about my program, most especially when I imagine the whole world of possibilities open when one have that skill. Within the first 3 lectures, I was already planning what projects I’d like to take on since everything revolved around relating one entity with another… or so I thought LoL. More than classes, there were some other exciting learning activities which gives you some opportunity to know and learn more about working as a team member. It would become very clear that making a good team member is super critical to writing great programs. When I searched about the number of codes that run popular web applications, I was intrigued as to how many smaller teams would have gone into making all that possible.</p><p>Overall, I can say I’m proud to be taking this bold step in my professional life and looking forwards to the challenges and thrills of the next modules. Until then, stay safe and have a great week ahead!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a34d237bbb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>