Tech Weekly

Recently, I ran into a problem that looked simple at first, but quickly turned into a performance bottleneck. I needed to fetch a directory of cities and branches from a third-party delivery service for an ecommerce checkout page. Since the store supports multiple languages, the same dataset had to be.

After working on more than 25 projects with Laravel, I’ve made enough mistakes to stop calling them “preferences.” Some patterns are no longer optional for me; they are rules. These are not theoretical best practices. They come from real situations where things broke, scaled poorly, or became painful to maintain..