<?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 Hussein Tirawi on Medium]]></title>
        <description><![CDATA[Stories by Hussein Tirawi on Medium]]></description>
        <link>https://medium.com/@htirawi?source=rss-144f0e7dd68c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GdkirENInBIqeRgo8tlf2A@2x.jpeg</url>
            <title>Stories by Hussein Tirawi on Medium</title>
            <link>https://medium.com/@htirawi?source=rss-144f0e7dd68c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:07:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@htirawi/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[100 Tips to Write Clean Code]]></title>
            <link>https://medium.com/@htirawi/100-tips-to-write-clean-code-5bed832a90e3?source=rss-144f0e7dd68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bed832a90e3</guid>
            <dc:creator><![CDATA[Hussein Tirawi]]></dc:creator>
            <pubDate>Mon, 15 Sep 2025 20:35:35 GMT</pubDate>
            <atom:updated>2025-09-15T20:46:27.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6OumuX_BEFCGELN1AF_vg.png" /></figure><p>Writing code is easy.<br> Writing <strong>clean code</strong> — code that is readable, maintainable, and scalable — is a craft.</p><p>Clean code helps teams collaborate better, reduces technical debt, and makes your future self (and teammates) grateful. Over the years, I’ve collected these <strong>100 practical tips</strong> that can help you and your team write cleaner, more sustainable software.</p><p>Here they are 👇</p><h3>📝 General Principles</h3><ol><li>Avoid NULLs</li><li>Keep It Simple (KISS)</li><li>Divide &amp; conquer</li><li>Working ≠ clean code</li><li>Don’t Repeat Yourself (DRY)</li><li>Refactor early &amp; often</li><li>Leave code cleaner than you found it</li><li>Strive for no side effects in functions</li><li>Write code for humans to read</li><li>Readability &gt; cleverness</li><li>Readability &gt; efficiency</li></ol><h3>🧑‍💻 Code Structure &amp; Naming</h3><ol><li>Use solid IDEs</li><li>Master IDE hotkeys</li><li>Set max line width</li><li>Keep proper indentation</li><li>Remove noise words</li><li>Use consistent naming</li><li>Use strong, intention-revealing names</li><li>Use pronounceable names</li><li>Use nouns for class names</li><li>Use verbs for function names</li><li>Use adjectives for booleans</li><li>Prefix your booleans</li><li>Don’t use negative booleans</li><li>Don’t use abbreviations</li><li>Use consistent vocabulary</li><li>Don’t use encodings in names</li><li>Use searchable names</li><li>Use the 3-second rule for function names</li></ol><h3>🧩 Classes, Functions &amp; Modules</h3><ol><li>Keep cohesion high</li><li>One responsibility per class</li><li>One public method per class</li><li>Keep interfaces small</li><li>One responsibility per module</li><li>Order functions by execution order</li><li>Strive for small private functions</li><li>Write small functions (max 8–10 lines)</li><li>Limit function arguments</li><li>Avoid long parameter lists</li><li>Use enums as flags in functions</li><li>Composition &gt; inheritance</li><li>Subtypes must fit their parent types</li><li>Depend on abstractions, not concretions</li></ol><h3>🧹 Cleanliness &amp; Maintenance</h3><ol><li>Delete unused code</li><li>Remove not needed code</li><li>Avoid large classes</li><li>Minimize comments</li><li>No extensive comments</li><li>Don’t state the obvious in comments</li><li>Comments should explain <em>why</em>, not <em>what</em></li><li>Use comments for API docs</li><li>Use comments for implicit behaviours</li><li>Use auto-formatters</li><li>Use formatting standards</li><li>Capture business logic clearly</li><li>Bundle data &amp; functions together</li></ol><h3>🧪 Testing &amp; Quality</h3><ol><li>Test early &amp; often</li><li>Write fast tests</li><li>Write repeatable tests</li><li>Produce thorough tests</li><li>Write deterministic tests</li><li>Write independent tests</li><li>Strive for clean test code (as clean as prod code)</li><li>Don’t use logic in tests</li><li>Don’t use boolean params in tests</li><li>Use meaningful test data</li><li>Use parameterized tests</li><li>Use AAA (Arrange–Act–Assert) pattern</li><li>One behavior per test</li><li>One assertion per test where possible</li><li>Use Should/When naming for tests</li><li>Use descriptive test names</li><li>Write self-validating tests</li><li>Hide irrelevant test data</li><li>Hard-to-test code is a bad smell</li></ol><h3>🔄 Version Control &amp; Workflow</h3><ol><li>Commit early &amp; often</li><li>Link commits to tasks</li><li>Write meaningful commits</li><li>Use present tense in commits</li><li>Use imperative mood in commits</li><li>Pair-programming by default (when possible)</li><li>Do real-time code reviews</li></ol><h3>🎨 Style &amp; Readability</h3><ol><li>Use empty lines to separate logic</li><li>No horizontal alignment</li><li>Avoid magic numbers</li><li>Avoid magic strings</li><li>Declare variables close to usage</li><li>Write code that reads like prose</li><li>Reduce cyclomatic complexity</li><li>Use feature-based folders</li></ol><h3>👥 Collaboration &amp; Practices</h3><ol><li>Collaborate closely with designers and backend engineers</li><li>Participate in Agile rituals (planning, standups, retrospectives)</li><li>Maintain and improve design systems</li><li>Share knowledge and mentor juniors</li><li>Encourage consistent best practices</li><li>Strive for accessibility and performance</li></ol><h3>⚡ Final Reminders</h3><ol><li>Clean code is a discipline, not an option</li><li>Clean code saves time in the long run</li><li>Clean code builds trust in teams</li><li>Clean code is <em>everyone’s</em> responsibility</li></ol><p>✨ <strong>Final Thoughts</strong><br> Clean code is not about writing “perfect” code — it’s about writing code that your future self, your teammates, and even new developers can easily understand and extend.</p><p>Which of these tips do you already follow?<br> And what’s your personal <strong>#1 clean code rule</strong> that you’d add to this list?</p><p>💬 Share your thoughts in the comments — let’s keep learning from each other!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bed832a90e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Month At King Hussein Cancer Center]]></title>
            <link>https://medium.com/@htirawi/month-at-king-hussein-cancer-center-20bbad492c36?source=rss-144f0e7dd68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/20bbad492c36</guid>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[volunteering]]></category>
            <category><![CDATA[summer-camp]]></category>
            <category><![CDATA[cancer]]></category>
            <category><![CDATA[power]]></category>
            <dc:creator><![CDATA[Hussein Tirawi]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 18:49:18 GMT</pubDate>
            <atom:updated>2018-08-03T18:49:18.033Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oNwpDrpc7DxASyIK2ZmEkQ.jpeg" /></figure><p>Yesterday, I’ve finished my voluntary work at the summer camp at <strong>King Hussein Cancer Center</strong>, it was a memorable month…</p><p>This month outdoor recreational program, held annually in the summer at <a href="http://www.khcc.jo/"><strong>KHCC</strong></a>, gives pediatric outpatients a chance to take part in fun-filled activities in a safe environment with family and friends, and a chance to enjoy simply being kids.</p><p>As the fragrance of a beautiful rose, the cancer fighters spread their cute love inside our heart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozludiqfCMr27G_bsWA11A.jpeg" /></figure><p>Learned a lot from them, how to smile even though there is literally nothing to smile about, how to be strong even though life and circumstances try to get you down continuously and how to love and hope even through the darkest time.</p><p>Fighters taught all of us the meaning of victory and success and that is no matter how hard the pain and how difficult the circumstances of life, we surely will overcome all these things by our determination and faith in our God and our strength.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FtFlFzbHIeI9kWdHcZ7XJQ.jpeg" /></figure><p><em>Cancer </em>is so bad <strong>BUT </strong>it is not the end of the world, that’s what they all spread by their beautiful smile and amazing talks.</p><p>I also worked with <strong>GREAT </strong>people, every volunteer has a different character but we all were <em>helping each other</em>, <em>laughing</em>, <em>playing with children</em> and <em>encouraging each other</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*09TUMQ-KFenAwtdPs2lACA.jpeg" /></figure><p>I will be always thankful to God for giving me this opportunity to love, live and hope :D</p><p>May Allah bless you and give you health, always…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20bbad492c36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RBK Experience]]></title>
            <link>https://medium.com/@htirawi/rbk-experience-981c54719359?source=rss-144f0e7dd68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/981c54719359</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[pair-programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[rbk]]></category>
            <dc:creator><![CDATA[Hussein Tirawi]]></dc:creator>
            <pubDate>Sun, 15 Jul 2018 20:25:28 GMT</pubDate>
            <atom:updated>2018-07-15T20:28:51.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*t5bX5MuEjjly5eweGYz85A.png" /></figure><p><strong>RBK </strong>is a career accelerator training producing high quality software engineers.</p><p>The training is 2 phases: <br>Phase 1 which is Prep phase, it’s 4 weeks to prepare you and give you the basics of programming.</p><p>Phase 2 which is immersive phase it’s 12 weeks long, which you hack for +12 hours daily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ja8P23mjwcC_UuP8M7nMJw.jpeg" /></figure><p>Every day at <strong>RBK </strong>is a life change, We start our day by a toy problem which is a brain exercise programming question, you have to do your best to solve it. This question varies between data structure, algorithms, math, etc.</p><p>The program is designed to be intense. It’s about 12 hours of day spent either commuting, in class or working on labs. It’s amazing how much you learn and what you can build after completing a bootcamp. But yes, it’s exhausting.</p><p><strong>Oh yeah, and it’s fun.</strong> Sure, there are panic attacks. But you need to deal with them. Take a deep breath and keep moving. Some days you will find yourself face down in the mud, freezing wet with sergeant yelling at you (your inner voice). Those days are part of the process. But shake it off and realize there is light at the end of the tunnel.</p><p>At <strong>RBK </strong>we had daily<strong> </strong>lectures given by HIR’s. They explain different topics related to programming and computer science concepts.</p><p>Then we hack until the end of the day.</p><p>Hacking time includes breaks to take launch, rest and to meditate :D</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*CcPcEIMeUKB00hAAlsoimA.jpeg" /></figure><h4>Technical learning part of the program ~6 weeks</h4><ul><li>Data Modeling and Classes</li><li>Data Structures and Complexity Analysis</li><li>Inheritance Patterns</li><li>Algorithms</li><li>Browser apps, jQuery, and AJAX</li><li>MVC and Backbone</li><li>ES6, APIs, and React</li><li>Servers and Node</li><li>Server-side Techniques</li><li>Databases</li><li>Authentication</li><li>Deployment</li><li>Angular</li><li>MVP Project</li><li>Greenfield Project</li><li>Thesis Project</li><li>Technical Assessment <em>(full day assessment on what you learned for the first 6 weeks)</em></li></ul><p><em>After this let me share some highlights from my experience at </em><strong><em>RBK</em></strong></p><h3>Be Comfortable Being Uncomfortable</h3><p>One of the recurring themes at <strong>RBK </strong>was your growth as a software engineer is directly proportional to your ability to be comfortable being uncomfortable.</p><p>It’s always been the case that growth comes from uncomfortable and hard circumstances. Adversity breeds character. This experience is no different, it was, is, and will continue to be hard. I’ve been pushed beyond what I thought were my limits. I’ve been asked to be a better version of myself. And after its all said and done, I don’t think I’d want to go back to anything less.</p><p>This is a honestly a pretty big life lesson if you haven’t picked it up yet, but it equally applies to your software engineer growth. Tthe experiences that push you the hardest end up being the ones that grow you the most.</p><h3>Other People (Pair Programming)</h3><p>You will need the help of people around you, whether it is for code review, debugging, explaining things, or just splitting work. Other people are a super valuable resource you cannot forgo, this was especially true in <strong>RBK</strong>. We were practicing through pairs, which helped us to consume so much knowledge in a short period of time.</p><p>For me it was super important to hear how other people thought about things I found confusing. If I had tried to grind my way through the understanding it probably would have taken twice as long for certain concepts.</p><h3>Conclusion</h3><p>Joining <strong>RBK </strong>was the best and the most enriching experience of my life. <strong>RBK </strong>did not only teach me how to code but it also helped me enhance my communication skills, my English and most importantly taught me how to teach myself!</p><p>There was so much more domain and life things I got from <strong>RBK</strong>. I’m not going to say you need to do it now, but if you are serious about looking for a change, especially in career and maybe how you approach things, I’d strongly recommend looking into it.</p><blockquote><em>The most important thing you will learn in RBK is autonomous learning and how to learn like a developer.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=981c54719359" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git, GitHub Manual]]></title>
            <link>https://medium.com/@htirawi/git-github-manual-c3000a3217dd?source=rss-144f0e7dd68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3000a3217dd</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Hussein Tirawi]]></dc:creator>
            <pubDate>Sat, 14 Jul 2018 20:00:03 GMT</pubDate>
            <atom:updated>2018-07-14T20:00:03.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Ga-idVlP3zqya8fj2RCIg.png" /><figcaption>GitHub Contribution Art</figcaption></figure><p>Git can be a very powerful tool for developers if they know what they’re doing, However, if they don’t, the workflow feels more like an obstacle. Although I agree that it can take a bit to understand the fundamentals of git, I strongly believe that learning it is a great investment. Lets start with some basic terminology. Don’t get discouraged if you don’t understand them right now.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#terminology">Terminology</a></h3><p><strong>Commit</strong>: A snapshot of changes to files that have been modified. Before making a commit, the files must be <em>staged</em>. This means that they must be tracked and added to the staging area by using the git add &lt;filename&gt; command.</p><p><strong>Staging</strong>: Before making a commit, tracked files must be <em>staged</em>. Modified, deleted, added, or moved files that are <em>tracked</em> are eligible to be staged. The git add command can be used to stage these modifications. Once staged, the staged files are eligible to be committed with the git commit command.</p><p><strong>Tracked file/folder</strong>: A file or folder that your git repository knows to watch for modifications on/in. Files can be untracked by adding them to a <em>.gitignore</em> file.</p><p><strong>Remote repository</strong>: Because git is a distributed source control system, source control for the same project can reside in many different places at once. For this reason, any repository that is located remotely (i.e. on github) is considered to be a remote repository. Remote repository’s can be cloned (copied) locally, creating a local copy of the repository known as a local repository. Once changes are made in the local repository, you can push changes back up to the remote repository, where other collaborators on the project will be able to see your changes.</p><p><strong>Local repository</strong>: The opposite of remote. This is the repository as it lives locally. You can <em>clone</em> a remote repository locally or use git init to initialize a local repository. Local repositories can be linked to remote repositories.</p><p><strong>HEAD</strong>: In git, HEAD refers to the last commit on the current branch.</p><p><strong>Clone</strong>: The process of pulling the source code from a repository hosted remotely to your local machine, creating a local repository, and then associating that local repository with the remote that it was pulled/cloned from.</p><p><strong>Branch</strong>: A branch can be thought of as an alternate timeline for your repository’s code. When initializing or cloning a repository, a master branch will be created. Creating a new branch will house commits (snapshotted changes) that are not present on the master branch until they are eventually merged back in.</p><p><strong>Fast-forward</strong>: When merging, if the target branch (where you’re merging to) does not contain commits outside of those from the incoming source branch (where you’re merging from), then the target can simply “fast-forward” it’s HEAD to the latest commit on the source branch once it is merged.</p><p><strong>Recursive merge</strong>: When merging, unlike the fast forward, if the target branch contains commits not included by the source branch, a recursive strategy is needed. This will merge all commits into the single target branch and then create a single “merge commit” stating that the branches have merged back together.</p><p><strong>Tags</strong>: Tags are references to specific commits and can be useful for specifying the state of your project at any given point. For example, a tag called v1.0 could be created to represent a specific version of the project and make it easier to reference this commit rather than remembering a commit identifier.</p><p><strong>Rebase</strong>: Can be used to integrate changes from one branch to another, much like merge. Rebase will do 3 things.</p><ul><li>Move all commits that are on the current local branch to a temporary area.</li><li>Add all of the commits from the specified source branch (from branch) to the current branch.</li><li>Add all of the commits from the aforementioned temporary area back onto the current branch.</li></ul><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#setup-basics">Setup &amp; Basics</a></h3><p>git init</p><p>Initializes a local git repository</p><p>git config --global user.name &quot;username&quot;</p><p>Sets the global git user name to be used when making commits.</p><p>git config --global user.email me@myemail.com</p><p>Sets the global git email to be used when making commits.</p><p>git config --global color.ui true</p><p>Sets the global git setting for adding pretty colors on command line</p><p>git status</p><p>Check which tracked files have been modified since the last commit, as well as untracked files.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#adding-files-to-staging">Adding files to staging</a></h3><p>git add . or git add --all</p><p>Add all files and folders that are part of your current working directory to the staging area.</p><p>git add &lt;filename&gt;</p><p>Add a single file to the staging area.</p><p>git add &lt;list of files&gt;</p><p>Adds multiple files. Files are delimited by spaces.</p><p>git add *.&lt;ext&gt;</p><p>Adds all files with the provided extension to the staging area. i.e.</p><p>git add *.txt</p><p>git add &lt;folder&gt;/*.&lt;ext&gt;</p><p>Adds all files in the docs folder with a <em>.txt</em> extension to the staging area. i.e. git add docs/*.txt</p><p>git add &quot;*.&lt;ext&gt;&quot;</p><p>Adds all files of a the provided extension in <em>the whole project</em> to the staging area.</p><p>git add &lt;foldername&gt;</p><p>Add a single folder and all associated modified files/folders in that folder to the staging area.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#removing-files-from-staging">Removing files from staging</a></h3><p>git reset HEAD &lt;file&gt;</p><p>Removes the file from staging, but keeps any modifications made to that file.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#undoing-changes">Undoing changes</a></h3><p>git checkout -- &lt;file&gt;</p><p>Undo all changes to a specific file. i.e. git checkout -- README.md</p><p>git checkout .</p><p>Undo all changes for all tracked files and folders in the current working directory</p><p>git reset --hard HEAD</p><p>Undo all changes for all files and folders (including untracked) back to the HEAD commit.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#creating-a-commit">Creating a commit</a></h3><p>git commit -m &quot;Create a README.&quot;</p><p>Creates a commit of all files that are currently in the staging area.</p><p>The -m flag followed by “Create a README” represents the message that will be associated with the commit, or the <em>commit message</em>.</p><p>Once committed, this “snapshot” of changes is added to the top of your timeline tree.</p><p>git commit -a -m &quot;My commit message.&quot;</p><p>or</p><p>git commit -am &quot;My commit message.&quot;</p><p>Add all tracked files in the current working directory to staging and commit them with the message <em>My commit message</em> in a single step. This however, does not include untracked files.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#undoing-a-commit">Undoing a commit</a></h3><p>git reset --soft HEAD^ (potentially dangerous)</p><p>Undo the last commit (HEAD) and move everything from that commit back into staging on the commit before it (HEAD^).</p><p><em>Caution:</em> Never do this when the commit has already been pushed to a remote repository. Rewriting history is dangerous.</p><p>git reset --hard HEAD^ (potentially dangerous)</p><p>Undo last commit and all pending changes to tracked files.</p><p><em>Caution:</em> Never do this when the commit has already been pushed to a remote repository. Rewriting history is dangerous.</p><p>git reset --hard HEAD^^ (potentially dangerous)</p><p>Undo last 2 commits and all pending changes to tracked files.</p><p><em>Caution:</em> Never do this when the commit has already been pushed to a remote repository. Rewriting history is dangerous.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#amending-to-a-commit">Amending to a commit</a></h3><p>git commit --amend -m &quot;My new commit message&quot; (potentially dangerous)</p><p>Add to the last commit. Optionally, a new commit message can be provided with -m, which will overwrite the previous commit message.</p><p><em>Caution:</em> Never do this when the commit has already been pushed to a remote repository. Rewriting history is dangerous.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#viewing-commit-history">Viewing commit history</a></h3><p>git log</p><p>Shows the latest commits and information about them, including their commit message and date.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#check-file-modifications">Check file modifications</a></h3><p>git diff</p><p>Show unstaged differences since last commit.</p><p>git diff --staged</p><p>Show differences on staged files since last commit.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#managing-remotes">Managing remotes</a></h3><p>git remote add &lt;remote_name&gt; &lt;repo_url&gt;</p><p>Associates a local repository with a remote repository.</p><p>Where <em>remote_name</em> represents any arbitrary name that you would like to reference the remote repository by (origin is commonly used) and <em>repo_url</em> represents the URL to your remote repository, which can be found on your remote hosting provider (i.e. github or bitbucket)</p><p>i.e. git remote add origin <a href="https://github.com/BrandonClapp/process-editor.git">&lt;</a>your_repo_url.git&gt;</p><p>git remote rm &lt;remote_name&gt;</p><p>Removes a remote repository reference from our local repository.</p><p>git remote -v</p><p>Check which remote repositories are associated/linked with a local repository.</p><p>git remote show &lt;remote_name&gt;</p><ul><li>Shows all remote branches and whether they’re being tracked by a corresponding local branch.</li><li>Shows which remote branch each local branch merges with for git pull</li><li>Shows which remote branch each local branch pushes to for git push</li><li>Shows if any local branch is out of date with it’s corresponding remote branch.</li></ul><p>git push &lt;remote_name&gt; :&lt;remote_branch&gt;</p><p>Deletes a <em>remote</em> branch. However, the local branch will still exist. Remember to remove it with git branch -d &lt;local_branch&gt;</p><p>git remote prune &lt;remote_name&gt;</p><p>Removes references to stale/deleted remote branches.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#pushing-to-remote-repositories">Pushing to remote repositories</a></h3><p>git push &lt;remote_name&gt; &lt;remote_branch&gt;</p><p>Pushes the currently checked out local branch to the specified remote branch on the remote repository. <em>remote_name</em> is the same value that is provided when adding the remote, and, in most examples is referred to as <em>origin</em></p><p>Optionally, the -u flag can be provided to set the upstream, resulting in not having to provide the remote name and branch on subsequent pushes. i.e. git push -u origin master.</p><p>If the remote branch that you have specified does not exist in the remote repository, it will be created. This will also link the current local branch to the remote branch that is being pushed to and, as a result, will be the default upstream branch that will be used when simply running git push without specifying a remote repository or branch.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#getting-changes-from-a-remote-repository">Getting changes from a remote repository</a></h3><p>git pull &lt;remote_name&gt; &lt;remote_branch&gt;</p><p>Gets the latest commits from the remote repository on the specified remote branch and merges those changes into your current local branch.</p><p>git pull is the equivalent of performing the following actions</p><ul><li>git fetch</li><li>git merge origin master</li></ul><p>git fetch or git fetch &lt;remote_name&gt;</p><p>Fetch the latest information about the remote repository such as commits and remote branches. Unlike git pull, this will not merge any commits into your current branch.</p><p>Tip: After fetching the remote branch, you can easily create a local branch that is already tracking the remote branch by simply running</p><p>git checkout &lt;remote_branch&gt;.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#cloning-a-remote-repository">Cloning a remote repository</a></h3><p>git clone &lt;remote_url&gt;</p><p>Pulls the source code from a repository hosted remotely to your local machine, creating a local repository, and then associating that local repository with the remote that it was pulled/cloned from.</p><p>This remote reference will be added as <em>origin</em>.</p><p>git clone &lt;remote_url&gt; &lt;local_folder_name&gt;</p><p>Clones the remote repository and puts it in the specified local folder rather than the default name of the repository.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#branching-merging">Branching &amp; Merging</a></h3><p>git branch &lt;local_branch&gt;</p><p>Create a branch on the local repository. i.e. git branch styling might be used for changing styles. This, however, will not change to that new branch.</p><p>git branch -d &lt;local_branch&gt;</p><p>Deletes the specified local branch. i.e. git branch -d styling.</p><p>git branch -D &lt;local_branch&gt;</p><p>Deletes the specified local branch <em>and</em> all un-pushed commits to a remote branch.</p><p>This is helpful for when a remote branch has been deleted and you want to remove the local branch but have commits that were never pushed to the remote branch.</p><p>git branch</p><p>Lists all of the current local branches. The current branch will be indicated by an asterisk, and optionally color formatted.</p><p>git branch -r</p><p>Lists all <em>remote</em> branches.</p><p>git checkout &lt;local_branch&gt;</p><p>Checks out (changes to) the specified branch.</p><p>git checkout -b &lt;local_branch&gt;</p><p>Both creates and checks out (changes to) the branch specified. This is essentially a combination of git branch &lt;branch_name&gt; and git checkout &lt;branch_name&gt; in a single command.</p><p>git merge &lt;from_branch&gt;</p><p>This will merge the commits on a different local branch into the branch which we currently have checked out.</p><p>For example, if I have committed 5 commits to a <em>styling</em> branch and want to merge those back to the master branch, I would first ensure that I have the master branch checked out with git checkout master and then merge the styling branch into master with git merge styling.</p><p>Tip: Upon fixing a merge conflict, using git commit -a will auto-generate a new commit message displaying the conflicted files that were resolved.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#tagging">Tagging</a></h3><p>git tag</p><p>List all of the tags for the repository.</p><p>git checkout &lt;tag_name&gt;</p><p>Checks out the commit that the tag represents. i.e. git checkout v1.0</p><p>git tag -a &lt;tag_name&gt; -m &quot;My tag description message.&quot;</p><p>Creates a tag and provides it a message. i.e. git tag -a beta3 -m &quot;it&#39;s beta, expect bugs!&quot;</p><p>git push --tags</p><p>Pushes tags to the remote repository.</p><h3><a href="http://brandonclapp.com/git/git-reference-useful-commands-overview#rebase">Rebase</a></h3><p>git rebase &lt;from_branch&gt;</p><p>Applies the commits from the <em>from_branch</em> onto the currently checked out local branch, and then applies any commits not present on the <em>from_branch</em> on top of those.</p><p>git rebase --continue</p><p>When a merge conflict is detected from a rebasing, after fixing the conflict, this will continue the rebase process.</p><p>Note: When a merge conflict occurs during a rebase, the result will be that you are no longer on a particular branch.</p><p>git rebase --skip</p><p>When a merge conflict is detected from rebasing, --skip can be used to skip applying the commit that resulted in merge conflict to the rebase operation. (The commit from the target/current branch will not be applied)</p><p>git rebase --abort</p><p>When a merge conflict is detected from rebasing, use the --abort to abandon all hope and give up, resulting in the rebase operation being rolled back.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3000a3217dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript Quiz]]></title>
            <link>https://medium.com/@htirawi/javascript-quiz-f009ef289c36?source=rss-144f0e7dd68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f009ef289c36</guid>
            <category><![CDATA[quiz]]></category>
            <category><![CDATA[brain-training]]></category>
            <category><![CDATA[noconsoleallowed]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Hussein Tirawi]]></dc:creator>
            <pubDate>Fri, 06 Jul 2018 12:08:02 GMT</pubDate>
            <atom:updated>2018-07-06T12:08:02.230Z</atom:updated>
            <content:encoded><![CDATA[<p>Let us do some practice in <strong>JavaScript </strong>and answer these questions without using console.</p><blockquote>Write down your answers.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*QAQqHzdRYLIxLMob9S4KTw.png" /><figcaption>JavaScript Questions</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f009ef289c36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I NEVER LOSE! Either I WIN or I LEARN]]></title>
            <link>https://medium.com/@htirawi/i-never-lose-either-i-win-or-i-learn-a22078dd2b16?source=rss-144f0e7dd68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a22078dd2b16</guid>
            <dc:creator><![CDATA[Hussein Tirawi]]></dc:creator>
            <pubDate>Sun, 14 Jan 2018 14:18:31 GMT</pubDate>
            <atom:updated>2018-01-14T14:25:57.222Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fplay.ht%2Farticles%2Fa22078dd2b16&amp;src=https%3A%2F%2Fplay.ht%2Fembed%2F%3Farticle_url%3Dhttps%3A%2F%2Fmedium.com%2F_p%2Fi-never-lose-either-i-win-or-i-learn-a22078dd2b16&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=play" width="700" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/c44909eb5cac32c00dfb18ca348e2381/href">https://medium.com/media/c44909eb5cac32c00dfb18ca348e2381/href</a></iframe><blockquote><em>“</em> I NEVER LOSE! Either I WIN or I LEARN.<em>.” — </em><a href="https://en.wikipedia.org/wiki/Nelson_Mandela">Nelson Mandela</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5PyVD4eJc_0helQDfLxLpw.jpeg" /></figure><p>If you have the right attitude, there is no such thing as truly losing. Defeat, or losing, is only possible when you give up and quit. Defeat is a state of mind, not a reality. You, and only you, determine whether you lose or whether you had a temporary set back from which you learned more and became stronger.</p><p><em>I never lose. Either I win or I learn</em>. How can I possibly make a statement like, “I never lose?” The answer is because I won’t throw in the towel; I keep coming back. If you beat me one time, you have just won one battle. You can bet your house that I haven’t hung my head, gone to bed, and cried myself to sleep. I will be back, and stronger than before. Sooner or later, I will win; until that time, I will learn and become stronger. <strong>Never </strong>let life or your enemies grind you down.</p><p><em>Never allow a defeatist mentality creep into your mind</em>. Develop the mentality that you never lose; you either win or learn and come back stronger than ever. Face life, and your enemies, with the eye of the tiger. When a tiger misses his prey, it doesn’t go back to its den and give up; it simply regroups, learns its lesson, and go out again and again, until it succeeds in its goal. Be as relentless as the tiger. Never give in and never give up!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a22078dd2b16" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>