Why I Avoid PHP Traits
I want to add a private method without checking the internals of every trait the class uses. PHP's trait mechanics make that harder than it should be.
Writing / From experience
Things I’ve tried, problems I’ve run into, and how I’ve worked through them.
7 posts
I want to add a private method without checking the internals of every trait the class uses. PHP's trait mechanics make that harder than it should be.
Starting again gives us a chance to use what we’ve learned. Deciding whether to do it means understanding what we can improve, what we might lose, and what it takes to keep the next system worth building on.
My thoughts on this well explored topic, and why I struggled to truly differentiate between the two concepts for a long time.
Grouping code by technical layer means jumping across the project to follow one feature. I group by feature instead, and adapt the structure to whatever the language and framework expect.
AI doesn't eliminate engineering work. It moves it — onto reviewers, and onto your future self.
Your understanding of a problem is lowest before you write the code. The systems that actually last are grown through real-world feedback, not built from a master plan.
Wasm is a genuinely interesting runtime primitive. I think it could become the compute layer of the web. I also think that probably won't happen anytime soon.
No posts match. Try another search or clear the selected topic.