Writing custom React components for reusability is very rewarding, but can also be a pain in the ass when I KNOW something has to happen, but not WHAT, and not WHEN, and certainly not WITH WHOM.
Frustrated developer seeks knowledgeable input on a really stupid problem that's probably not that difficult, but is still a problem. #docker #reactjs #nodejs #traefik #dns
I’ve had a time, I’ll tell you wut. My original category system got broken out into a classification and category system, with a classification being a top level and the category being a subset, which meant I had to go back and…
This post is really more for my own edification than anything else. I’ve been spending many hours these past few days trying to get this community site database and API working, with limited front-end support as a “proof of concept” that I…
Strap in, folks, this is going to be a wild ride. Not really. It’s more development talk, so it’s about as wild as a walk in the park, which this project is turning out not to be. I have mentioned that a…
This is a follow-up to the previous post regarding my attempts to centralize a React app connection to a Colyseus game server. Earlier I had come up with what I had thought was a great way to manage a connection between a…
Sometimes the easiest stuff takes me 10 times longer to implement than it would for pretty much any other developer out there. Exhibit A: authentication with Google’s Firebase. I have probably written about this before, but regardless I’ll provide a crash course…
Continuing my series on blogging about every line of code I write, today’s topic is one that is pretty critical to creating a working auth system that I don’t have to code. If I were rolling my own auth, I wouldn’t have…