greg0ire 

@[email protected]
200 Followers
221 Following
869 Posts
J'ai plus d'une corde à ma harpe
greg0ire Mar 11
Pauline VosMar 11
Hit me with your best resources for learning C
greg0ire Feb 14
Julia EvansFeb 14
now that Git 2.53 is out, the Git data model @omarieclaire and I wrote is on the official Git website! https://git-scm.com/docs/gitdatamodel
Git - gitdatamodel Documentation

greg0ire Feb 10
golangFeb 10

🥳 Go 1.26.0 is released!

📝 Release notes: https://go.dev/doc/go1.26

⬇️ Download: https://go.dev/dl/#go1.26.0

#golang

greg0ire Feb 6
Sebastian Bergmann Feb 6

I have released #PHPUnit 13:

https://phpunit.de/announcements/phpunit-13.html

Release Announcement for Version 13 of PHPUnit

The PHPUnit development team is pleased to announce the immediate availability of PHPUnit 13. This release adds new features, changes and removes existing features, and fixes bugs.

greg0ire Feb 1
Dan LeechJan 31

Unhinged, sweary but beautifully illustrated blog post about legacy project structure: Space - the Final Straw

https://www.dantleech.com/blog/2026/01/30/space-the-final-straw

#php

greg0ire Jan 31
At #fosdem2026 , getting my feelings hurt
greg0ire Jan 27
Show threadSimon PraetoriusJan 26

@jaapio I would say: If I‘m having a hard time understanding something that shouldn‘t be hard or complicated, I won‘t merge. No matter which tools were involved in the process. Same goes for docs or comments.

Like this: https://mathstodon.xyz/@mjd/115096720350507897

Mark Dominus (@[email protected])

I think many people misunderstand the purpose of code review. The purpose of code review is not for the reviewer to find bugs, and certainly not for them to ensure that the code is bug-free. Anyone who depends on code review to find bugs is living in a fool's paradise. As everyone should know by now, it is not in general possible to find bugs by examining the code. The primary purpose of code review is to find code that will be _hard to maintain_. The reviewer looks at the code and tries to understand what it is doing and how. If they can't, that means it will be hard to maintain in the future, and should be fixed now, while the original author is still familiar with it.

Mathstodon
greg0ire Jan 27
JaapioJan 26
Fellow #maintainers. How do you handle #LLM generated pull requests? For me a small pr that fixes a bug or adds a feature is great. But what todo with new subsystems... For example introduce caching. Or even push a large wall of text, that explains exactly nothing?
greg0ire Jan 19
Ondřej MirtesJan 19

PHPStan 2.1.34 is out with two great advancements:

Optimized performance: between 25 % to 40 % faster times thanks to more caching and raw performance tweaks in code.
More precise analysis with Fibers (super-cool) on PHP 8.1+.
Upgrade today and let me know how it works for you!

greg0ire Jan 19

📦release: `doctrine/collections` 3.0.0

Most notably, `Selectable` is now extended by `ReadableCollection` (which is extended by `Collection`).

Check out the release notes: https://github.com/doctrine/collections/releases/tag/3.0.0

Release 3.0.0 · doctrine/collections

Release Notes for 3.0.0 Backwards incompatible release (major) 3.0.0 Total issues resolved: 0 Total pull requests resolved: 10 Total contributors: 4 BC break 522: Make ReadableCollection extend ...

GitHub