At long last, my masterclass on Laravel Testing is live (and on sale!)
Here's a question I've been grappling with: Does testing still matter in an age where most developers are spending less and less time writing code in their editor, and more time directing agents and (maybe) reviewing their code?
For many years, I have been a big believer in testing as a way of writing more maintainable software, with fewer bugs, and better architectural design. It has helped me personally "sleep better at night" knowing that a whole bunch of potential bugs would be caught automatically by my test suite.
This wasn't theoretical either. I experienced these benefits personally, and I saw others experience them as well when I taught them testing and watched them adopt my same patterns.
I believed in this value so much that I spent a lot of time over the last 18 months developing a complete course on all the essentials of what I think is important for testing Laravel applications.
Yesterday, I launched this course, and you are the first group of people to hear about it.
Whether you buy it or not, I would really appreciate it if you can send me a quick reply and answer this question: Do you think learning how to test is still important? Or is writing tests a job you're happy to delegate to a coding agent?
Be honest, even if the answer is "No" I really want to hear it, along with your reasoning.
And if you do think testing is still a relevant skill, I think this new course is the best resource for learning it. Obviously, I'm a bit biased, but I genuinely think the approaches I share here are the most practical ways of quickly building confidence in your Laravel apps without a lot of ceremony or frustration.
Here to help,
Joel
P.S. One last reminder to hit reply and let me know what you think: good, bad, indifferent, too expensive, too long, whatever. Lay it on me!
You received this email because you signed up at masteringlaravel.io. Thanks!
Or click here to update your email address.
