<?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 Shaun Montoya on Medium]]></title>
        <description><![CDATA[Stories by Shaun Montoya on Medium]]></description>
        <link>https://medium.com/@smontoya0009?source=rss-844e19eb2829------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gNAUSEpcxqt2_44A</url>
            <title>Stories by Shaun Montoya on Medium</title>
            <link>https://medium.com/@smontoya0009?source=rss-844e19eb2829------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:48:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@smontoya0009/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[Learning React: How Components, JSX, and State Changed the Way I Think About Building UIs]]></title>
            <link>https://medium.com/@smontoya0009/learning-react-how-components-jsx-and-state-changed-the-way-i-think-about-building-uis-ac91ad03c581?source=rss-844e19eb2829------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac91ad03c581</guid>
            <category><![CDATA[beginner-programmers]]></category>
            <category><![CDATA[beginner-developers]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <category><![CDATA[beginner-coding]]></category>
            <dc:creator><![CDATA[Shaun Montoya]]></dc:creator>
            <pubDate>Wed, 24 Dec 2025 22:20:13 GMT</pubDate>
            <atom:updated>2025-12-24T22:20:13.456Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started learning JavaScript just a few months ago, I learned to appreciate the fundamentals of building front-end web applications, but most of my time spent working with the DOM felt clunky and repetitive, which made wanting to build a more challenging web application felt tedious and longing for efficiency. Writing several lines of code to create one element, attach it to the page, and update it manually was cumbersome, and often made my projects harder to reason about as they grew in complexity. That tiny micro-moment of frustration will scale exponentially as your application grows in complexity, which is part of what excited me to explore React, a language built on compressing tedious lines of Javascript code into a single declarative JSX element. The shift in how I now approach UI development has been extremely helpful in the way that I think about writing Javascript efficiently.</p><h3>From DOM Manipulation to JSX</h3><p>One of the first things that clicked for me was how React allows HTML-like syntax to live inside JavaScript using JSX. Instead of juggling document.createElement() calls or string-building markup, I can describe the structure of my UI directly in my component code. JSX feels expressive, readable, and natural — as if JavaScript and HTML are actually speaking the same language.</p><p>This blend doesn’t just feel cleaner; it also makes UI logic easier to reason about. When coding in React, I think lessin terms of “how do I manipulate the DOM step-by-step,” but instead “what should the UI <em>look like</em> based on the current state?” That shift alone has made my development process far more efficient.</p><h3>Components as a Natural Extension of Object-Based Thinking</h3><p>In a previous blog post, I wrote about organizing JavaScript code using objects. React takes that abstraction further by encouraging the organization of code into components. Each component encapsulates structure, logic, and behavior: a self-contained building block that represents a meaningful part of the UI.</p><p>Seeing how data flows from parent components down to children and grandchildren has been especially interesting. It’s equally powerful to trace that data back up when callbacks or state updates occur. This top-down flow helped me better visualize how React models application behavior as a set of relationships rather than scattered functions.</p><p>And one thing that I have learned about programming is that the more you can compress relevant code blocks into easy-to-handle packages, the more efficiently you can construct complex relationships between code blocks.</p><h3>Understanding Props, State, and That “Second-Language” Feeling</h3><p>I’ll be honest: mastering props, state, and array destructuring did not happen overnight. Early on, I frequently had to reread examples and walk through code line-by-line just to understand what was happening.</p><p>But after enough practice, React began to read to me like a second language. Concepts that once felt foreign — like updating state, passing props between components, or unpacking values from hooks — started to become intuitive. The more I worked with React, the more natural it felt to think in terms of component data flows rather than procedural instructions that connected only to a specific part of your code somewhere down the line.</p><h3>The Challenges: Too Many Functions, Too Many “Gotchas”</h3><p>Of course, learning React isn’t without its challenges. There are many functions and hooks available to import from the React library, and keeping track of what each one does can definitely be overwhelming. I’ve also run into plenty of technical “gotchas” along the way, such as forgetting cleanup functions, missing dependency arrays, or not fully understanding lifecycle behavior until something breaks.</p><p>Most of this simply requires repetition and exposure. I’ve found that I’m currently better at <em>reading</em> React code than writing it, which is inevitably part of the natural progression of learning any foreign language. To support myself, I take extensive notes, which mostly consists of copies of working examples that I use to identify and reuse patterns as I build projects. That practice has been invaluable.</p><h3>Context Through History — and Seeing React in the Real World</h3><p>Researching the history of React has also helped anchor my learning. Understanding where it came from and why it was created makes the design choices feel more intentional and meaningful. It’s also motivating to see how widely React is adopted today — from Instagram and Spotify to GitHub and countless modern consumer applications.</p><p>Realizing that the same concepts I’m learning power large-scale, real-world systems gives this journey a sense of relevance and momentum.</p><h3>Moving Forward</h3><p>Learning React has certainly changed the way I think about building user interfaces. It replaces tedious DOM manipulation with a declarative, component-driven model that feels both elegant and scalable. While the leap forward from Javascript can feel wide, it has been a very rewarding step in my development journey.</p><p>I’m still growing, still refining my understanding, and still encountering challenges. But with each project, React feels a little less foreign and a little more like home.</p><p>If you’d like, I can also help you tailor the tone further for Medium, add a short intro bio, or format it with headings and spacing styled for publishing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac91ad03c581" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Boxes to APIs: My Phase 1 Journey into JavaScript Objects and Beyond]]></title>
            <link>https://medium.com/@smontoya0009/from-boxes-to-apis-my-phase-1-journey-into-javascript-objects-and-beyond-8db4c3c8e4ca?source=rss-844e19eb2829------2</link>
            <guid isPermaLink="false">https://medium.com/p/8db4c3c8e4ca</guid>
            <category><![CDATA[codingjourney]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[flatiron-school]]></category>
            <category><![CDATA[beginnerdev]]></category>
            <dc:creator><![CDATA[Shaun Montoya]]></dc:creator>
            <pubDate>Fri, 17 Oct 2025 00:04:06 GMT</pubDate>
            <atom:updated>2025-10-17T00:04:06.723Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started learning JavaScript at Flatiron School, I didn’t expect to think of code as… boxes. But that’s what objects started to feel like to me — little boxes that hold both <em>data</em> and <em>rules</em> for how that data behaves.</p><p>I used to think programming was just about making things happen in sequence. But once I learned about objects, everything clicked differently. Objects can <em>contain</em> things — not just values, but functions, too. Those functions are called methods, and they’re like specialized tools stored inside your box.</p><pre>const dog = {<br>  name: &quot;Cairo&quot;,<br>  breed: &quot;Dachshund&quot;,<br>  bark() {<br>    console.log(`${this.name} says woof!`);<br>  }<br>};<br><br>dog.bark(); // Cairo says woof!</pre><p>Here, bark is a method — a function that belongs to the dog object. I love this concept because it feels like defining a set of rules that live inside the object. You can move it around, pass it to other functions, or even expand it later — and those rules go with it.</p><p>Once I understood how to make individual objects, the next step was constructor functions. This is where the power of “object factories” comes in.</p><pre>function Dog(name, breed) {<br>  this.name = name;<br>  this.breed = breed;<br>  this.bark = function() {<br>    console.log(`${this.name} says woof!`);<br>  };<br>}</pre><p>What blew my mind is the keyword <strong>this.</strong></p><p>Like most JavaScript beginners, I couldn’t quite wrap my mind around the concept of <strong>this</strong> in programming. Before I could understand <strong>this</strong>, I had to first understand that constructor functions were essentially a <em>blueprint</em> for the properties and methods that many other objects would inherit, and <strong>this </strong>was simply a placeholder for any specific object that used that blueprint.</p><pre>const zurich = new Dog(&quot;Zurich&quot;, &quot;Dachshund&quot;);<br>zurich.bark(); // Zurich says woof!</pre><p>Every time I call new Dog(), it builds another box just like the last — same structure, different data. Once I started using constructors, I realized how easy it is to keep my code organized, scalable, and reusable.</p><h3>Fetching Data: From APIs to the DOM</h3><p>The next “aha” moment for me came with fetch requests.</p><p>Using fetch() to grab objects from an API felt like connecting my boxes to someone else’s warehouse. Suddenly I wasn’t just creating my own data — I was pulling <em>live</em> data from another source and using it in my own app.</p><p>What’s even cooler is how iterative functions like .forEach() or .map() let you transform that data to fit your needs. I could take one JSON response and turn it into cards on a web page, rows in a table, or even something visual like a chart.</p><p>That’s when I realized something powerful: <em>Data is standardized, but presentation is limitless.</em></p><p>Whether it’s text, numbers, or nested objects, JavaScript lets you reshape it however you want.</p><h3>Final Thoughts</h3><p>Phase 1 of Flatiron taught me more than just syntax — it taught me how to <em>think</em> in terms of systems.</p><ul><li>Objects are my boxes.</li><li>Methods are the tools inside.</li><li>Constructor functions are blueprints for new boxes.</li><li>Fetch requests are the bridges between my boxes and the outside world.</li></ul><p>Every project I build now starts with these principles in mind. Whether I’m rendering API data or constructing custom objects, I’m no longer just writing code — I’m designing how those boxes interact, move, and respond in the world I’m building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8db4c3c8e4ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>