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.

📢 We just published a deep dive on compile-time-only generics and we need your feedback!

This isn’t "full generics". It’s a scoped, performance-friendly approach focused on interfaces and abstract classes.

Is this the right direction for PHP?

https://thephp.foundation/blog/2025/08/05/compile-generics/

🚀 Neos 9 is here! 🎉
We’re excited to announce the launch of Neos 9 and Flow 9 with the Event Sourced Content Repository, elevating content management.
Key highlights:

Event Sourcing – complete history of content changes 📜

Smarter publishing – update properties without overwriting pages 📝

Font Awesome 6 – hundreds of new icons 🎨

Improved performance – faster routing, better scalability ⚡

Big thanks to all contributors! 🙏
For more, check our blog post on neos.io. 📚

#Neos9 #NeosCMS #EventCR