<?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: George M</title>
    <description>The latest articles on DEV Community by George M (@georgem_it).</description>
    <link>https://dev.to/georgem_it</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%2F851923%2Fa798de64-20bf-4a69-9494-63a78fad4dec.png</url>
      <title>DEV Community: George M</title>
      <link>https://dev.to/georgem_it</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/georgem_it"/>
    <language>en</language>
    <item>
      <title>My (frontend) dev learning journey, part 2: the break and the continuation</title>
      <dc:creator>George M</dc:creator>
      <pubDate>Thu, 05 Jan 2023 19:26:13 +0000</pubDate>
      <link>https://dev.to/georgem_it/my-frontend-dev-learning-journey-part-2-the-break-and-the-continuation-2ac8</link>
      <guid>https://dev.to/georgem_it/my-frontend-dev-learning-journey-part-2-the-break-and-the-continuation-2ac8</guid>
      <description>&lt;p&gt;It has been almost a year since I had first started learning programming. My first (and last) post was in May. So this is an update for me and anyone who stumbles upon this blog and is curious how my dev learning journey went.&lt;/p&gt;

&lt;p&gt;During the months of May and June, I did some simple projects (most of them I left either unfinished or unpolished to perfection). Sharpened my HTML and CSS skills a bit, started grasping JavaScript a bit more. Then, over the months of July and August, I took a small break from programming, because I had to switch focus to my Master's (in a totally unrelated field) work. I had to prepare (and pass) some exams, collect and analyze all the lab work results, and start communicating with my mentor about all the stuff that needed to be done (my grand plan was to defend my thesis before the end of 2022 - and I (spoiler alert) did it successfully, on Dec 21st).&lt;/p&gt;

&lt;p&gt;Then, in the middle of September, I enrolled into a local coding bootcamp, while still battling with my Master's work. In the bootcamp, we went over a lot of JavaScript, and at the end we also learned some basic uses of Node and React. The bootcamp lasted 3 months, and I learned A LOT. The stuff I knew, I perfected; the stuff I had a hard time with (like DOM manipulation), I learned really well, just simply by basically doing it a lot in various problems and tasks we encountered during the bootcamp. I met some awesome people there and really further sharpened my JS skills. The bootcamp also gave me a sense of confidence, and for the first time, I started believing that I could maybe find a job with the skills I acquired. I really liked the backend tutorial that our tutor gave us - it was really short and basic (we went over the basics of setting up an API, a database and a schema, and connecting all that to our frontend), but the methods I saw there really opened my eyes into some stuff I wondered about for a long time, and inspired me to learn more about it all!&lt;/p&gt;

&lt;p&gt;In the meantime, I successfully wrote, submitted and defended my Master's thesis, titled: "Production of bioethanol from photocatalytically processed starch material". So now I have a Master's degree. Yay!&lt;/p&gt;

&lt;p&gt;The bootcamp ended in mid-December, and we have until mid-January to finish a final project, and showcase it to our tutor and the other candidates. &lt;/p&gt;

&lt;p&gt;As of this writing, I am still in the process of creating my final project - a fullstack web app which will be a simpler, humorous version of twitter, called Kriker (roughly translated to Shrieker in English), where you send kriks (shrieks) instead of tweets. I finished probably 95% of the frontend part, and started working on the backend part today. I'll make another post when I'm finished with it all.&lt;/p&gt;

&lt;p&gt;Till next time!&lt;/p&gt;

</description>
      <category>watercooler</category>
      <category>discuss</category>
    </item>
    <item>
      <title>My frontend dev learning journey, part 1: how it's going</title>
      <dc:creator>George M</dc:creator>
      <pubDate>Sat, 21 May 2022 10:44:51 +0000</pubDate>
      <link>https://dev.to/georgem_it/my-frontend-dev-learning-journey-part-1-how-its-going-47no</link>
      <guid>https://dev.to/georgem_it/my-frontend-dev-learning-journey-part-1-how-its-going-47no</guid>
      <description>&lt;p&gt;January 14th 2022, I decided enough is enough. This is the year I will finally become what I've dreamt of for some time: a web developer. As my bio here says, I have a bachelor's degree in food science &amp;amp; technology (and am currently studying for my master's in bioprocess engineering), but after a relentless job hunt and a short-lived job in the industry, I realized I don't really like &lt;em&gt;working&lt;/em&gt; as a food scientist - I enjoyed studying all about it, but the industry was not what I had imagined as a freshman. Low pay, rare job postings, and far away location of the food plants were my top 3 reasons to stop searching for a job in my field. So, I decided to start learning programming/dev stuff, and to jump ship!&lt;/p&gt;

&lt;p&gt;A quick google search pointed me to endless reddit threads with a few strong recommendations: The Odin Project, Freecodecamp, and some Udemy courses. &lt;/p&gt;

&lt;p&gt;As I had some previous HTML/CSS experience (or, at least, I thought that I did), I decided to join Freecodecamp (FCC for short), and started learning all about JavaScript there. At the same time, I stumbled upon a not-that-famous resource, called "watch and code" and started following along the (very) well explained videos. The watch and code guy had a special way of teaching JS - you make a todo app, but through versions - so, version 1 is very simple, where you try to learn what console.log() does, and then it ramps up from there, you learn about the classic stuff (integers, operations, strings, loops, arrays, functions, objects), and apply the knowledge to make your todo app more and more functional. As of writing this blog, I stopped at version 10, because I realized that my HTML knowledge was lacking, but I plan to pick it back up soon!&lt;/p&gt;

&lt;p&gt;I finished most of the "JavaScript Algorithms and Data Structures" course on FCC in a month and a half. I have nothing bad to say about this course, it teaches you the basics of JS programming very well, but it doesn't teach you a lot about researching on your own, using the console, debugging, using an editor and creating your own files, etc.&lt;/p&gt;

&lt;p&gt;In the meantime, I also started The Odin Project (foundations), to refresh/update my HTML/CSS knowledge, and I'm currently finishing up the CSS section, which taught me a lot of neat tips and tricks. Next up is the JS section, which I should be starting in a few days, and that should conclude the foundations part. I also plan on trying out their Full Stack JS course afterwards. Basically, where FCC was lacking, The Odin Project shines: you learn the basics of git/github at the start, they provide some additional material for you to research on your own (and to learn to read documentation), they promote good practice of using VS code and they also push for using Linux (although it's not necessary for a complete beginner to do so, you can do all the exercises on your Windows/Mac machine).&lt;/p&gt;

&lt;p&gt;So that's what I've been doing the last 4-ish months. I could have probably done all this a bit faster, but I had some personal time breaks a couple of times (a few days at a time), and sometimes my uni work eats up the time I would normally spend learning/coding, but I'm taking it one step at a time, and trying to absorb and really understand everything I'm doing.&lt;/p&gt;

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