<?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: Alex Tran</title>
    <description>The latest articles on DEV Community by Alex Tran (@alextran).</description>
    <link>https://dev.to/alextran</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%2F692002%2F602bbe71-cf39-4986-8ccc-22e46613d906.jpeg</url>
      <title>DEV Community: Alex Tran</title>
      <link>https://dev.to/alextran</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alextran"/>
    <language>en</language>
    <item>
      <title>HRF Asylum Update</title>
      <dc:creator>Alex Tran</dc:creator>
      <pubDate>Fri, 27 Aug 2021 00:31:48 +0000</pubDate>
      <link>https://dev.to/alextran/hrf-asylum-update-2imp</link>
      <guid>https://dev.to/alextran/hrf-asylum-update-2imp</guid>
      <description>&lt;p&gt;It has been a pleasure working on the HRF Asylum web app. I learned so much getting the upload function to work. How to set up my amazon s3 bucket and to use Multer-s3 to upload multiple files at once. I learned so much about ant design and how to display initial form data, how to do form validation, and how to stylize the components. I learned how Ploty components interact with the ds backend to display the graphs. I wish to have more time with this app, there's still a lot more thing that needs to be done. The review case form still needs to have the correct put request. The user notification tab still needs to get hooked up to the backend. The Plotly graph still needs some styling done. I hope the next group that works on this app will be able to understand the code I wrote for my upload pdf function. It was nice receiving feedback from my peer because that feedback helps me become a better listener. I work hard to get my work done and have no patience for those who waste my time with feedback that doesn't have a good backing or are unprepared for my questioning, sometimes it can be a little difficult for me to differentiate what feedback is important and what I should ignore but I will work on that. Working on this project help me learned a lot about how the ds team interacts with the backend and how the backend interacts with the front end. I didn't know how to use nodemailer, Multer-s3, or ant design before working on this project. Spending the last 4 weeks working on this app help me become a better coder and communicator. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://youtu.be/zxbbQCE2RL8"&gt;https://youtu.be/zxbbQCE2RL8&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Just make a new table</title>
      <dc:creator>Alex Tran</dc:creator>
      <pubDate>Fri, 27 Aug 2021 00:11:30 +0000</pubDate>
      <link>https://dev.to/alextran/just-make-a-new-table-hlj</link>
      <guid>https://dev.to/alextran/just-make-a-new-table-hlj</guid>
      <description>&lt;p&gt;I am working on a project that requires me to link up multiple tables in my database together so it would be more efficient for the front end to grab that information. While linking up my table I encounter a problem. My app originally was designed so that there can be only one judge per case, however, I need each case to have multiple judges. At first, I ponder as to what is the best way of solving this issue. At first, I tried turning all the judges names into a string but then realized that it will be very difficult for the front end to find the id of each judge. Next, I tried making a new copy of the case for each one of the judges but then I then realize that will be very difficult to sort and it may return duplicate data. Finally, I remembered a solution my old instructor taught me, "just make another table". I made a new table linking all of the judges to the case and called it judges_to_case. Now, whenever I join the two tables together I can link them both with my new Judges_to_case table.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>When in doubt console.log it out</title>
      <dc:creator>Alex Tran</dc:creator>
      <pubDate>Tue, 24 Aug 2021 15:20:25 +0000</pubDate>
      <link>https://dev.to/alextran/when-in-doubt-console-log-it-out-1eaa</link>
      <guid>https://dev.to/alextran/when-in-doubt-console-log-it-out-1eaa</guid>
      <description>&lt;p&gt;I'm currently working on an app that requires me to fix a complex feature that allows the user to upload multiple images to Amazon s3 cloud storage and I'm completely lost as to where the problem is coming from. I first looked at the code with my front-end engineer and my data science engineer to get a better understanding of how the feature was originally implemented. I then start from the beginning which is the front-end code. While debugging I found a more efficient way of uploading multiple files so I implemented that and confirm from my back end that the file is being uploaded. I then check the back-end upload function to see if it has successfully uploaded the file to s3. While debugging the back end I decided to re-write the entire upload function keeping what is important and changing what needs to change. Along the way there were a lot of challenges, bugs popping up out of nowhere and happening at different time intervals. One thing that really helped me was console logging every part of the way to see where the function break and to navigate the file structure. And yes, I know that the debugger is way more efficient than putting in console.log but this title wouldn't rhyme and sound as cool. &lt;/p&gt;

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