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.
Do you ever get frustrated when you call an API and it sends back an inappropriate HTTP status code? I never want my APIs to be a source of frustation, so I’ll share a recent debate I had with myself as to which status code was the best.
Why would you ever mark a test as todo? Isn’t that devaluing your tests? Not at all! I’ll share some ways I use todo tests effectively.
A couple days ago, I walked through a few potential gotchas with relationships in Laravel factories. Let’s see how it works in Laravel 8.
The forthcoming release of macOS 11 (Big Sur) provides one more compelling reason to move to Fathom Analytics.
What’s the best way to define a relationship in your Laravel factories? I’ll share some tips that will help you avoid some common pitfalls, as well as give you a deeper insight into how factories work.
Ask most developers a question and you’ll often hear the phrase “it depends”. While it can be annoying, there’s a truth to it. Let’s consider an example of how knowing who your typical user is can affect even basic decisions like how to validate a request.
Let’s wrap up this series of tips, and show one final example when setting an explicit primary key value can improve the quality of your tests.
Yesterday I shared an example where setting explicit primary key values in your tests can make your tests more reliable. Let’s take a look at another example.