I've seen too many engineers get stressed about a timelines, then they come off looking bad. In my experience, looking bad has nothing to do with missing that timeline and instead has everything to do with bad communications and acting shifty/dishonest about the project status. At the end of the day, we're all granted a lot of trust and we gotta pay that trust back by explaining what's going on.

NextJS doesn't support websockets or proxying them. It's middleware act's like its running on the edge instead of nodejs. Andddd their cookie library isn't configurable. Here are my techniques for getting around all these problems and get this whole thing to work - begrudingly.

Exploring practical applications of Large Language Models (LLMs) in this blog post. Learn how LLMs can enhance products, from suggesting emojis for game reviews to simplifying categorization and generating website content. Discover the benefits and considerations of using LLMs for product improvement.

Last year, I got that itch to make a game again, and this time I was determined to ship! Like clockwork, once a year I re-download both Unity and Unreal Engine. These tools are solid but by the time I onboard I lose focus. This time, I knew what I was going to make, and I wasn't going to let the technology choices distract me. I chose React Native as my game engine.

I've seen a ton of post's lately on Twitter, hackernews, etc. All effectively saying "yolo more". Yea that's cool and all, but honestly I actually find true yolo to be much slower and low leverage than just having a decent test harness. Before I start - I'm not advocating for TDD nor am I advocating for really trivial/low value unit tests.