<?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 Josh Hayles on Medium]]></title>
        <description><![CDATA[Stories by Josh Hayles on Medium]]></description>
        <link>https://medium.com/@joshhayles?source=rss-38874c713e17------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2biN7K7H22MEk9QXuM8o7A.jpeg</url>
            <title>Stories by Josh Hayles on Medium</title>
            <link>https://medium.com/@joshhayles?source=rss-38874c713e17------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:05:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joshhayles/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[Algos, Data, and Big O …]]></title>
            <link>https://medium.com/@joshhayles/algos-data-and-big-o-ff04a00217e8?source=rss-38874c713e17------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff04a00217e8</guid>
            <category><![CDATA[algorithms]]></category>
            <dc:creator><![CDATA[Josh Hayles]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 20:48:19 GMT</pubDate>
            <atom:updated>2022-03-30T20:48:19.027Z</atom:updated>
            <content:encoded><![CDATA[<h3>Algos, Data, and Big O …</h3><p>[Inspired by Raymond Gan and Colt Steele]</p><p>When I first heard of Algorithms (Algos) in Flatiron school I didn’t think much of it.</p><p>When I heard about them again … I started to worry.</p><p>I don’t have a strong math skill / background, and that’s what I began to think about when people were talking about solving Algorithms in programming. And after speaking with many people <em>(successful Senior Software Engineers, Junior Engineers, current students, staff, and previous students who are currently employed)</em> there are no shortages of opinions on the topic of Algos.</p><p>The commonality I’ve seen is that Senior Engineers working at enterprise-level corporations <em>all highly suggest</em> studying Algos and Data Structures on a regular basis. They claim it leads to strong problem-solving abilities that translate (later on) to faster and more efficient code when developing projects.</p><p>They also agreed with each other that most Software companies are interviewing people in ways that require the applicant to have a thorough knowledge in their programming language of choice, and to possess the ability to solve difficult situations using Algo techniques.</p><p>Of course, not all companies require a deep understanding of these practices, so other programmers believe you should know just enough to pass an interview, and that many don’t use Algo processes on the job.</p><p>There’s also another opinion that you should just build projects to get noticed. According to Raymond Gan, if you’re able to build a project that will impress a company enough to hire you without doing a formal Algo Testing interview, then go for it.</p><p>Most Bootcamp grads are not at that level.</p><p>Personally, I will take the route of diving deep into Algo and Data Structures for the first three months. After three months, I’ll assess where I am, what I’ve learned, and then start a project to apply what I’ve practiced and see if it increases my coding abilities.</p><p>It doesn’t mean I won’t build anything. It just means I’m not going to spend all of my time hacking through a project (at least for the first three months).</p><p>Ultimately, it’s about becoming a master practitioner at your ‘first’ programming language of choice. Not trying to do everything at once.</p><p><strong>How to get started/tips with Algos (super-beginner level) inspired by Raymond Gan:</strong></p><ol><li>Choose your primary programming language <em>(this does NOT mean you can’t learn other languages. It’s choosing one at a time to master for Algo practice)</em></li><li><a href="https://fktpm.ru/file/77-data-structures-and-algorithms-with-javascript.pdf">Download Data Structures &amp; Algorithms with Javascript</a> (I’m sure they have others specific to your language of choice). Throughout the book, read the concept and code example, then cover up the code example and code an example from scratch. Obviously it will take a while before being able to accomplish this, but it’s a goal to keep in mind.</li><li>Don’t memorize code. Practice until you understand the IDEA behind the code.</li><li>Complete as many Algo problems as you can <em>(the long-term goal is 50 to 100 completed problems)</em></li><li>Use multiple sources for variety: Leetcode, AlgoExpert, Interview Cake, Udemy Courses, Hacker Rank</li></ol><p><strong>Linked List Example</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Jbgwqih6ZUbuJK8dKzKDNA.png" /></figure><p>Linked lists are arguably the most fundamental data structure to learn.</p><p>Each one points to the next, and the last one points to null.</p><p><strong>Post-Grad activities that will lead to employment (Inspired by Raymond Gan):</strong></p><p>Ideas for making yourself marketable after graduation:</p><ol><li>Github is your resume! Work on developing your Github to showcase what you’re up to.</li><li>Speaking of Github … start contributing to other people’s open source projects. This will give you a better understanding of what it’s like to work on enterprise-level applications. While I’m still figuring out exactly how this works, and it may be difficult to find beginner-level contributions, <a href="https://github.com/firstcontributions/first-contributions">here’s a good place to start.</a></li><li>Solve as many Algo problems as possible!</li><li>Consider getting involved in testing (with Jest, as an example). <a href="https://www.udemy.com/share/1040ZS3@azFzPOmCXMuHrj_83N7jPEKcDXt-J9VvW-8wBuDR6pECOJRK_g7VLXLMMQEinugE/">Here’s a great course on the subject.</a></li><li>Document the journey! According to multiple successful Software Engineers, when contributing to open source projects <em>(your profile information is attached to all of that activity)</em>, solving Algos, and documenting these things along the way (Social media) will eventually turn the heads of people who can offer you career opportunities.</li></ol><p>None of this is fullproof, and there’s no one way to accomplish this. Everyone is different and is at a different place in their journey. Some may be naturally better at solving Algos than others, and some might offer other areas of expertise that Algos don’t apply to.</p><p>The general idea is to put as much of this together as possible. It’s like an Athlete training for the Olympics … they have a primary focus (i.e. Gymnastics) but the training involves a wide variety of exercises to fully prepare them.</p><p><strong>Resource Links</strong></p><ol><li><a href="https://eloquentjavascript.net/Eloquent_JavaScript_small.pdf">Eloquent Javascript Book (PDF)</a></li><li><a href="https://fktpm.ru/file/77-data-structures-and-algorithms-with-javascript.pdf">Data Structures and Algorithms with Javascript</a></li><li><a href="https://www.udemy.com/share/1040ZS3@azFzPOmCXMuHrj_83N7jPEKcDXt-J9VvW-8wBuDR6pECOJRK_g7VLXLMMQEinugE/">Udemy course for learning how to test in React with Jest</a></li><li><a href="https://www.youtube.com/watch?v=-EDUhPg6930&amp;list=PLpPXw4zFa0uKKhaSz87IowJnOTzh9tiBk&amp;index=11">Linked List Example Video</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff04a00217e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full-Stack Software Engineer]]></title>
            <link>https://medium.com/@joshhayles/full-stack-software-engineer-b029151371c1?source=rss-38874c713e17------2</link>
            <guid isPermaLink="false">https://medium.com/p/b029151371c1</guid>
            <category><![CDATA[flatiron-school]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Josh Hayles]]></dc:creator>
            <pubDate>Tue, 15 Mar 2022 02:06:30 GMT</pubDate>
            <atom:updated>2022-03-15T02:06:30.404Z</atom:updated>
            <content:encoded><![CDATA[<p>[update on my experience at Flatiron]</p><p>Well, phase 3 is in the books! We’re now in Phase 4 of Flatiron’s 5-phase Software Engineering program.</p><p>How does it feel?</p><p>AWESOME!!!!!!</p><p>If you recall from my previous rants about my emotional state and the hell-of-a rollercoaster ride I’m on with this curriculum … I’m finally at a place where I’m not overwhelmed with new material, and I’m applying the last piece to the full-stack puzzle …</p><p><strong>Rails (MVC)</strong></p><p>Rails is a framework <em>(technically, it’s capable of building a full-stack environment, but I’m using it for the back-end)</em> written for Ruby and used by some of the greatest websites and social media platforms we know today.</p><p>It revolves around the Model, View, Controller (MVC) framework to follow what they call convention over configuration. It’s a high-level organization opportunity that allows developers to separate concerns and organize their applications properly. You have to follow their standard conventions, which takes away some “freedom”, but it’s for the best because it eliminates the need for developers to decide how their code should be organized, and provides a template for them. This not only frees up their time greatly and allows them to focus on creating, it also creates an entire world of other developers who are following the same practices (easier connection to understanding other applications).</p><p><strong>Active Record</strong></p><p>I’ve also learned how to utilize a powerful tool called Active Record, which makes querying a database SO MUCH simpler. It works in conjunction with SQL queries and makes the commands easier to write, read and understand. Under the hood, Active Record writes the complex SQL data queries while all we have to learn are the simple lines of code Active Record provides.</p><p>For example:</p><p>SQL Query: <strong>SELECT * FROM cheeses</strong></p><p>Active Record turns this into a simple: <strong>Cheese.all</strong></p><p>Pretty cool!</p><p>Something else I love about Rails are how simple the commands are:</p><p><strong>Rails Generators</strong></p><p>Rails generators allow you to quickly create/install a large list of helpful files to give you a fast start for a project.</p><p>Here are some basic examples:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3G2DYCE-1D5NX0q5qp2jw.png" /></figure><p><em>*the — no-test-framework flag is only used to make sure Flatiron’s tests aren’t interfered with. That flag is not needed outside of Flatiron’s program*</em></p><p><strong><em>rails g resource</em></strong> is probably the coolest command that saves you a lot of time. When you use that it creates your migrations, models, and controllers in one swoop! So cool.</p><p><strong>Model</strong></p><p>A Rails Model is typically referred to as holding the <em>logic</em> of the application. Some teachers use a kitchen analogy, which states the Model is the kitchen (or Chef) where everything is prepared.</p><p>The Model communicates with the database via Active Record because it has direct access to the data.</p><p><strong>View</strong></p><p>A Rails View file is the <em>dinner table</em> (keeping in-line with the restaurant analogy some teachers use). The table doesn’t do anything but sit there and hold the food when it arrives. This file does not hold any programming logic, it just renders what is sent to them by the controller.</p><p><strong>Controller</strong></p><p>The controller is the <em>waiter</em>. The waiter “takes the order from the customer at the table”, then takes it to the kitchen, or Chef, then brings the food back to the customer at the table.</p><p>In other words, the controller is the middle-man for it all.</p><p>I’m really digging Ruby and Rails! I can’t wait to build more projects with it and learn more.</p><p>If you’re interested in learning more about Rails you can start by <a href="https://world.hey.com/this.week.in.rails">joining their email list here.</a></p><p>They also have great information on their <a href="https://rubyonrails.org/">main page.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b029151371c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A 5 Step Process to Finding a Study Rhythm in Flatiron’s Software Engineering Program]]></title>
            <link>https://medium.com/@joshhayles/finding-a-study-rhythm-in-flatirons-software-engineering-program-c1905f7176b2?source=rss-38874c713e17------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1905f7176b2</guid>
            <category><![CDATA[flatiron-school]]></category>
            <dc:creator><![CDATA[Josh Hayles]]></dc:creator>
            <pubDate>Mon, 07 Mar 2022 23:20:58 GMT</pubDate>
            <atom:updated>2022-04-19T01:15:12.987Z</atom:updated>
            <content:encoded><![CDATA[<p><em>[Update on my Flatiron Software Engineering Journey]</em></p><p>What does finding a Rhythm in a coding bootcamp mean? Is it necessary?</p><p>After I went through Phase 1 in Flatiron (we learned Javascript) I quickly realized that I needed to create a learning structure for myself. Even though I kept organized notes, with the amount of material I needed to keep up with <em>(it’s very difficult to read everything that’s opened up to you)</em> I never felt confident deciding when I needed to move on to the next topic. Some labs were more difficult than others, and required additional time and research to complete. And while you’re working on that there could be two or three additional modules opened up that needs to be looked at too.</p><p>So, I created a 5 step process to help me keep track of where I was with the material, <strong>measured not by how much of it I was consuming, but how <em>confident</em> I was:</strong></p><ul><li>Introduction</li><li>Research</li><li>Basic Understanding</li><li>Practice</li><li>Comfort</li></ul><p><strong>Step 1: Introduction.</strong> Being introduced to the topic in the sense of understanding some of the new vocabulary, the general purpose, and what the topic’s overall purpose or role is within the context of what we’re learning.</p><p><strong>Step 2: Research.</strong> This is the phase where I research more about the topic, using the new vocabulary given to us, I watch videos, read additional articles, and overall spend a handful of hours gathering more information. This is also the phase where it’s helpful to consume other people’s teachings because having multiple ways of being taught helps solidify the material.</p><p><strong>Step 3: Basic Understanding.</strong> At this level I can have a decent conversation with someone about what’s happening and what’s being discussed. I also know more about how to apply the topic within the context of solving basic labs, small coding exercises, and I feel ready to put it into practice.</p><p><strong>Step 4: Practice.</strong> During the practice phase is where I tackle more difficult labs, ask additional questions, and put the new material into actual coding practice. This may include code-alongs (which still explain what to do), but will escalate into intermediate lab solutions, and reaching a point in this process where I can say I’m confident with the material and ready to tackle advanced labs.</p><p><strong>Step 5: Comfort.</strong> This is the last phase in the process <em>(in regards to consuming material). </em>Being comfortable with the material means I can not only apply it to my project, if I want, but I also don’t have to rely as much on my notes or doing research. I’ve solidified the teaching in a way that I’m even comfortable teaching it to others. It doesn’t necessarily mean having ‘mastered’ it all, but at this level passing the code challenge and completing advanced labs will be relatively easy.</p><p><strong>Introduction: How Javascript is Synchronous</strong></p><p>An example of an introduction is how Javascript is Synchronous. You can <a href="https://www.youtube.com/watch?v=pIjfzjsoVw4&amp;t=3s">watch a great video here.</a></p><p>Note to self … I rarely reach the Comfort phase. The level of comfort I’m referring to will take months of additional practice before I can say I’m truly at a comfortable level with it.</p><p>That’s it! As with most discussions like this, the 5 step process is what works for me. Everyone is different, and they learn at different paces and in different ways. For me, following this guideline helped me make a decision on when I can or can’t move on to something new in the program. If I’ve only been through the introduction part of a topic and more material is released, I needed to get through <em>Step 3: A Basic Understanding</em> before I could move on to something new. It didn’t make sense to try something new without having at least a basic understanding of the current material first. I didn’t expect to get all the way to comfort for everything.</p><p>It’s a good guideline. It developed a rhythm for me.</p><p>Try it out! Maybe it will work for you, too!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1905f7176b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identifying Synchronous and Asynchronous code and Repeating Phase Two [update]]]></title>
            <link>https://medium.com/@joshhayles/repeating-phase-two-it-pissed-me-off-21c399b0f6b?source=rss-38874c713e17------2</link>
            <guid isPermaLink="false">https://medium.com/p/21c399b0f6b</guid>
            <category><![CDATA[flatiron-school]]></category>
            <dc:creator><![CDATA[Josh Hayles]]></dc:creator>
            <pubDate>Thu, 10 Feb 2022 21:10:58 GMT</pubDate>
            <atom:updated>2022-04-19T01:11:06.750Z</atom:updated>
            <content:encoded><![CDATA[<p><em>[An update to my Software Engineering Journey with Flatiron]</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VlANZT-GD3GdaJsuZ6xKXQ.png" /></figure><p>I’ve debated for a while on what to write about this time…so I decided on a little mix:</p><h3>Synchronous and Asynchronous code</h3><h3>Question 1</h3><p>Given the following code list the order of console.logs:</p><pre>console.log(&quot;Hello&quot;)</pre><pre>fetch(&#39;https://randomuser.me/api/&#39;)<br>  .then( res =&gt; res.json() )<br>  .then( data =&gt; {<br>    console.log(&quot;Hi&quot;) <br>  })</pre><pre>console.log(&quot;Sup?&quot;)</pre><p>Which one will log first?</p><p>That’s right! The first console log “Hello” will log first.</p><h3>Question 2</h3><p>When fetchData is executed what will be console logged?</p><pre>function fetchData(){<br>        let data = fetch(&#39;https://randomuser.me/api/&#39;)<br>          .then( res =&gt; res.json() )<br>          .then( res =&gt; res )<br>        console.log(data)   <br>}</pre><pre>fetchData()</pre><p>What will be console logged when the following code is run? Why?</p><pre>function fetchData(){<br>        let data = fetch(&#39;https://randomuser.me/api/&#39;)<br>          .then( res =&gt; res.json() )<br>          .then( json =&gt; console.log(json) )<br>}</pre><pre>fetchData()</pre><p>What will be console logged when the following code is run? Why?</p><pre>function fetchData(){<br>        let data = fetch(&#39;https://randomuser.me/api/&#39;)<br>          .then( res =&gt; res.json() )<br>          .then( console.log )<br>}</pre><pre>fetchData()</pre><p><strong>[Emotional Baggage]</strong> I’m now roughly two months into the Software Engineering Program with Flatiron. To say that it’s an emotional rollercoaster is an understatement. While I’m having a blast learning about programming and <em>loving</em> it, there are also days where it’s flat-out overwhelming with the amount of information we not only have to consume, but retain so we pass our code challenge.</p><p>For me, the program is pushing me to my limits. I’m completely consumed each day with coding, studying, practicing, researching, etc. And sometimes I feel like I’ve been in a dark basement for a year while the world continues to churn without me having a clue as to what’s happening outside of my home.</p><p>The curriculum is information-overload on steroids. It’s almost impossible to consume everything being thrown at me. There simply aren’t enough hours in the day, and I’m not a “natural” at anything, so I have to work crazy hard to keep up.</p><p>And it caught up to me in Phase Two … I did not pass my code challenge after two attempts, so I had to repeat that phase. I was NOT happy about it. In fact, it pissed me off.</p><p>But, it was my only choice. I stayed behind and repeated Phase Two.</p><p><strong>[Encouragement] </strong>However, today we took our first code challenge test and I passed it! That means I can use all of next week to focus on my project before we start Phase Three (Ruby) in 11 days.</p><p>It turns out repeating Phase Two has been a blessing. Being able to review the material again and get more practice has made all the difference in my understanding of React. And that will only make me stronger in the coming Phases of the program.</p><p>Oh, and to answer the question: “Do I still love to code?” …</p><p>Hell yes. 100%, I still LOVE coding. I’m in it for the long haul.</p><p>Here’s to Phase Three!</p><p>Your friend,</p><p>Josh Hayles</p><p><strong>Resources:</strong></p><ol><li><a href="https://www.youtube.com/watch?v=pIjfzjsoVw4&amp;t=3s">https://www.youtube.com/watch?v=pIjfzjsoVw4&amp;t=3s</a></li><li><a href="https://www.freecodecamp.org/news/synchronous-vs-asynchronous-in-javascript/">https://www.freecodecamp.org/news/synchronous-vs-asynchronous-in-javascript/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21c399b0f6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first two weeks in Flatiron Software Engineering Program … a big fat waste of time?]]></title>
            <link>https://medium.com/@joshhayles/my-first-two-weeks-in-flatiron-software-engineering-program-a-big-fat-waste-of-time-f6d834c4d850?source=rss-38874c713e17------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6d834c4d850</guid>
            <category><![CDATA[flatiron-school]]></category>
            <dc:creator><![CDATA[Josh Hayles]]></dc:creator>
            <pubDate>Thu, 23 Dec 2021 22:34:28 GMT</pubDate>
            <atom:updated>2021-12-23T22:34:28.784Z</atom:updated>
            <content:encoded><![CDATA[<h3>My first two weeks in Flatiron Software Engineering Program … a big fat waste of time?</h3><p>The first two weeks, to say the least, have been a mixture of emotions ranging from excitement to despair.</p><p>I just took my phase 1 exam and I completely bombed it. I had no idea I would be so upset about it.</p><p>Emotions rushed through me, flashing back to the 120+ hours I’ve worked and studied in the last two weeks, thoughts of my family picking up the slack and taking care of everything while I’m in school, etc.</p><p>It hurt.</p><p>A lot.</p><p>In fact, writing this article right after it happened was the last thing I wanted to do. But for some reason, here I am.</p><p>Maybe I’ll reflect back one day and see it as a valuable lesson. I hope so. Otherwise, what in the hell was it all for?</p><p>What I’m going to do next is follow the same advice I would give anyone else who didn’t pass a test the first time …</p><blockquote><strong>Shake it off. Get up. Get back to work!</strong></blockquote><p>That’s it.</p><p>It sucks, for sure. It’s a fist in your gut that knocks the breath out of you.</p><p>But I’m not letting it hold me back.</p><p><em>Why?</em></p><p>Because, through the 80 hours of Prework that was required before starting Phase 1, and then the 120+ hours from Phase 1 so far, I’ve come to a conclusion:</p><blockquote><strong>I absolutely LOVE coding. I do. After putting in that much time, failing a test, and then STILL wanting to start again…that’s what it’s all about.</strong></blockquote><p>I will beat this. I will be a Software graduate from Flatiron, guaranteed.</p><p>Keep your head up,</p><p>Josh</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6d834c4d850" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>