<?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 Chaitanya Nijhara on Medium]]></title>
        <description><![CDATA[Stories by Chaitanya Nijhara on Medium]]></description>
        <link>https://medium.com/@cnijhara?source=rss-8810e844ee32------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BTmtFhbIFey6szAYIvK-vA.png</url>
            <title>Stories by Chaitanya Nijhara on Medium</title>
            <link>https://medium.com/@cnijhara?source=rss-8810e844ee32------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:28:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cnijhara/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[Recap: Day 1-100 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/recap-day-1-100-100-days-full-stack-challenge-13b713dc17ae?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/13b713dc17ae</guid>
            <category><![CDATA[node]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 23:56:51 GMT</pubDate>
            <atom:updated>2018-08-29T01:34:47.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7XKY6h88FVzo-AP_" /><figcaption>Day 100 | Challenge Complete</figcaption></figure><h3>Overview</h3><p>And…it’s a wrap! I spent the last few weeks just practicing all that I’ve learned through this challenge on a personal project. When I first started this challenge, here is what my goal was:</p><blockquote>“After completing this challenge, I should be able to build a full-stack functional application from start to finish without the need to search for any basic syntax or ask for help. If successful, all I’d need to worry about is execution and not ‘how to execute’.”</blockquote><p>To be specific, I thought if I was able to put together a boilerplate fullstack application myself from scratch by the end of this challenge that’ll be a win. However, I’m happy to say that I have far exceeded that goal. :)</p><p>I can now build almost anything that my mind desires. It might take me time, and I might have to make use of libraries for some aspects, but the point is I now understand how to go about it and that’s awesome!</p><p>That said, I wouldn’t call myself a fullstack programmer in the traditional sense, but I know enough to hack something together relatively quickly and get the boll rolling, which is exactly what I set out to do in the first place.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_p42hVWMG0C8H5uLNIPvw.png" /></figure><h3>Gaps</h3><p>Below are a couple of the areas that I’m still not very confident in:</p><ol><li>Redux form</li><li>Sendgrid email integration</li></ol><p>Follow me here on medium, I’ll post intermittently. Also, if you have any questions, please feel free to reachout.</p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13b713dc17ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recap Day 65–81 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/recap-day-65-81-100-days-full-stack-challenge-7af8df41abc5?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/7af8df41abc5</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 18:18:30 GMT</pubDate>
            <atom:updated>2018-07-26T18:18:30.760Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PHxvIdQCTXIra7fc" /><figcaption>Day 82 — Complete Guide to MongoDB | Recap: Day 65–81</figcaption></figure><h3>Overview</h3><p>Hi there! I finished this course about a week or so before, spent the last few days practicing what I’ve learned so far on a personal project. Overall, I feel a lot more comfortable with React and Redux vs. working with the database. That’s where I struggle the most and have to google stuff every now and then.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GIp_jZTJBl2qfoUrH1uGNQ.png" /></figure><h3>Gaps</h3><ol><li><strong>Higher Order Components</strong>: In particular, I am a bit lost with the order of operations when you have multiple higher order components on a single component. Due to the async nature of JS, it seems a little hard to predict what line would be executed when.</li><li><strong>MongoDB complex query syntax</strong>: I struggled a lot with MongoDB sytax. Simple, GET POST PUT and DELETE commands are OK. It’s when you’d like to create a complex query or a post command is where I start to struggle.</li></ol><p>Over the next few days, I’ll continue with my project. I still might have a couple of courses that I’d like to go through before 100 days are up, but will take a decision when I’m at a comfortable position with my project.</p><p>See you guys soon!</p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7af8df41abc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 69 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-69-100-days-full-stack-challenge-d60ba1ef2411?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/d60ba1ef2411</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[mongodb]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Sun, 15 Jul 2018 18:21:03 GMT</pubDate>
            <atom:updated>2018-07-15T18:21:03.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5TD-jWza3gcQID_D" /><figcaption>Day 69 — Complete Guide to MongoDB | Creating a RESTful API</figcaption></figure><h3>Overview</h3><p>I started reading the documentation for mongoose and mongoDB and realized that I don’t really know much about theses topics. So instead, I finished a short video series on Youtube called as <strong>Creating RESTful API</strong> by <strong>Maximilian Schwarzmüller. </strong>In the series, Max walks us through the entire process of setting up routes, models and controllers from scratch. Although, I wouldn’t say I learned anything new, it was still a good refresher.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e80Z9caziOtpVkrpq7_YLQ.png" /></figure><h3>Key Takeaways</h3><ol><li>Mongo Atlas</li><li>Encrypting passwords and implementing JWT tokens without passport</li></ol><p>Let’s wrap this up tomorrow for <strong>Day 70 — Complete Guide to MongoDB | Recap</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d60ba1ef2411" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 68 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-68-100-days-full-stack-challenge-2914211fe41?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/2914211fe41</guid>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Sat, 14 Jul 2018 08:59:31 GMT</pubDate>
            <atom:updated>2018-07-14T08:59:31.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tia3ij6HoHSz_ilW" /><figcaption>Day 68 — Complete Guide to MongoDB | MongoDB with Node and Express</figcaption></figure><h3>Overview</h3><p>Today, I completed the final section in the course — MongoDB with Node and Express. This section in particular was just brilliant in clarifying so many doubts and holes I had in my understanding of the backend setup. The name of course makes it sound like a super advanced course compared to other courses by Stephen Grider. To the contrary, I found this course to be simpler and slower where Stephen took all the time in the world to explain all the important topics in this field, which is great! Exactly what I needed at the moment.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HJwU4sHgxrbLGXWi5n0p9A.png" /></figure><h3>Key Takeaways</h3><ol><li><strong>Router-countroller-model</strong> architecture</li><li>Making <strong>$geoNear</strong> queries and handling <strong>geoJSON</strong> data with mongoDB.</li><li>More practice with async / await syntax</li></ol><p>I think, this course was great in giving me a primer for learning more about mongoose and mongoDB myself. So tomorrow, I’ll some time going over the docs of mongoose and mongoDB.</p><p>See you tomorrow for <strong>Day 69 — Complete Guide to MongoDB | Reading Docs</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2914211fe41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 67 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-67-100-days-full-stack-challenge-9419eb73155e?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/9419eb73155e</guid>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Fri, 13 Jul 2018 01:41:04 GMT</pubDate>
            <atom:updated>2018-07-13T01:41:04.425Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YWVMuxvnMOwHX9hb" /><figcaption>Day 67 — Complete Guide to MongoDB | Practice Session #18</figcaption></figure><h3>Overview</h3><p>Completed all the lessons from the sections I worked on yesterday, building out the database side of things for this fictional application. Overall, I feel pretty good with what I’ve learned about mongoose/mongoDB.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0o1IwCR3xbK2FG_S9nGSAQ.png" /></figure><h3>Output</h3><p>Created database collection Models and added queries to fetch and update data as needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3rWjMWxBz_c1ls5lz5-Yw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uUSa3SwMZE0mXtfwGBRTcA.png" /></figure><p>Continuing to the final section in the course: <strong>Day 68 — Complete Guide to MongoDB | MongoDB with Node and Express</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9419eb73155e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 66 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-66-100-days-full-stack-challenge-ece890e58c80?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/ece890e58c80</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Wed, 11 Jul 2018 22:04:21 GMT</pubDate>
            <atom:updated>2018-07-11T22:04:21.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1CiZE5UUURAGvgrx" /><figcaption>Day 66 — Complete Guide to MongoDB | Middlewares and Music project</figcaption></figure><h3>Overview</h3><p>Covered a bunch of mongoDB topics today. Overall, I’m starting to appreciate the complexity and the vastness of the topic. One place that I struggled a bit during today’s sections was handling promises. Mainly because the instructor was following ES5 .then syntax and I wanted implement ES6 async await syntax. In most places it worked alright, expect the music project where the boiler plate application that the instructor had built for us expected to receive unresolved promises, so I couldn’t use async await.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*87feWQKg6__PtxsGFaFJxw.png" /></figure><h3>Key Takeaways</h3><ol><li><strong>Mongoose middlewares:</strong> Middlewares can be defined for a Schema that get executed BEFORE or AFTER a specified event, such as ‘save’ or ‘remove’</li><li><strong>Skip</strong>: Mongoose operator that skips a predefined number of items before returning any items from the database for a given query.</li><li><strong>Limit</strong>: Mongoose operator that limits a predefined number of items returned from the database for a given query.</li><li><strong>Indexes</strong>: MongoDB by default indexes _id of any document saved in any collection. That’s why lookup by _id is very fast vs. any other property because _ids are already indexed. Likewise, we can setup our own indexes for a collection to speed up the lookup on a given property. For example — performin text search on names, etc.</li></ol><p>I still need to solidify the learnings, so I’ll spend tomorrow practicing all the lessons from today.</p><p>See you tomorrow for <strong>Day 67 — Complete Guide to MongoDB | Practice Session #18.</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ece890e58c80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 65 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-65-100-days-full-stack-challenge-29e8384b2f95?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/29e8384b2f95</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[mongodb]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Wed, 11 Jul 2018 04:23:36 GMT</pubDate>
            <atom:updated>2018-07-11T04:23:36.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TGKEdK94QuwTlPR5" /><figcaption>Day 65 — Complete Guide to MongoDB | Tests for Mongo</figcaption></figure><h3>Overview</h3><p>Alright! I’m really exited to be working on the database side of things. I fell it’s quite important to understand optimal ways of designing, saving and querying databases. Luckily, <strong>Stephen Grider</strong> has a course —<strong> Complete Guide to MongoDB</strong> — on this topic (in case you haven’t noticed, I <em>really</em> like learning from him!).</p><p>Today, I completed mongoDB / mongoose setup and a couple of sections on running tests using mocha library.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J87M3ku8-8up7_vg2Z6i-w.png" /></figure><h3>Key Takeaways</h3><ol><li><strong>mocha</strong>: A simple-to-use library that helps us design tests.</li><li><strong>CRUD — Create Read Update and Destroy </strong>: These represent the four types of methods we can run on our database</li><li><strong>Query methods</strong>: find, findOne, findById</li><li><strong>Deleting methods:</strong><br>-Model Instance: remove<br>-Model Class: remove, findOneAndRemove, findByIdAndRemove</li><li><strong>Updating methods:</strong><br>-Model Instance: update, set and save<br>-Model Class: update, findOneAndUpdate, findByIdUpdate</li><li><strong>Mongoose Validators</strong>: validate &amp; validateSync. We can assign validators right inside our Schema object and mongoose will make sure they pass before saving data to the database. Neat!</li><li><strong>Virtual Types</strong>: These are functions that sit on top of our Schema and can be called as a property of that Schema. For example: Fetching the total number of blog posts with a user document. Note — While defining virtual types we should not use fat arrow =&gt; functions since ‘this’ called within the function does not have the right context. Instead, use traditional functions with the ‘function’ keyword.</li></ol><p>See you tomorrow for <strong>Day 66 — Complete Guide to MongoDB | Middleware and Music Project</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29e8384b2f95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 64 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-64-100-days-full-stack-challenge-915eb28d6053?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/915eb28d6053</guid>
            <category><![CDATA[react-router]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 08:33:48 GMT</pubDate>
            <atom:updated>2018-07-10T08:38:50.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FW583i96Eocyqfo2" /><figcaption>Day 64 — Status Update</figcaption></figure><h3>Overview</h3><p>Hello again! It feels good to be back writing some posts on medium. I’m finally back from my hiatus. I took a couple of days off for the July 4th weekend and then wanted to spend time working on a personal project before moving on.</p><p>Over the last few days, I’ve learned quite a lot about React Route v4, and managing and persisting Redux State. Additionally, I realized that I’m quite weak in working with mongoDB and the database side of things. So, that’s what I’m planning to work on next.</p><h4>Revised Syllabus 6:</h4><ol><li>Day 1–9: Codecademy React | <em>Done!</em></li><li>Day 10–28: Udemy Modern React and Redux | <em>Done!</em></li><li>Day 29–37: Udemy Advanced React and Redux | <em>Done!</em></li><li>Day 38–39: Udemy ES6 Javascript | <em>Done!</em></li><li>Day 41–50: Udemy Node with React | <em>Done!</em></li><li>Day 52–57 : Materialize CSS From Scratch |<em> Done!</em></li><li><strong>Day 65–75: Complete Guide to MongoDB</strong></li><li>Open</li></ol><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MeesuClRRb0dZY0OYeNUPQ.png" /></figure><p>See you tomorrow for <strong>Day 65 — Complete Guide to MongoDB | Tests for Mongo</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915eb28d6053" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recap: Day 52–57 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/recap-day-52-57-100-days-full-stack-challenge-d4a68b2cce65?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4a68b2cce65</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Wed, 04 Jul 2018 07:39:17 GMT</pubDate>
            <atom:updated>2018-07-04T07:45:53.060Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bm2ARLzkfFViLqLH" /><figcaption>Day 58 — Materialize CSS | Recap: Day 52–57</figcaption></figure><h3>Overview</h3><p>Finished another course in this journey. Although, I’m glad and appreciate all the learnings I got from <strong>Materialize CSS </strong>by<strong> Brad Traversy</strong>, I would’ve liked if the instructor had gone into the concepts and underlying philosophy behind Materialize CSS and CSS in general. I felt that only learning what is included in the framework can also be gathered by simply visiting the materialize css website, they’ve documented things well (for the most part).</p><h4>Revised Syllabus 5:</h4><ol><li>Day 1–9: Codecademy React | <em>Done!</em></li><li>Day 10–28: Udemy Modern React and Redux | <em>Done!</em></li><li>Day 29–37: Udemy Advanced React and Redux | <em>Done!</em></li><li>Day 38–39: Udemy ES6 Javascript | <em>Done!</em></li><li>Day 41–50: Udemy Node with React | <em>Done!</em></li><li>Day 52–57 : Materialize CSS From Scratch |<em> Done!</em></li><li>Open</li></ol><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsYKrJnrry2icG3m3DXVTw.png" /></figure><h3>Key Takeaways</h3><ol><li><strong>How to Materialize CSS with React</strong></li><li><strong>window.scrollY</strong>: To add scrolling event listener at a particular point on the page</li></ol><h3>Gaps</h3><ol><li>CSS basics such as position, display etc.</li><li>pre-loader</li><li>google maps</li></ol><p>Next, I’m taking a break for a couple of days. I’ll see you guys when I’m back!</p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4a68b2cce65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 57 | 100 Days Full-Stack Challenge]]></title>
            <link>https://medium.com/@cnijhara/day-57-100-days-full-stack-challenge-1ed8a94746bf?source=rss-8810e844ee32------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ed8a94746bf</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Chaitanya Nijhara]]></dc:creator>
            <pubDate>Tue, 03 Jul 2018 01:18:52 GMT</pubDate>
            <atom:updated>2018-07-03T01:19:32.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jIavB5GE_NPuEJZD" /><figcaption>Day 57 — Materialize CSS | Project 4</figcaption></figure><h3>Overview</h3><p>Completed the 4th project in the course. We built another corny-businessy marketing website. The main thing that I learned about was window.scrollY method that helps me control css property of elements as the user scrolls through the page. For example — making the nav bar solid form transparent beyond a certain point on the screen.</p><h3>Progress Bar</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJ9MuWyV4UyrYNt0Jegstg.png" /></figure><h3>Output</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*He2Nk0-8v1wbMo9VPPAQCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrXqN_fiaNkeaub7fixGPA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pNyBg-nbVLdOqrmp25eUlg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-vJKWtU7sqsEbQD7oYGq5w.png" /></figure><h3>Gaps</h3><ol><li>Couldn’t figure out Google Maps implementation in react. That’s why you see white space around the contact form. I’m not too concerned about this since we did implement google maps in one of the earlier courses I took — Modern React with Redux. I’ll look that up when I need it in my personal projects.</li></ol><p>I’m skipping the final project in the course since the output seems repetitive but the implementation is using SCSS which seems to be an overkill at this point. I’m satisfied with what I’ve learned so far.</p><p>See you tomorrow for a wrap-up of this project <strong>Day 58 — Materialize CSS | Recap: Day 52–57.</strong></p><p><em>If you stumbled upon this page, read how I ended up starting this challenge and what it is all about → </em><a href="https://medium.com/@cnijhara/100-days-full-stack-challenge-5410dad92a0e"><em>here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ed8a94746bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>