<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Aaron</title>
    <description>The latest articles on DEV Community by Aaron (@aleviticus).</description>
    <link>https://dev.to/aleviticus</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1249755%2F9f2b3d41-1e1e-4e79-b5b2-b47af6eba582.png</url>
      <title>DEV Community: Aaron</title>
      <link>https://dev.to/aleviticus</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aleviticus"/>
    <language>en</language>
    <item>
      <title>Phase-4 FlatIron</title>
      <dc:creator>Aaron</dc:creator>
      <pubDate>Sun, 10 Mar 2024 23:54:13 +0000</pubDate>
      <link>https://dev.to/aleviticus/phase-4-flatiron-5bof</link>
      <guid>https://dev.to/aleviticus/phase-4-flatiron-5bof</guid>
      <description>&lt;p&gt;In this phase we were able to set up the backend using Flask and SQLAlchemy. This allow us to connect the frontend with the backend and have our tables updated.&lt;/p&gt;

&lt;p&gt;The best part about learning Flask-SQLAlchemy was running the seed file. When running the seed file it allowed us to test our data with our table and the introduction of using faker was very helpful but it saves so much time when trying to update our data and see if the backend is working. While my time during this phase was us still using python and incorporating Flask-SQLAlchemy with CRUD we were able to use Postman to test our data. I was further able to understand the relationship between classes when it came to one to many and many to many relationships. At first it is tricky trying to figure out what model has a one to many and many to many relationship. So when testing our data we had to use serilaization rules in order to to avoid recursion errors. &lt;/p&gt;

&lt;p&gt;Towards the end of this phase when working with this project it allowed us fully use CRUD. While doing the project it allowed us to see when a user makes a user by registering we were able to use cookies and bcrypt which allowed us to save the users session if they was to close the website and come back to stay logged in until they sign out. When using Flask we use validations to make sure a user name, password, and emails is unique. Overall learning python, flask, and SQLAlchemy this allowed me to understand how a application works on establishing a database to hold our data and understand the relationship between different models to our table. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Phase-3-FlatIron</title>
      <dc:creator>Aaron</dc:creator>
      <pubDate>Mon, 04 Mar 2024 03:37:12 +0000</pubDate>
      <link>https://dev.to/aleviticus/phase-3-flatiron-43hj</link>
      <guid>https://dev.to/aleviticus/phase-3-flatiron-43hj</guid>
      <description>&lt;p&gt;In phase 3 beginning to learn Python we were learning about Object-Orientented Programming. With OOP we were able to represent data by using class methods. By doing this we were able to create data for a given class. &lt;/p&gt;

&lt;p&gt;In my final project I used the class methods to initiate the class for the person and the monster to give it its unique attribute. This helps with organizing complex programs to help mimic real world situations. With class methods you can also make a class inherit the other class init from one another, which I feel like helps us any programmer/ developer to handle and modify. &lt;/p&gt;

&lt;p&gt;When trying to understand OOP and class methods in Python it is much more efficient and easier to manage. Within my final project using a cli it was very helpful to be able to just refer a init of a certain class after creating a class method and quickly being able to refer to it later on for the project. Being able to use property and setters to handle whether a class and its init is immutable or mutable helps a lot to when a user is not allow or has certain criteria’s to meet when declaring a certain lets say a age or name for the class.&lt;/p&gt;

</description>
      <category>react</category>
    </item>
    <item>
      <title>Phase-2-FlatIron</title>
      <dc:creator>Aaron</dc:creator>
      <pubDate>Sat, 27 Jan 2024 18:17:00 +0000</pubDate>
      <link>https://dev.to/aleviticus/phase-2-flatiron-52ff</link>
      <guid>https://dev.to/aleviticus/phase-2-flatiron-52ff</guid>
      <description>&lt;p&gt;The reason why phase-2 was impactful was because it allowed us to make our website still a one page application but allowed us to further practice our html, css, and javascript. &lt;/p&gt;

&lt;p&gt;At the very beginning hearing about React being able to have different components so I know what file does what individually allows any programmer/coder where there potential syntax error may lie because it tells you where specifically the error is coming from. Within React we learned about components, props, lists, keys, states and events. When learning javascript from phase-1 and further learning the skills within React I have used, understanding props and getting the information I need from the data I was working it. I felt more comfortable mapping throughout the objects or an array of objects I was working with. At first again I did struggle but then after practicing with different labs I was able to understand how to do the mapping and it made it a little bit easier because I went back and kept practicing what I was really struggling with. &lt;/p&gt;

&lt;p&gt;Unlike JavaScript having on j.s file we had components. When using coming and having the ability to know what components are doing what you can see whats happing within one file. The unique thing about working with react we have to create a state in the app and having to send props to different children’s and its parents in order to send functionality to different components. Doing this was very similar to callback functions to other components. Doing this does get tricky because the user has to understand how the tree of the component flows.&lt;/p&gt;

