Lau Bannenberg

I've felt that pain. When some API call randomly fails because an id was already used by a dev environment that doesn't even exist anymore.

Great Art Explained is very nice. It avoids jargon but it has real substance. I like that they look from a lot of angles (social, technical etc) at why the piece is so interesting.

Option B) is to make a full component (blade, vue, react or whatever) that combines html and styling in one file

Option A) use "@apply" to make for example a btn-primary class that contains all the utility classes for styling primary buttons. So a bit more semantic CSS again.

If you find yourself using the same combination of utility classes over and over that's a hint that you could extract a reusable component and/or design token there.

And there was much wailing and gnashing of regexes

What he said, plus juggling file ownership between www-data and your ssh user.

Looks legit

The docs say that if you use once() from within an object instance, it'll be "once for that instance", not once globally, that might be the reason?

It feels like there might (should!) develop a rift in the market between slop sellers and vendors that painstakingly guard a reputation for quality.

Use AI if it makes sense, but have a QA process with teeth, because your good reputation is going to be your lifeblood.

I'm missing a "customs has a package for you, but you need to pay duties" with a glaring lack of detail about which package they're talking about or how the duties were calculated.

It's painful every time I'm looking at a second hand game sale, wondering which are the good ones.

I've noticed some N+1 queries can be hidden deeply by good intentions. You have some gnarly operation that you put in an action class, very clean and reasonable. And then someone uses that class in a loop somewhere, but the repeated query is no longer plainly visible because it's in another file.

Yeah docker desktop did _not_ play well with DDEV (on Linux). And was mostly unnecessary. Might be a good NativePHP project to just provide a little GUI to spot check what's running though.

Yeah, you should be getting feedback from what is causing customers trouble. Fixing it. And then you don't need a chatbot to handle repeated complaints.

It can answer confidently... too confidently.

I was tidying up an old php website that didn't use anything as new as classes. But it had been running unmaintained without any problems for six years. I was kinda inspired by how nice simplicity can be.

Today is one of those days where I think you should always multiply "just the work" by the number of stakeholders to set a more realistic lower bound

Maybe much of the value is in minimizing the amount of git a new hire has to learn, before being able to contribute actual work. Similar to how road signs don't innovate all that much. We're optimizing to address the largest possible population.

Much of it comes down to a git hook kicking off a script that spins up a docker container, injects some secrets, clones into the container, and then runs some more scripts in thr container. The 80/20 use case is not magical, just really convenient.

But this isn't over yet. Paywalls, but also more news sites having features like "gift articles" that let o e reader pay to open the wall to others, are attempts to build a new market.

There is demand from readers, and supply from journalists. This market *wants* to exist. But what is basically industrialized piracy by AI firms is getting in between.

FrankenPHP hit 9k stars on GitHub.
At 10k, we'll make a stuffed elePHPant!

Click, click!

I'd go with 8.2 because I want to make sure I can use readonly classes for value objects. Don't want people to start using on 8.1 and then get friction if I start using some.

Or maybe 8.4 so I'll have a clear path when 8.5 comes out, the pipeline syntax is sweet.

It was a lot of fun, looking forward to the next one!

AmsterdamPHP Special PHPVerse Edition, Tue, Jun 17, 2025, 6:30 PM | Meetup **🎉 Special AmsterdamPHP Meetup – June 17th, 2025** Right after **[PHPVerse 2025](https://lp.jetbrains.com/phpverse-2025/)**, we’re keeping the momentum going with two of

If that link doesn't work, try this one: meetu.ps/e/P1xQT/m08S... :)

Github has a big advantage with the community around actions. There's a lot more information and examples than I found for Bitbucket. But I did most of the work in deployer, the actions are just for getting the ball rolling

I found it pretty easy to set up with github actions. Bitbucket pipelines was a bit harder but still doable. I put most of the logic in deployer. I like how very customizable it is.

It makes more sense when you try to imagine $game-template as a PHP variable. (Sirens in distance)

Yes always