And that's a wrap. You've made it through defensive Laravel, and I hope you're walking away from the scores with a whole new mindset when you come to writing safer, more maintainable Laravel code. We covered a number of tools, techniques, and patterns throughout this course, but the common message through all of the lessons and the goal of the scores is to write code that guides you, your future self, and your teammates towards the right path.

and the goal of the scores is write code that guides you, your future self and your teammates towards the right path code that fails very loudly when something goes wrong. Code that's self-documenting and code that makes legal state impossible. Of course, not every application needs to be perfectly typed or perfectly modeled or to use all of the techniques we've covered on the scores, but the important thing is having the knowledge and knowing those tools

but the important thing is having the knowledge and knowing those tools and techniques to be able to dial up the safety of your code base when needed. That's what really matters. So whether you're working on a large team, on a legacy code base or just on your own projects, you not have the knowledge and you are able to determine what your application needs. Does it need to be very heavily typed?

and you are able to determine what your application needs. Does it need to be very heavily typed? Does it need to be super defensive? That's up to you, but now you have the knowledge and you can make the decision consciously. Thank you for sticking through the course. I really do appreciate your time and attention. I want to add something, although this course does not have that many episodes, the modular level, for example, it is a very, very dense course, so if you feel

that many episodes, the modular level, for example, it is a very, very dense course, so if you feel that you haven't fully captured a concept, I do suggest you go back to the lesson and re-watch it on your own time. Have your code editor open next to it, play with it a little bit until you fully capture the concept. If even after that you still don't fully understand something, do feel free to reach out. I would love to hear from you. In fact, if you just wanted

something, do feel free to reach out. I would love to hear from you. In fact, if you just wanted to share some feedback or just share what you're building, I would love to hear from you anytime. Again, thank you so much for your time and attention, and I really do hope that you walked away from this course with a whole new mindset and more confidence when it comes to shipping stable safe code. Until next time, bye.

to shipping stable safe code. Until next time, bye.