The latest articles on DEV Community by aibarra11 (@aibarra11). https://dev.to/aibarra11 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F285027%2Ff4c1d5a9-76b4-42fd-92cf-5b817dee9240.png https://dev.to/aibarra11 en aibarra11 Thu, 08 Oct 2020 16:00:22 +0000 https://dev.to/aibarra11/try-catch-everything-2ea4 https://dev.to/aibarra11/try-catch-everything-2ea4 <p>Just to give a background, I was mainly self taught CSS/HTML/JavaScript and basic PHP. Found Laravel &amp;Laracasts.com and have create a few applications in production. Starting to work on more complex applications while applying more strategies/architectures (CQRS, DDD, event driven...) I know I'm lacking some basics, and one of them is the use of try catch. Do I use them everywhere? I'm creating APIs, and for now I know who will be programming against them. But who knows in the future if the API outlives my involvement. Anyways, do I try catch everything? Are there some basic principles/guidelines I should follow when using them? I know laravel provides its own generic ones, I'd like to improve on that with more specificity. <br> thanks!</p> discuss