All articles

A day with Laravel - #030

HappyToDevHappyToDev
··5 min read


Hey LaraDevs 👋,

I am proud to present a new "A Day with Laravel" issue.

If you think of a resource that could be useful for the Laravel dev community, let me know in a comment or DM on Twitter (HappyToDev)

The objective of this newsletter?

🎯 To deliver to you daily, or almost daily*, the recent or important resources (videos, articles, GitHub repos, packages, tutorials, ...) that I could find on Laravel and its ecosystem.

This is a quick content of a few links to feed your watch on Laravel and its ecosystem daily.

* Or almost: why?

Simply because I'm the only one to manage this newsletter and "Quoi de neuf les devs? 🇫🇷" Depending on my availability and obligations, it is possible that this newsletter is not daily.

I need your support 🙏

My mission with this newsletter at 🇬🇧 and 🇫🇷 is to help you by bringing you as much value as possible, and I really like that.

If you want to support me to encourage me to keep up, please consider helping me by making a one-off or recurring donation starting at €2 by clicking on the image below or via this link.

To help me 👇

A free alternative to support me?

Of course, just subscribe below 👇


For whom?

For whom?

For Laravel devs, you guessed it.

Subscribe to not miss the next issues and receive them directly in your email box!

Subscribe now

PS : tu préfères la version Française, clique sur le drapeau tricolore

👉 🇫🇷


Meaning of emojis used in titles

  • 📖 Article
  • 💡 Tip
  • 🆕 News / Update
  • 📦 Package
  • 🎙️ Podcast
  • 🐦 Tweet / Xeet
  • 🎥 Video

🇬🇧 📖 A complete history of Laravel's versions (2011-2023)

If you're interested in the history of Laravel versions since its inception, then you should read Benjamin Crozat's article (@benjamincrozat).


See the history of Laravel


🇬🇧 📖 Single-Use Tests

Tim MacDonald (@timacdonald87) shares his technique for managing single-use tests that he doesn't want to send to his project's repo.


Read the article


Battle Ready Laravel by Ash Allen

The link below is an affiliate link, it means that if you buy this book, I will get a small commission. If you don't want to help me, just search "Battle Ready Laravel" on your favourite search engine ;-)

The ultimate guide to auditing, testing, fixing and improving your Laravel applications so you can build better apps faster and with more confidence.

Order on Amazon


🇬🇧 🎥 The History of Laravel's dd()

Nuno Maduro (@enunomaduro) takes you through the history of the `dd()` command in this very short video.


🇫🇷 📖 The basics of CQRS in Laravel

Mathieu De Gracia (@DeGraciaMathieu) from Laravel France (@laravel_france) has written an article explaining the CQRS architecture.

Here's the introduction:

🇫🇷Le pattern CQRS, pour Command Query Responsibility Segregation, vise à séparer les opérations de lecture (queries) des opérations d'écriture (commands) de votre application.

Son principal objectif est d'améliorer la scalabilité et la flexibilité de l'application en traitant les requêtes de lecture et les commandes d'écriture de manière totalement indépendante.


🇬🇧 The Command Query Responsibility Segregation (CQRS) pattern is designed to separate the queries and commands of your application.

Its main objective is to improve the scalability and flexibility of the application by handling read requests and write commands completely independently.


Read the article


Infomaniak Web Hosting

The link below is an affiliate link, it means that if you buy this book, I will get a small commission. If you don't want to help me, just search "Battle Ready Laravel" on your favourite search engine ;-)

Infomaniak's reputation is well established 🇨🇭

Quite simply, it's one of the best web hosts around.

Discover Infomaniak


🇬🇧 🎙️ Some reasons to write a down method in your migrations

I'd like to take this opportunity to introduce a new type of content that we haven't yet had on "Laravel in everyday life": the podcast.

No compromises with Aaron Saray (@aaronsaray) and Joël Clermont (@jclermont)

Here's the introduction by the authors:

This is a surprisingly controversial topic. In this episode, we share why we write down migration methods, and it's probably not the reason you're thinking of.


Listen the podcast


This newsletter with its short format is yours, come and tell me what you think in the comments 👇

Leave a comment


See you soon for the next issue.

If you haven't already done so, subscribe!

Subscribe now

Stay in the loop

Get new articles delivered directly to your inbox. No spam, unsubscribe anytime.

0 Comments

No comments yet. Be the first to comment!