<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>React on Gilhooley Developer Blog</title><link>https://pgil256.github.io/blog/tags/react/</link><description>Recent content in React on Gilhooley Developer Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© Athul</copyright><lastBuildDate>Mon, 04 Sep 2023 12:13:30 +0530</lastBuildDate><atom:link href="https://pgil256.github.io/blog/tags/react/index.xml" rel="self" type="application/rss+xml"/><item><title>How To Mess Up a React App</title><link>https://pgil256.github.io/blog/posts/post-2/</link><pubDate>Mon, 04 Sep 2023 12:13:30 +0530</pubDate><guid>https://pgil256.github.io/blog/posts/post-2/</guid><description>How not to develop a React Node.js application:
Rush through your data structurization. As long as they contain the necessary columns and are relationally sound, you&amp;rsquo;ll be fine, right? No need to plan further. Never proof your API routes. If you mess up a variable name or return the wrong value in a route, surely you will catch that later. Those deprecation warnings you keep seeing in NPM install? Probably nothing.</description></item></channel></rss>