They're different videos, released seven years apart.

@Morgy If you have a hard rule that you never effectively pass Request::all() to an Eloquent query, you should be fine.

This is a preference thing, but I run Model::unguard() for all of my projects. It's one of the first things I do.

@CLab The Prompts package is unrelated to anything AI-specific.

We're not using the official Laravel AI SDK because the entire point of the series is to understand how these things work at their core. For real-projects, I would use the SDK.

@amauro I'll upload it today.

@sadhakbj That's the plan!

@ghiath.dev Definitely fun to code everything by hand again.

I miss this kind of sereies

Cool!

@sebkay No kidding haha. Normally, I'd work on something else...but when recording, you just have to wait it out.

Jeffrey, you're going to get yourself killed by some angry laid-off developer with all the AI courses you keep making

Hmm - that doesn't sound right. This would/should only happen if you come back to a thread after leaving the page up for a decent amount of time.

@orgabor Test

@chang180 Yes, I think we can definitely add Chinese translations!

Hey Jeffrey, loving the content so far! Would love to see how you start and plan a new project from scratch with these tools

@nullnan Yep! That shouldn't be a problem anymore.

Really good video, shows how much experience and sharp eyes you have.

Loved the series! These are the valuable conversations we should be having around AI right now. Can't wait for more episodes. Maybe a look at more models (except Grok, of course) and how they can all play along with Laravel Boost.

It's included as one of the branches in section 2 of the Path.

Nice to see you all again. Amazing video as always. Been a few years for me now. Busy busy busy but need to learn this AI stuff

@Grizlex Haha, yeah that was funny.

Fully agree. Great videos Jeffrey! As a senior dev I haven't watched much Laracasts lately (I used to watch EVERY video 10+ years ago) but these AI workflow videos are right on point.

@Brammah That is a hat that gets warn almost every day. 🙃

@flavioludi Test it out for yourself. Build a small app or feature by hand, and then try again using an agent as the driver.

@skylark The summary was AI generated based on the transcript, and were not reliable.

Could also remove the trim() as the middleware TrimStrings should already apply this on the request.

This is fixed now!

I put a baseline for my team to follow, either with AI or not, else your codes won't be accepted.

Using AI is an add-on tools to speed up our works.

But again, we still need to verify and validate the output generated by AI.

@imakeinternet YES. That's a very good point. AI will think, "Well...this is how it's done."

ok, Boomer!

@ian_h Thank you! Pushing a fix up now.

Yeah that is pretty cool! Reminds me a lot of one of my favourite and to a large extent entry to the professional coding world - RPA. Am actually running a RPA pipeline while watching this - great demonstration thank you!

morning, overslept or something? :))

I have made a primitive nightshift worker to myself like a week ago. My task was to update and refactor everything to new Livewire 4 setup. It's not arbitrary, so that I did not want to spend my time on this "luxury" task. Created a new branch, so if thing's got messy, I would go back easily. I waited like 20 minutes and it was going perfect. Then left it and go to bed.

My rules were similar, but I also added call laravel-simplifier and check after every commit. This was misunderstood, it kept calling laravel-simplifier:laravel-simplifier after every edit, was like 10 thousand times. After a sanity check, I figured out that too much refactoring and had to re-write almost half of my tests, so I went back to the origin branch and add testing to the scope of the nightshift. (I didnot call it nightshift, mine was "unmanned")

Second night, I requested Claude to make a master plan first, and follow the plan. Included testing. This way, it had a better routemap and did not call laravel-simplifier once in every minute. again, almost was ok. but figured out that it created irrelevant directories and forgot to remove old directories. some new files were referencing old classes, again it was a mess.

Third try, (I created a totally new livewire project, and referenced it's directory and approach. The scan notes were inserted into my main project. This second .md helped a lot. While maintaining the consistency, it also figured out some more improvements by itself, that I hadnot noticed even.

If to summary, for the first time in this human being's history, I managed to think something earlier than you. I'm proud.

Cheers,

Thanks, everybody. The issue is that the exams feature requires an active subscription - but one of the pages didn't have the proper authorization. That's why you received a 403 when submitting.

Sorry for the confusion! All patched up now.