<?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 Anne Hyacinthe on Medium]]></title>
        <description><![CDATA[Stories by Anne Hyacinthe on Medium]]></description>
        <link>https://medium.com/@annedhyacinthe?source=rss-d1512bcb37d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NRV0vhF3qNEImwkswrsA_A.jpeg</url>
            <title>Stories by Anne Hyacinthe on Medium</title>
            <link>https://medium.com/@annedhyacinthe?source=rss-d1512bcb37d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:10:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@annedhyacinthe/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[The Scheme of a Schema]]></title>
            <link>https://medium.com/the-marcy-lab-school/the-scheme-of-a-schema-f27e74ade503?source=rss-d1512bcb37d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f27e74ade503</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Anne Hyacinthe]]></dc:creator>
            <pubDate>Tue, 04 Aug 2020 11:08:39 GMT</pubDate>
            <atom:updated>2020-08-04T11:11:25.705Z</atom:updated>
            <content:encoded><![CDATA[<h4>The differences between a schema and schemaless database</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywd_QK_ptvoPt5Tk0PAYBA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@artunchained?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Manuel Geissinger</a> from <a href="https://www.pexels.com/photo/interior-of-office-building-325229/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>The best way to learn new concepts is to know the 5Ws and H, but with this topic, not all of these are applicable so by the end of this blog you will know:</p><ol><li>What is a schema?</li><li>How are schema and schemaless databases different?</li><li>Why is each beneficial?</li></ol><h3>What is a schema and what does that mean for the data?</h3><p>A schema is the structure of a database and it encapsulates things such as tables and columns. It allows for normalization and regulation of the data being entered into the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/0*ahkZ2RV728X3_lFb" /><figcaption>A schema database</figcaption></figure><p>So a schemaless database not having a schema allows for data to be entered in any manner the developer finds to be necessary but documents in the same collection closely resemble each other configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/0*aa7d_D5BJBIi-v5E" /><figcaption>A schemaless database</figcaption></figure><h3>How are they different?</h3><p>The first is that schema databases are written in SQL while schemaless databases are written in a NoSQL language (like MongoDB) and utilize JSON documents or key/value pairs. The second difference is that they are used in different types of databases: schemas are for relational databases while schemaless databases are non-relational. A relational database relies on the schemas outline, tables and columns so that relations can be set between tables.</p><p>This causes components of data entries to be separated and placed into their proper table. For example in the first table pictured above the author went to the authors table while the book went to the books table. But in the second picture, we see how a non-relational database instead keeps the entry together.</p><h3>Why are each beneficial?</h3><p>Because of their horizontal scalability, schemaless database scale almost effortlessly. To change the standard of data entry no work is needed. As seen above, only the last entry has an amt property. To do that, I didn’t have to add a column, all that I did was add the property to the JSON document. In a schema database, I at least have to add a column. And if I were to ignore a column that had a NOT NULL constraint, a schema database would not add that entry at all. I would have to alter the entire table to remove the column.</p><p>A schema database allows for the utmost clarity. The data is consistent and with constraints, you know exactly what you’ll be receiving such as whether it’s an integer or characters. The relationships between tables are also clear cut due to foreign and primary keys.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f27e74ade503" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-marcy-lab-school/the-scheme-of-a-schema-f27e74ade503">The Scheme of a Schema</a> was originally published in <a href="https://medium.com/the-marcy-lab-school">The Marcy Lab School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dockers, knockers, tik tokers, what is it?]]></title>
            <link>https://medium.com/the-marcy-lab-school/dockers-knockers-tik-tokers-what-is-it-fa12912e7e4a?source=rss-d1512bcb37d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa12912e7e4a</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Anne Hyacinthe]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 11:01:01 GMT</pubDate>
            <atom:updated>2020-07-27T11:01:01.008Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Dockers, Knockers, Tik Tokers, What Is It?</strong></h3><h4><strong>A high level overview of Docker</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8v3jUTpnfwr6lyAe.jpg" /></figure><p>The best way I know how to understand new technologies is by knowing the 5Ws and the H, so that is what I’m going to do here.</p><h3><strong>Who is Docker for?</strong></h3><p>Docker is for any developer or developer team.</p><h3><strong>What does it do?</strong></h3><p>Docker is a tool that makes it easy to create, deploy, run, and destroy applications. It does this all by utilizing containers. Containers are essentially runtime environments with each having all of the dependencies, libraries and etc. for the application to run.</p><h3><strong>Where will you use a Docker?</strong></h3><p>You can use them any and everywhere and there are benefits for giving each application component (such as the front-end, database, server, etc.) its own container. One of the benefits being that the separation of components allows application components to avoid conflicting dependencies. For example, if there were to be different versions of ESLint in your front-end and backend, that would cause an error but if they were in separate containers they would be read and created as separate entities.</p><p>But how do we put these containers together to form one application? Great question, you can use <a href="https://docs.docker.com/compose/">Docker Compose</a> to run multi-container applications.</p><h3><strong>When will you use Docker?</strong></h3><p>Docker can once again be used any and everywhere because containers can serve any purpose the developer desires. So a developer can very well have one container for development, one for production and another for testing.</p><h3><strong>Why do you want to use Docker?</strong></h3><p>There are a plethora of reasons to use Docker such as the ones that I’ve listed like the ability to avoid dependency conflicts and quickly alter the application. But my two favorites are that due to all Docker containers needing to run on the Docker Engine all containers can be read and run in all environments (such as linux and windows). So, it resolves the common issue of “my code runs on my system but not yours.” The second is that Docker can be used as version control because it does allow you to commit, push and go to prior images.</p><h3><strong>How does Docker create a container?</strong></h3><p>Docker containers are an instance of Docker images and Docker images are assembled by a list of commands that are in a Dockerfile. An image is a read-only immutable template of all the instructions it takes to build the container. An image becomes a container by a writable layer being added to it by running <a href="https://docs.docker.com/engine/reference/commandline/create/">docker create</a>. When it is a container, you can alter the image by taking a screenshot of the container state and adding that as a new layer to the image by running <a href="https://docs.docker.com/engine/reference/commandline/build/">docker build</a> making it the new template model.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa12912e7e4a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-marcy-lab-school/dockers-knockers-tik-tokers-what-is-it-fa12912e7e4a">Dockers, knockers, tik tokers, what is it?</a> was originally published in <a href="https://medium.com/the-marcy-lab-school">The Marcy Lab School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To Do or Not To Do: a walkthrough a To-do application using React Redux]]></title>
            <link>https://medium.com/the-marcy-lab-school/to-do-or-not-to-do-a-walkthrough-a-to-do-application-using-react-redux-764295f16645?source=rss-d1512bcb37d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/764295f16645</guid>
            <dc:creator><![CDATA[Anne Hyacinthe]]></dc:creator>
            <pubDate>Tue, 16 Jun 2020 02:47:45 GMT</pubDate>
            <atom:updated>2020-07-27T03:06:16.818Z</atom:updated>
            <content:encoded><![CDATA[<h3>To Do or Not To Do: a Walkthrough For a To-Do Application Using React Redux</h3><p>The final product from this walkthrough will allow users to create a task, toggle between the task being complete or incomplete and finally deleting the task. The application will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*J2F0zWT4PZ8MEsYeZPvhag.gif" /></figure><p>The first step I took was adding a redux folder to the src folder of my react app. I then added an actions, reducers and store folder in that redux folder.</p><figure><img alt="src folder" src="https://cdn-images-1.medium.com/max/210/1*cZgPKzyX_w4nYnO1GuvN4Q.png" /><figcaption>src folder of react app</figcaption></figure><h3><strong>Actions</strong></h3><p>My second step was building the actions folder. <em>Actions</em> are objects and they carry the data that is taken from the application to the store through a dispatch(will go into detail later).</p><p>My first file created was actionTypes.js. An action must have a type property that says what action is being completed. Types are string literals but it’s common practice to define them as string constants due to the ease it provides with the debugging process because if a type constant was to be misspelled it would throw a ReferenceError while if it was a string it would not throw an error at all. In this file I am just exporting all of the type constants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*v61en9gAiDe52fLt6MIRIA.png" /></figure><p>The second file created was actions.js and in this file are action creators and these are functions that return an action. The action types are imported and are used as the values for action creators type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*wHxERbFtwCwe9u5xDNKMtQ.png" /></figure><h3>Reducers</h3><p>Reducers are pure functions meaning that you should not mutate the input due to side effects being created and instead should clone your input and modify that instead. Reducers take two parameters a state and an action object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*Rz2umxBPOOh5fgWdiZTTMw.png" /></figure><h3>Store</h3><p>The store is an object that holds all of the states in your project and there should only be one. It has a few methods on it such as dispatch a method that calls a state change. A store is created using the createStore function that takes a reducer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*kuOMCjPwnGeEjf64mJnghg.png" /></figure><h3>Dispatch</h3><p>In this walkthrough instead of using the connect function to connect the store to react components I will be using the useDispatch hook an easier and quicker alternative. The useDispatch hook references dispatch so it can be used to dispatch actions the action will reflect the objects used in actions.js but the variables will now have a value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*uJmiEihYJk8ccrTZE1VOMA.png" /></figure><p>The apps repository : <a href="https://github.com/annedhyacinthe/redux-todo-practice">https://github.com/annedhyacinthe/redux-todo-practice</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=764295f16645" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-marcy-lab-school/to-do-or-not-to-do-a-walkthrough-a-to-do-application-using-react-redux-764295f16645">To Do or Not To Do: a walkthrough a To-do application using React Redux</a> was originally published in <a href="https://medium.com/the-marcy-lab-school">The Marcy Lab School</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>