&lt;p&gt;Towards the end of learning React we learned how to do routes so when the user presses on lets say the login feature, the about, products or cart depending what the website has it allows us to redirect the user to a different page on the application making it easier to pass information. Overall React is a great library for someone who knows Javascript because it allows the user flexibility’s. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Phase-2-FlatIron</title>
      <dc:creator>Aaron</dc:creator>
      <pubDate>Sat, 27 Jan 2024 18:17:00 +0000</pubDate>
      <link>https://dev.to/aleviticus/phase-2-flatiron-1916</link>
      <guid>https://dev.to/aleviticus/phase-2-flatiron-1916</guid>
      <description>&lt;p&gt;The reason why phase-2 was impactful was because it allowed us to make our website still a one page application but allowed us to further practice our html, css, and javascript. &lt;/p&gt;

&lt;p&gt;At the very beginning hearing about React being able to have different components so I know what file does what individually allows any programmer/coder where there potential syntax error may lie because it tells you where specifically the error is coming from. Within React we learned about components, props, lists, keys, states and events. When learning javascript from phase-1 and further learning the skills within React I have used, understanding props and getting the information I need from the data I was working it. I felt more comfortable mapping throughout the objects or an array of objects I was working with. At first again I did struggle but then after practicing with different labs I was able to understand how to do the mapping and it made it a little bit easier because I went back and kept practicing what I was really struggling with. &lt;/p&gt;

&lt;p&gt;Unlike JavaScript having on j.s file we had components. When using coming and having the ability to know what components are doing what you can see whats happing within one file. The unique thing about working with react we have to create a state in the app and having to send props to different children’s and its parents in order to send functionality to different components. Doing this was very similar to callback functions to other components. Doing this does get tricky because the user has to understand how the tree of the component flows.&lt;/p&gt;

&lt;p&gt;Towards the end of learning React we learned how to do routes so when the user presses on lets say the login feature, the about, products or cart depending what the website has it allows us to redirect the user to a different page on the application making it easier to pass information. Overall React is a great library for someone who knows Javascript because it allows the user flexibility’s. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Phase-2-FlatIron</title>
      <dc:creator>Aaron</dc:creator>
      <pubDate>Sat, 27 Jan 2024 18:17:00 +0000</pubDate>
      <link>https://dev.to/aleviticus/phase-2-flatiron-38jm</link>
      <guid>https://dev.to/aleviticus/phase-2-flatiron-38jm</guid>
      <description>&lt;p&gt;The reason why phase-2 was impactful was because it allowed us to make our website still a one page application but allowed us to further practice our html, css, and javascript. &lt;/p&gt;

&lt;p&gt;At the very beginning hearing about React being able to have different components so I know what file does what individually allows any programmer/coder where there potential syntax error may lie because it tells you where specifically the error is coming from. Within React we learned about components, props, lists, keys, states and events. When learning javascript from phase-1 and further learning the skills within React I have used, understanding props and getting the information I need from the data I was working it. I felt more comfortable mapping throughout the objects or an array of objects I was working with. At first again I did struggle but then after practicing with different labs I was able to understand how to do the mapping and it made it a little bit easier because I went back and kept practicing what I was really struggling with. &lt;/p&gt;

&lt;p&gt;Unlike JavaScript having on j.s file we had components. When using coming and having the ability to know what components are doing what you can see whats happing within one file. The unique thing about working with react we have to create a state in the app and having to send props to different children’s and its parents in order to send functionality to different components. Doing this was very similar to callback functions to other components. Doing this does get tricky because the user has to understand how the tree of the component flows.&lt;/p&gt;

&lt;p&gt;Towards the end of learning React we learned how to do routes so when the user presses on lets say the login feature, the about, products or cart depending what the website has it allows us to redirect the user to a different page on the application making it easier to pass information. Overall React is a great library for someone who knows Javascript because it allows the user flexibility’s. &lt;/p&gt;

</description>
    </item>
    <item>
      <title>Phase-1 FlatIron</title>
      <dc:creator>Aaron</dc:creator>
      <pubDate>Fri, 05 Jan 2024 17:36:33 +0000</pubDate>
      <link>https://dev.to/aleviticus/phase-1-flatiron-49cf</link>
      <guid>https://dev.to/aleviticus/phase-1-flatiron-49cf</guid>
      <description>&lt;p&gt;The reason why phase-1 was important to me is that a couple of weeks ago I could have never imagine creating a simple page application.&lt;/p&gt;

&lt;p&gt;I did struggle in the beginning trying to understand all the new information I was starting to learn now. Throughout my first 3 weeks into the program I was able to learn basic variables, functions, arrow functions, anonymous function, arrays, objects, filters, scope and blocked scope. &lt;/p&gt;

&lt;p&gt;Within the first week we went over the basic getting the foundation setup before learning DOM. While learning DOM in the second week we were learning how to incorporate everything together. Being able to create a function With the DOM opened my eye to how from scratch you can create everything from the index.js. &lt;/p&gt;

&lt;p&gt;What really fascinated me was getting the Array(data) being able to filter through the data and create functions, addeventlisteners to the page so we can manipulate what we can see.    &lt;/p&gt;

&lt;p&gt;Throughout my time prepping ourself to the third week being able to create a project from scratch is really helpful. Being able to test myself and build a single page application is an eye opener because to me its only the beginning. I'm excited to see what I can learn throughout my time in the bootcamp.  &lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
