Freek.dev

We talk about cleverness as if it’s Just Bad, such as “clever code is harder to debug”. That’s going too far. Cleverness can lead to faster, safer, even clearer code.

Read more [www.hillelwayne.com]

PHP is a fantastic language that has seen many cool improvements over the past few years. What you may not be aware of is that only a very few people can work on the language itself. This is obviously not healthy and hopefully this situation will improve in the future.

Read more [blog.krakjoe.ninja]

All models are wrong but simple models are more wrong than complex ones. Simple models are more appealing, easier to teach and spread and apply. Because of that, they can bring value faster, and they can cause harm faster.

Read more [verraes.net]

Tony Messias been looking up resources on the roots of Object-Oriented Programming. He shares some very interesting ideas.

Read more [www.tonysm.com]

Yesterday, Matt Stauffer on Twitter was very open on some mental health issues he is coping with. In response Kai shared this older blogpost which resonated with me.

Read more [www.kai-sassnowski.com]

My colleague Brent makes the case for targetting and uses the latest PHP version.

Read more [stitcher.io]

My colleague Brent makes the case for being more creative on the web

Read more [stitcher.io]

In this post, Francois Zaninotto explains why and how he stopped working on Faker.

Read more [marmelab.com]

Seb makes the case that subtracting things can be better than adding things.

Read more [sebastiandedeyne.com]

Brent offers scientific arguments why a light color scheme is better. Personally, since I started using a light color scheme a few years back, I've sticked to it and never turned back.

Read more [stitcher.io]

Brent wants you to vote yes. Here's why from the point of view of a userland developer, both for client projects and open source.

Read more [stitcher.io]

AnyList explains in great detail why they made this decision.

Read more [blog.anylist.com]

My colleague Brent shares a story to illustrate why you shouldn't write your own framework.

Read more [stitcher.io]

What's the ideal amount of abstraction? When does a framework start having "too much magic"? When are there too many languages in an organisation?

Read more [ferd.ca]

Larry Garfield has some interesting thoughts on how PHP can be improved.

Read more [hive.blog]

String concatenation is the current way we can pass arguments to Laravel middleware - but what if there was another way

Read more [timacdonald.me]

This is what would happen to PHP if my colleague Brent's will was law.

Read more [stitcher.io]

In a new blogpost, my colleague Seb explains why he chose not to use any JavaScript framework for the interactive parts of Mailcoach

Read more [sebastiandedeyne.com]

Mattias Verraes explains a method for making technical debt visible and negotiable.

Read more [verraes.net]

JMac, the creator of Laravel Shift, has a few interesting ideas on how to make the framework better.

Every so often a revolutionary change is required. This provides a chance to revisit goals. One of the primary goals of Laravel is developer experience. And maintainability, freshness, and approachability all improve developer experience. So, with all this in mind here are the top five things I would change in Laravel.

Read more [jasonmccreary.me]