Let’s say you have a form with two groups of related, but mutually exclusive, fields. When you POST and store a new record, no problem, only the right fields are sent in. But what do you do when that record is updated? How can you cleanly handle this?
Laravel validation supports “dot notation” to let you validate arrays in a request. But what if your field name contains a literal dot?
Google Analytics is free and has every imaginable feature you might ever want. So why would I switch to paying for Fathom Analytics?
Today I realized something about myself, I actually really enjoy working in legacy applications. This may seem odd. It’s common to hear complaints about “how bad this old code is”, so why would I enjoy working in a difficult environment? First, it would be useful for me to define what makes an application a legacy application. I realize this may not be a universal definition for everyone, but here are the core elements I think of that make an application qualify as “legacy”:
Randomness can serve a useful purpose in factories, seeders, and tests. There are times it can cause issues though. Here are some rules I think about when introducing randomness into a test.
Is git rebase a command to be avoided at all cost? I say no. Here’s one use case where I reach for rebase instead of merge.
Here’s a handy tip when you want to rename a file with a long path/name and don’t want to retype it twice.
Many of us have a seemingly endless backlog of tasks we could be doing. How can you figure out what’s most important, and use that decision to bring focus to your day?
Many developers feel overwhelmed with the amount of work they want to get done each day. Or they feel pulled in multiple directions and struggle to make progress on the important things. I can totally relate! One thing that helped me is keeping a work journal.
While everyone is loving the features in the new Laravel 8 release this week, I just discovered something cool I missed in Laravel 7.