<?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 Shahzi Rahim on Medium]]></title>
        <description><![CDATA[Stories by Shahzi Rahim on Medium]]></description>
        <link>https://medium.com/@ShaziRahim?source=rss-1071f9efb4a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*52R7v_C5i_LhB7BWg7KFsQ@2x.jpeg</url>
            <title>Stories by Shahzi Rahim on Medium</title>
            <link>https://medium.com/@ShaziRahim?source=rss-1071f9efb4a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:38:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ShaziRahim/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 a Website game using JQuery, Javascript, HTML5 and CSS]]></title>
            <link>https://medium.com/@ShaziRahim/building-a-website-game-using-jquery-javascript-html5-and-css-2d60627a1894?source=rss-1071f9efb4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d60627a1894</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[self-learning]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Shahzi Rahim]]></dc:creator>
            <pubDate>Sun, 17 Dec 2017 21:14:13 GMT</pubDate>
            <atom:updated>2017-12-17T21:14:13.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*uGFyznxircFyHLptHGBvaQ.jpeg" /></figure><p>Man. Being a developer is hard. It’s so much fun when you’re deciding on what you want to create, figuring out what is necessary to know to create something, and finalizing what to have on your creation. Building an application would be a lot more fun too if they weren’t so many bugs involved. So many of them being simple things too.</p><p>Let me start from the beginning.</p><p>As I was approaching the end of my first month in a coding bootcamp, this was finally my chance to start working towards my portfolio that I would be using to enter the job market. I have a lot of aspirations in terms of my portfolio. I really want a kick-ass portfolio, not only because I want to keep my first job search as short as possible, but I feel like the projects of my portfolio would give a good understanding of who I am and where my skills lie. Building impressive projects is a goal of mine but impressive to who? To potential employers? Friends and family? It has to be impressive to me. I’m hard person to impress.</p><p>My first project was a beginners version of Sorry! the board game. I’ve played a similar game growing up called Ludo, and it is still a game that I play time to time now with friends. It’s a game with 4 players, 4 pieces each and the object of the game is to take your pieces around the board setting and come back to your home base without getting ‘cut’. Getting ‘cut’ refers to another player’s piece landing on the same game space as one of your pieces.</p><p>I started off by building Wireframes for this project. Wireframes are whiteboard designs of what you want your site to look like and how you plan on organizing your code to achieve those said designs. My project was only having about three different looks. A landing page, game play page, and an ending page. The thing was, all this was to happen without the page refreshing, meaning that some DOM manipulation will be necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WrQUePmR2YipgQgD67FBEw.jpeg" /></figure><p>This was pretty helpful for me throughout my entire process. By clearly drawing exactly what I wanted, I had a visual of the game in mind throughout the entire process. I had only 6 days to build this project and had came up with a sort of priority matrix to figure out what was the first and foremost essentials so I could at least a working game. My first project and I wanted to emulate a real-life sort of setting, deadlines and all. I was determined to give it my all.</p><p>I started off first by setting my HTML page. I decided that I would be using Flex-box to set a container for my game-board and eventually for the game squares. I built divs inside divs and used clear classes and IDs to differentiate between each of these divs. Using the display property in the CSS file, I turned the display to flex in order to activate other flex properties.</p><p>After getting a simple design going for my board, I got started with my javascript files. A challenge for me was to use ES6’s use of classes to build methods for specific instances as opposed to having free floating functions in the global scope. Other challenges included being able to target my nicely designed flex boxes within my code. I was able to loop through each class but the order was all messed up. My flex-box order was essential for me in order to move my pieces. Without having that down, my game play would suffer significantly.</p><p>So what did I do? I did everything else that I knew I could do. I built pieces into my game, created a event listeners that allowed pieces to move, built a function that would choose a number between 1 and 6 (for the dice portion of my game), and a bunch of other helper functions. Along the way there were a lot of moments where I would just stare at code hoping to catch something that I had might of missed. Many times, simple syntax errors would make my entire code break. I told myself I should just change up my project so at least I’d be able to have something completed by the end of my deadline.</p><p>Thankfully I persevered. I realized that the longer you work on your code the more you figure out things. You end up googling things you might of thought you had down but not really. StackOverFlow was one of my favorite sites by the end of it. Google was my best friend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ww78LXHnc4xp2-V3tVMMjg.png" /></figure><p>Nothing exceptionally sexy about my game. I’ve never been much into design but I love understanding systems and how things work. What I really liked about this experience was that I learned so much along the way and in the end I built what I had in mind and something that has the potential to be much more. Now that I built a game that can have movement, adding players or pieces would only be few more steps. I added some cool animations and audio and I really feel like those smaller details add so much value to the game.</p><p>This was an amazing experience. I’ve got a long way to go before I can consider myself a full on employable developer but I’m already loving the process. Being able to code is so similar to just living life. When things get tough or seem impossible, sometimes just taking a step back from everything gives you a chance to destress and come back with a different perspective. The same goes for code and applications. It’s all about not giving up and staying positive. I can’t wait to keep working on this project and adding new projects onto my portfolio. I am aiming to add functionalities to this game as time goes by while I continue learning more about front and back end technologies. If anyone has an pieces of advice for a growing novice developer or wants to check out my code, feel free to check out my GitHub.</p><p><a href="https://github.com/shazrahim94/Sorry-Game/tree/master/sorry_project">shazrahim94/Sorry-Game</a></p><p>Thanks for the read!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d60627a1894" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flex Box, Animations and other Fun Front End work]]></title>
            <link>https://codeburst.io/flex-box-animations-and-other-fun-front-end-work-1261994412a3?source=rss-1071f9efb4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1261994412a3</guid>
            <category><![CDATA[flexbox]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Shahzi Rahim]]></dc:creator>
            <pubDate>Mon, 04 Dec 2017 05:47:53 GMT</pubDate>
            <atom:updated>2017-12-05T20:59:15.122Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello all</p><p>What a week it has been. Finally getting used to being in a classroom learning code all day. It has been full of ups and downs; lots of moments of hair pulling frustration yet also short moments of triumph. I started this course feeling confident in calling myself an advanced beginner in the subject of Programming, due to my prior knowledge of JS. That is not the case. There is so much to programming than being able to answer some algorithms.</p><p>We started off this week getting deeper into CSS. I got a bit up close and personal with CSS when we had our lessons on properties and the box model. My favorite thing out of those lessons were getting more familiar with CSS position. I was always a bit confused of when to use absolute and when to use relative. Relative to what? What is static? When does fixed come in handy? This all came into play when we started our first Race car program. I was never really big on designing sites for user interface so it was pretty uncomfortable for me. Nonetheless I was able to push through and finished with somewhat of a working site.</p><p>We spent the next day learning how to add Javascript into our sites. This was my first time really combining my knowledge of HTML, CSS, and Javascript. It was hard. A lot of moments I was just staring at my code without knowing what I was supposed to do. That was fun.(Not at all fun.)</p><p>Next up was learning about responsive CSS properties such as transition and animation. From what I have heard about modern day sites, everyone is always talking about some cool Front-end frame work like Angular2 or React. I never understood what was the purpose of learning CSS when there are libraries that can make your site nice looking without knowing too much CSS. I find it cool that there are multitude of things you can do without getting into Frameworks and still have a fun looking site!</p><p>One of the defining moments of this week for me has got to be the learning of FlexBox. I’ve never heard of it before because it is fairly new concept. It finally gained a good traction over the years and understandably so. It makes the layout for our webpages extremely easy.</p><p><a href="https://medium.freecodecamp.org/understanding-flexbox-everything-you-need-to-know-b4013d4dc9af">Understanding Flexbox: Everything you need to know</a></p><p>I found a cool article here on Medium that explains in-depth of what Flexbox is and why it is the greatest thing since animations and transitions were introduced to CSS. Blog writer Ohans Emmanuel is really excited about Flex box and rightly so.</p><p>First off, like most new technology, its pretty easy to understand. Previously, Developers would have to be able to build multiple other divs, use tables, get into ul’s and li’s, and then use stuff like float and position to get their page layout to what they want it to be. Using Flex on the other hand is as easy as changing your display property of a class that holds “flex-container” to “flex”. Then you can start using properties such as flex-direction, flex wrap, align-self, justify-content, order and more.</p><p>For me, I just couldn’t figure out what the “stretch” value would do. Apparently it is the default value for most of the property for Align-content and what it does is it stretches out child elements to the edges of the flex-container set in the parent element. It comes in handy if we want to make the top portion of our container into a nav like state.</p><p>We learned about it a great deal in class, but this article goes way more in-depth. If you guys have time I’d recommend to set some time to check it out(its a long read, about 47 minutes). I see it as a reference as I continue on my journey on becoming a full-stack developer.</p><p>What a great week it has been. I look forward to the following days and seeing how much more my work will improve as I learn new and more effective concepts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1261994412a3" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/flex-box-animations-and-other-fun-front-end-work-1261994412a3">Flex Box, Animations and other Fun Front End work</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>