The value of a quick code demo

Sometimes it's more effective to show than tell

Joel Clermont
Joel Clermont

Recently, I was emailing a client to let them know a new feature in their Laravel app was ready for them to test in the staging environment.

It was a fairly complex workflow with 4 different scenarios, so instead of writing up a long email, I recorded a short screencast for them instead.

I thought it would be more likely for them to understand it with the visual walkthrough, and not just a wall of text instructions. As a bonus, in the process of recording it, I found 2 small issues myself and was able to fix them before sending the email.

This same approach works well within a team. Instead of just typing up a bug report or submitting a PR with a text description, recording a quick demo can provide a lot of valuable context.

Here to help,


P.S. Want to work with Laravel developers that know how to communicate?

Toss a coin in the jar if you found this helpful.
Want a tip like this in your inbox every weekday? Sign up below 👇🏼

Level up your Laravel skills!

Each 2-minute email has real-world advice you can use.