I spent some time last night thinking about the file structure of #PHP projects in a world where insights like https://www.theverge.com/22684730/students-file-folder-directory-structure-education-gen-z exist.
It made me wonder, what would things look like if we did away with nested directories? Is there another means of organizing code that would be both efficient from a computational standpoint and intuitive to humans?
So I did a thing. I volunteered to be a release manager for #PHP 8.2. Here's hoping elections go in my favor :-)
Regardless, I'm still writing a book on PHP for O'Reilly and will be paying close attention to this release so I can accurately cover it.
Probably time I wrote an actual #introduction piece ...
Today's challenge: refactoring a legacy app written in procedural #PHP that has no test suite.
Objective: object orientation and at least 50% code coverage.
Please: send Skittles...
I'm working on documenting some #PHP design patterns. One fun pattern is "value object." In a past life, we used a custom approach with value objects to protect personally identifiable information (PII) in an application.
Functions can act on the objects and pass them around, but the data inside is protected in most contexts. Would this be an interesting read for y'all?
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!