As we have more pages and new user-interface elements, it was a great time to think about improving our frontend, targeting the reusability of components and code organization. This post explains how we did that with Phoenix Components and the Atomic Design methodology.
Organizing code takes a lot of work. It is easy to make a mess as we build and grow our applications. This post aims to dive into the concept of contexts in Elixir by using real-world examples and understanding how it can help us keep our codebases manageable.
The original concept for RFP was to build software products from scratch in a limited time frame. The only requirement was those products should be ready to go live at the end of that period.
A few days ago, we've redesigned the Ready for Production brand & website, and we thought it would be nice to tell you a little more about it.
We watch games from different places every week and chat about the teams we like, but it takes time to keep track of everything. The good news is many web apps provide live coverage of almost every soccer match on the planet. The bad news is great live experiences are rare because they are complex to build.
Have you ever needed to build solutions related to execution flows like wizards, admission processes, or game rules in your software? If you do, you know it can be a nightmare of conditionals and complexity. We can make our lives easier by developing them using state machines.