Thanks for this series. Made it really easy to digest.

Great explanation!

content => 'poly relationships are cool'
That could be taken in a couple different ways

My sides 🤣

I recently came across the morphMap static method when working on a project, and I found that using an enum for the *_type column in the database works wonders when you wish to enforce strict database constraints, making it impossible to insert an invalid string.

Also, you have a great sense of humor. I laughed at 11:18 ^^

Thanks all! I really appreciate the feedback!

For really difficult bugs, I usually run an adversarial prompt where I have multiple agents, each using a different model, trying to figure out what's causing the bug. I have the models review each other's findings to determine what makes the most sense. Just like you, I tell them not to rush to implement a fix. Instead, I ask them to describe the bug using technical language that an experienced developer would understand. I then take the description that the various agents agree upon and feed it into a new prompt where I work on the fix.

@romeoboris It's not even close once you find a workflow that clicks for you.

Embrace the future, guys. No one is going to pay you for organic, pasture-raised code if the alternative costs a fraction of what it used to and delivers the same value to the customer. I love programming—it's more than an occupation for me—but we have to get real about it. There will still be a place for those who love to tinker with technology, but writing code will never be the same now that we've opened the Pandora's box of AI tooling.

Thank you for this course, Jeremy. Even though I've been working with Laravel professionally for over three years, I learned a few things that I'll definitely be using in my next project.