<?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 Fadi Hakim on Medium]]></title>
        <description><![CDATA[Stories by Fadi Hakim on Medium]]></description>
        <link>https://medium.com/@fadihakim?source=rss-41faa2afabb6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OFGt26eY88cvcBrn.jpg</url>
            <title>Stories by Fadi Hakim on Medium</title>
            <link>https://medium.com/@fadihakim?source=rss-41faa2afabb6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:25:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fadihakim/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[Convention over Configuration (CoC)]]></title>
            <link>https://medium.com/@fadihakim/convention-over-configuration-coc-4e946655bfde?source=rss-41faa2afabb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e946655bfde</guid>
            <dc:creator><![CDATA[Fadi Hakim]]></dc:creator>
            <pubDate>Tue, 01 Sep 2015 10:34:48 GMT</pubDate>
            <atom:updated>2015-09-01T10:35:20.056Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>C</strong>onvention <strong>o</strong>ver <strong>C</strong>onfiguration <strong>(CoC)</strong> is a principle which is heavily used in Ruby on Rails. it emphasise the use of convention which in other words, means using existing patterns and reducing the amount of decisions and hence reducing the amount of configuration needed.</p><p>Ruby on Rails framework have laid out a route for programmers in which they can be more productive and can keep their code DRY.</p><p>For instance, the naming of the classes corresponds to the names of the tables in the database, this is a convention made by Rails.</p><p><em>Fadi and Benjamina</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e946655bfde" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do we use ORM ?]]></title>
            <link>https://medium.com/@fadihakim/why-do-we-use-orm-4a35db6679f0?source=rss-41faa2afabb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a35db6679f0</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Fadi Hakim]]></dc:creator>
            <pubDate>Wed, 12 Aug 2015 09:58:04 GMT</pubDate>
            <atom:updated>2015-08-12T09:58:04.092Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>O</strong>bject-<strong>R</strong>elational <strong>M</strong>apping <strong>(ORM)</strong> is a framework that enables developers to map the world of objects found in OO languages like Ruby, to rose in relational tables found in relational databases like SQL.</p><p>ORM manages the mapping details between a set of objects and underlying relational databases, saving us from doing it manually.</p><p>Separating the responsibility of mapping objects into table, would keep our code focused on the app logic , maintaining <strong>the single responsibility principle</strong>.</p><p>ORM by keeping our code focused on the app logic and the business logic we would significantly <strong>reduce our code</strong> by note repeating the CRUD logic.</p><p>ORM would allow us to implement <strong>the Domain Model</strong>, by modelling real life entities and concepts rather than database structure. ORM provides us with this functionality through mapping between the logical business model and the physical storage model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*G-I6YnpKFuXYFasS7ydmoA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a35db6679f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MVC]]></title>
            <link>https://medium.com/@fadihakim/mvc-af9092cac729?source=rss-41faa2afabb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/af9092cac729</guid>
            <dc:creator><![CDATA[Fadi Hakim]]></dc:creator>
            <pubDate>Tue, 11 Aug 2015 12:58:33 GMT</pubDate>
            <atom:updated>2015-08-11T13:31:02.287Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>M</strong>odel <strong>V</strong>iew <strong>C</strong>ontroller (MVC) is a web architecture used for building user interfaces. The MVC breaks down the process of exchanging data between client (the browser) and the server into 3 different parts and hence 3 different responsibilities:</p><ol><li><strong>Model: </strong>is where the data lives. in our case the Ruby files (later on we would add a Database)</li><li><strong>View: </strong>is what the user sees. We have used HTML, CSS and ERB files.</li><li><strong>Controller: </strong>is the mediator between the view what the user sees and the model is the app logic. the controller delivers requests from the view (the user) to the model in order to change the state of the data accordingly. for that purpose we have been using Sinatra.</li></ol><p>An important thing to mention is that following this model will make scalability of the website or the program easier as we have separated the responsibilities to the three elements mentioned above.</p><p>This is a simplified view of the MVC model whoever it can get more complicated as we introduce databases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*h_1lIsmQZDdlesajwELajg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af9092cac729" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[REST verbs]]></title>
            <link>https://medium.com/@fadihakim/rest-verbs-a4b0be75ed5c?source=rss-41faa2afabb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4b0be75ed5c</guid>
            <dc:creator><![CDATA[Fadi Hakim]]></dc:creator>
            <pubDate>Wed, 05 Aug 2015 10:55:11 GMT</pubDate>
            <atom:updated>2015-08-05T10:55:11.487Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Fadi Hakim and Gius De Santis</em></p><h4>What are the REST verbs?</h4><p>REST (Representational State Transfer) verbs can be summarised by the CRUD acronym. CRUD stands for: Create, Read, Update and Delete.</p><h4>Why do they exist?</h4><p>REST is an architecture style for designing networked applications. Its simplifies the process of connecting machines by simple HTTP to make calls between a client and a server.</p><h4>How do they relate to routing in Sinatra?</h4><p>Each verb can be used in Sinatra in the following way:</p><ul><li><strong>post</strong> → <strong>create</strong></li><li><strong>get → Read</strong></li><li><strong>put → Update</strong></li><li><strong>delete → delete</strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4b0be75ed5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cookies vs Session]]></title>
            <link>https://medium.com/@fadihakim/cookies-vs-session-2d320d8239e2?source=rss-41faa2afabb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d320d8239e2</guid>
            <dc:creator><![CDATA[Fadi Hakim]]></dc:creator>
            <pubDate>Mon, 03 Aug 2015 10:36:02 GMT</pubDate>
            <atom:updated>2015-08-03T10:36:02.380Z</atom:updated>
            <content:encoded><![CDATA[<p>Fadi &amp; Sarah</p><p>Cookies are records of stateful information, concerning user interaction on a website. Cookies store things like items you have in a virtual shopping cart. Cookies are stored on the user’s browser.</p><p>HTTP is state less so in order to relate requests from the client to one another, each new session is given a new ID. The client is given the ID and passes it back with every request. Session ID is stored in the server and communicated to the client’s browser in a session token which usually stored in the form of HTTP Cookie.</p><p>Session ID expire after a short time of activity while Cookies are stored for a longer period.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d320d8239e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>