Life's a mess. So is this blog! 😅

“You mean the docs must be changed?! Why? For your ego??” was the response I received on the Larachat Slack forums (of the famous Laravel PHP framework) one day. The gentleman was a veteran on the forums, and the argument I had wasn’t even a bad one. The exact details escape me, but my point was that I couldn’t figure out how to pass route params in the case of reverse routing.

I wrote a very small demo involving useEffect() today. Actually, before that, I happened to be reading about useEffect() in some article and caught myself confused. I had been always confident that I knew the finer details, but I just couldn’t tell one thing — will the effect run on the first render if the dependencies are listed exhaustively? If you’re laughing at me, let me join as well — 🤣🤣🤣🤣

Refs is one of those topics that sends even seasoned React devs into fits of panic. What is this mysterious thing called a “ref” that we never encounter and yet is encountered everywhere (in blog posts and interviews, at least!)? Am I less of a React dev if I don’t know how to use refs? Where the heck would I need this ref thing? Calm down, my friend. The topic of refs might be on the fringes and it might be a bit weird, but it’s by no means mysterious or useless.

People hate StackOverflow (SO) for various reasons. There’s the general hate that SO is a quick-and-dirty help forum that promotes copy-paste-driven development. Then there are architects and “10x” developers who say that the entire SO is a joke, and so are the solutions found there. Finally, many people consider it a valuable entity and want to participate but are repulsed by the heavily acidic moderators and downvoters. What do I think?

How to structure your web app’s code base is a difficult problem, even more so when there are full stack frameworks involved. Take Django, for instance. “Apps” is one of its cornerstones, and the docs say they allow you to create reusable, pluggable modules. GREAT! A project structure that is mature, well-designed, and well understood . . . what more does a developer want, right?! Unfortunately, it doesn’t really work out that well in practice.