markus staab

@markusstaab@phpc.social
234 Followers
30 Following
889 Posts
software development with passion - open-source lover, creator of staabm/phpstan-dba, excessive freetime @phpstan, @rectorphp and @phpunit contributor
Bloghttps://staabm.github.io/
GitHubhttps://github.com/staabm
Twitterhttps://twitter.com/markusstaab

Things I've been up to over the last 30 days:

- 👨‍🍼 Became a dad
- 🎉 In between diaper changes, I worked on preparing the release of version 2.0 of Valinor, a PHP library that helps to map any input into a strongly-typed value object structure.

Release notes: https://github.com/CuyZ/Valinor/releases/tag/2.0.0
Upgrade guide: https://valinor.cuyz.io/2.0/project/upgrading/#upgrade-from-1x-to-2x

Enjoy! 🥳

I'm still surprised by how often I meet people who are surprised to learn that I offer consulting, coaching and training services focused on #PHPUnit and other #PHP-related topics.

I’m passionate about helping PHP development teams overcome the challenges they face, whether that's improving code quality, mastering PHPUnit or modernising their software.

If you struggle with PHP, I can help you find the right solutions. Let's work together to build better software!

https://phpunit.expert/?ref=mastodon

phpunit.expert - Professional Services around PHPUnit from Sebastian Bergmann

Learn PHPUnit directly from its creator. Sebastian Bergmann offers professional training, workshops, and consulting for your team.

usually I use a deprecated-phpdoc to mark code which no longer should be used.

This doesn't work for parameters though.
PHP 8.4 native #[Deprecated] doesn't support it either.

TIL: #[\JetBrains\PhpStorm\Deprecated] works for this case.

Ever ran your #phpunit test-suite to create a code-coverage report and after waiting minutes, a warning showed up, that you forgot to configure/load the coverage driver (xdebug or pcov)?

Fix it for you in the upcoming PHPUnit 12.x release - it will immediately stop.

If someone’s looking for open source projects to contribute to, I have some static analysis failures that I’m not sure what to do about.

https://github.com/ramsey/uuid/pull/603

#PHP

Re-add the @pure annotations by ramsey · Pull Request #603 · ramsey/uuid

Description Add @pure annotations where the @psalm-pure annotations used to be. Motivation and context These were removed in 691c2c8 but should remain in the code base. For more information, see di...

GitHub

I rarely subtoot, but when I do just to say: if an open source project that your commercial project depends on breaks something in your software stack, causing you trouble, no matter how much, that's your problem and your problem alone.

"The software is provided as is" is a part of OSS licenses for a reason, and unless we have a contract that says otherwise, I'm not part of your bloody "supply chain".

I declined a $1,000/month ESLint sponsorship from a pay-for-follows company. That's not the type of sponsor we want. It's frustrating that these types of companies (as well as online casinos) are more willing to sponsor ESLint than tech companies where ESLint is used.

Running a few @infection_php performance tests on the #valinor codebase, to get an idea how we progressed in newer versions and latest dev-master.

seems were are working in a good direction 🚀

Yesterday I hunted down a performance regression in #phpunit 11.x and 12.x when big objects (e.g. ReflectionClass) are used in dataproviders, in comparison to phpunit 10.x

Proposed a fix, short discussion with Sebastian Bergmann, and here we go: Fix released today.

love it.

Yesterday I hunted down a performance regression in #phpunit 11.x and 12.x when big objects (e.g. ReflectionClass) are used in dataproviders, in comparison to phpunit 10.x

Proposed a fix, short discussion with Sebastian Bergmann, and here we go: Fix released today.

love it.

×
Let's see whether we can get @infection_php faster ⚡️
@markusstaab @infection_php given the huge amount of improvements merged, are you planning to release/tag a new version soon? (RC, Beta appreciated too ;-) )