I miss the days I could look at multiple files from @github.com PRs at once.

The way I watch people use Laravel's enum_value() sometimes makes me wish PHP didn't add enums.

I miss the days when I could work on open source code without being forced into having political opinions.

GitHub stops responding the minute after I push my own release to production. Surely that's just a coincidence.

This week is one of those weeks that reminds me why my OSS contributions have slowed down to (mostly) business needs. I'm too technically apolitical to care enough to want to work a 2nd full time DevOps/SA job just to not use a GitHub-like service.

I missed the news about Microsoft's CoreAI and GitHub being placed under it from the beginning of the year, but with that knowledge in mind, it explains so much about the (questionable) direction GitHub's moving.

Something I will never not be annoyed by as an OSS maintainer is how quickly people will pile on with +1 or "up" comments on issues but heaven forbid anyone do anything to help test or review changes.

If you can't even be bothered to replace the AI-generated placeholder in your email closing, I'm just going to assume that you and everybody you work with are incompetent at your jobs and should seek new work. Attention to detail matters, folks.

I always get a chuckle about the people who groan about OSS projects not self-hosting all their infrastructure. Not every project has the resources to do it, and not everyone wants to volunteer to be a full-time DevOps person for an underfunded software project.

It's 2025 and there are still OSS projects which will not run their automated tests or static analysis tools if the code style isn't up to snuff. But I'm sure a line not being indented properly is good cause to not run the unit tests to validate a change.

The sooner we see the end of corporate exploitation of open source software (LOL who am I kidding it won't happen), the sooner posts like gitlab.gnome.org/GNOME/libxml... stop being a normal thing.

Which of you broke Google Cloud?

Another day, another waste of time blocking IP addresses from LLM enabled web crawlers. Oh, BTW, Scrapy, it's really a dick move to have a SaaS that doesn't publish an IP list, and also a red flag on how bad your product is.

The more I try to use Laravel's ApplicationBuilder "slim skeleton", the more I get bitten by bugs that it introduced by changing the order of operations for when certain things run.

My GitHub notifications today say that folks don't read past the pinned and/or most recently opened issue.

I would pay good money for a GitHub feature that blocks commits where the message is "wip".

It only took 6 months for someone to figure out that using negative emoji reactions when someone’s behavior deserves said reactions shouldn’t be a banable offense.

There aren't many things more cringeworthy than the excessive emoji use in AI generated content.

I'm pretty sure there is no PHP SDK I've worked with that is worse about versioning than Twilio.

Today's protip for developers, don't store version strings as floating point numbers.

One of the most annoying things about all the AI hype is how much time I spend figuring out what network ranges I need to block because they're all so spammy.

It’s not a bug for a #PHP #Symfony bundle to be using the token storage on a stateless route, I shouldn’t have to work around upstream fixes because of this misunderstanding.

Interesting choice by Laravel to make github.com/laravel/nigh... an AGPL package instead of MIT…

Well here’s a first, and a last @rec.poker

Well, at least I’m learning to check out on weekends.

I don’t know which AI service CodeRabbit is using under the hood, but based on an auto-generated PR review comment I just read from it, seems like the service is just full of bad advice thanks to the cutoff dates of all of the models.

I’ve had git commit signing turned on in my global git config for years, so having to fight with PhpStorm’s new signing feature, which also tries to manage it at the repository level and seems to not support global config, is kind of annoying.

Vue’s type coercion on certain form elements will be that thorn in my ass that I’ll never get rid of.

SQL gen tools that ignore every configuration and directive regarding these critical bits are not production ready: - Not creating write queries (INSERT, UPDATE, DELETE, etc.) - Applying filters based on a security configuration - Only reading from allowed tables and fields

People aren’t going to Mastodon or Bluesky because one of those platforms is generally better than the place we still call Twitter. People are going there because each of those 3 services has their own target user audience and people are finding the one they most fit into.

Someone in one of my feeds shared the W3C CMS trends to hype WordPress’ market share. Ignoring that anomaly in the data for the moment, my key takeaway from those trends is that the ideals of open source and/or the concept of owning your data aren’t enough to win the market.

Well, this is awkward. #PurposefullyVaguePost

275 files changed, 3490 insertions(+), 7516 deletions(-) Not a bad way to go out before a holiday weekend I suppose.

Given everything going on in the #WordPress ecosystem, now’s a really bad time for paid plugins to be adding new telemetry features (even with a user friendly config screen for them). Also, don’t use guilt tripping language on your telemetry config.

With tags equating to releases in the PHP ecosystem, it’s not surprising everyone thinks the minute a release tag is published in the PHP source repo, it’s been released. Unless I missed something in nearly 15 years working on PHP, the tag being pushed has never meant released.

It’s crazy how in one CMS ecosystem, everyone will groan that if it isn’t part of core, it’s not safe to use & being in core makes it better maintained and more secure (it’s not), yet in another CMS ecosystem, you better be ready to install dozens of plugins for a useful website.

You can tell which companies really don’t care about their #PHP customers when they can’t even be bothered to start updating their extensions for the next release until months after the stable tag is created.

There’s something ironic about people saying they’re abandoning a social platform they made zero effort to engage in in favor of a social platform they’ve put effort into engaging on.

Hot take. Automatic updates like those promoted as a first-class feature of WordPress goes against every responsible software maintenance best practice you can think of. Why should I assume all of the risk because someone else can update my software at any time?

Welp, I'm here. We'll see how quickly this joins my collection of social media accounts that barely get any attention.