Freek.dev

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]

Gergely Orosz argues that you should start with a simple design and try your best to keep it simple. I don't necessarily agree with everything in the post, but it's an interesting opinion nonetheless.

Software architecture best practices, enterprise architecture patterns, and formalized ways to describe systems are all tools that are useful to know of and might come in handy one day.

Read more [blog.pragmaticengineer.com]

Extracting doesn’t guarantee simplicity. Sometimes extracting code into another module means I’ve smeared one “conceptual module” in my brain into two physical files. Now I can’t look at the whole thing at once, and their internal wiring is more prominent than it deserves. Oops.

— Dan Abramov (@dan_abramov) September 25, 2019

Read more [twitter.com]

Mike Veerman points out that managers that are not making decisions are lazy.

Lazy management means not choosing. It’s only paying lip service. When we put quality first, together with security and performance and everything else, we’re not doing our job. We’re postponing the inevitable in the hope the monster goes away.

Read more [www.mikeveerman.be]

An interesting opinion written by my colleague Seb.

Over the years I’ve experimented with different strategies to build user interfaces. From sprinkling JavaScript over server side templates to full-blown SPAs. My conclusion up until now: we can do better.

Read more [sebastiandedeyne.com]

Contrary to the title, Gilles Chehade that it's acutually doable running your own mailserver.

TL;DR: Mail is not hard: people keep repeating that because they read it, not because they tried it. Big Mailer Corps are quite happy with that myth, it keeps their userbase growing. Big Mailer Corps control a large percentage of the e-mail address space which is good for none …

Read more [poolp.org]