Always use [closed, open) intervals
– fhur.me
A good tip by Fernando Hurtado
Read more [fhur.me]
– fhur.me
A good tip by Fernando Hurtado
Read more [fhur.me]
This post is about Rails, but applies to Laravel as well
Read more [dev.37signals.com]
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"As a Laravel developer, this is the one newsletter I most look forward to. Freek has a talent for distilling packages or techniques down to something immediately useful - one tip can save you hours and even weeks. It's concise and practical and highly relevant."
– tray2.se - submitted by Patrik Ahlström
Tracking changes in a table or several tables for that matter can be essential for your application, and we are going to take a look on how to do that using only the MySQL/MariaDB database.
Read more [tray2.se]
Here's how you can make sure that all implementations of an interface behave correctly
Read more [www.kai-sassnowski.com]
– planetscale.com - submitted by Aaron Francis
A comprehensive overview of Laravel's many safety features that can help you prevent painful mistakes.
Read more [planetscale.com]
– tray2.se - submitted by Patrik Ahlström
What is a database view, and how can we use it to make our code cleaner?
Read more [tray2.se]
My colleage Sebastian digs named arguments in PHP. As do I!
Read more [sebastiandedeyne.com]
According to the React maintainers, React developers reach for the useEffect hook too quickly. It is far from the only hook with many naive usages. Why won't we go through my favorite example of an incorrect usage for useRef?
Read more [flareapp.io]
Good tips by Jeffrey Way
Read more [laracasts.com]
– arunas.dev - submitted by Arunas
You'll learn the difference between "tactical" and "strategic" programming, and why choosing the right approach is important in the long run.
Read more [arunas.dev]
Let's explain the two most important topics when working with RDBMSs: indexes and transactions.
Read more [architecturenotes.co]
– arunas.dev - submitted by Arunas
Before we learn strategies for better software design, we must understand our enemy - complexity. Let’s define complexity, how to spot it, and what causes it.
Read more [arunas.dev]
DRY is just like every other principle out there - it has its place, but it's best taken in moderation.
Read more [gordonc.bearblog.dev]
Some good tips for writing effictive, human-friendly documentation.
Read more [thenewstack.io]
Did you know that DateImmutable isn't really immutable?
Read more [matthiasnoback.nl]
A nice list of things to keep in mind when writing software or documentation.
Read more [leerob.io]
Personally I don't know if this is a good practice, but you (and future me) might like it.
Read more [www.aaronsaray.com]
There are a couple of nice ideas there to solve longstanding problems with UUIDs
Read more [www.ietf.org]
I'm proud to announce that our new premium course on writing readable PHP is now available. It's called Writing Readable PHP.
This course contains a collection of bite-size tips (both in written form and videos) that make your code a joy to read for your co-workers and future self. These tips are aimed towards developers who know the basics of PHP and want to improve their craft. As a bonus, you'll learn to use static analysis to ensure that your code is understandable and correct.
Writing Readable PHP has been created by our team and Christoph Rumpel. It contains our combined knowledge on how to write the best PHP possible.
– doeken.org - submitted by Doeke Norg
DRY up code by deferring specifics to a callback.
Read more [doeken.org]