Our Journey: Building with Generative AI, Part II
In a recent article, I shared Revelry’s journey into building with generative AI. As a brief recap: since 2013, Revelry has been at the…
In a recent article, I shared Revelry’s journey into building with generative AI. As a brief recap: since 2013, Revelry has been at the…
Businesses of all sizes and industries are eager to take advantage of Generative AI right now, so I’m going to share some details of Revelry’s journey with this emerging technology over the past year.
… and why you might just want to stick with the Chat Completion API Not unlike the rest of the world, Revelry has been…
What is GraphQL? The Graph Query Language is an API specification created by Facebook that provides an efficient, declarative and flexible alternative to REST.
Even though it’s really easy to get in the habit of using inline styles all over the place in your components, there might be better ways of organizing your styles for React Native.
While working on getting a product live in Canada, we have gone through various trials and tribulations getting localization to work. Globalization generally refers to the combination of localization (L10N), and internationalization (I18N).
This purpose of this article is simply to give an up-to-date example of a React Google Maps component using ES6.
It’s hard to not get stressed when there is so much work to do and seemingly not enough time get it all done. In this situation, it really helps to have a strong work-life alliance.
If you aren’t familiar with the term “wfh”, it means “working from home”, which just so happens to be a very popular place to work from nowadays.
I’d like to suggest a simple piece of advice to fellow React devs out there. When rendering dynamic arrays of child elements within a React component…
Don’t Forget Your Keys!
I never thought I would become a programmer. I stumbled into web development while I was studying music in college. Believe me, I was surprised when I ended up becoming a professional web developer.
Any software developer who deals with MVC frameworks has most likely come across the mantra “Fat Model, Skinny Controller”. This is not a good philosophy. It is a bad idea to have a fat model. In fact, it is a bad idea to have a fat anything. Instead, you should strive for Skinny Everything.
Concerns are modules you can use to extract code out of models and controllers. This is useful for various reasons. An obvious one is that this makes things skinnier, which we’ve already established is good. Another is that you can use these concerns to mix into other models and controllers
While it is definitely good to have a slim controller for sake of code reusability, readability, and testing, it is also good to have a skinny model (for the exact same reasons). In fact, its just good to have a skinny everything.