Back-End Engineering
Revelry’s talented engineering team – comprised of front- and back-end developers – offers expertise in a wide range of languages, frameworks, and capabilities. In addition to long-time favorites, like Elixir and Phoenix, they enjoy exploring “what’s new and what’s next,” and then sharing about it.
Check out some of our tech team’s latest insights and opinions below, and then sign up for our monthly e-newsletter for more.
Dynamic Child Components with React
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!
Death by SaaS – Long Live SaaS
Every Tuesday night in New Orleans the developer community gets together for Hack Night. We rave and argue about old and new technologies and…
Music & Coding
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.
Hi, I’m a Recruiter and I’m Coming for Your Employees
That’s basically what someone told me on the phone last week. Jon answered the phone and the caller, a recruiter, asked to be connected…
3 Bits of CSS That I’m Going to Start Using Everyday
Viewport Sized Typography, CSS Columns, and Using CSS Shapes as Text Wrap
Skinny Everything (Part 3 of 3)
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.
Faster Software Development with (Smart) Technical Debt
“technical debt” noun. the sum of costs owed to one’s computational progeny for past transgressions against their design and future well-being If you’re like…
Skinny Everything (Part 2 of 3)
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
Skinny Everything (Part 1 of 3)
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.