To Array is Human
Context matters more than dogma. Why arrays aren't always evil and how to know when rules don't apply.
10 posts found
Context matters more than dogma. Why arrays aren't always evil and how to know when rules don't apply.
The 'U' in CRUD is lying to you—updates don't tell the story, domain events do.
Stop wrapping ORMs and start thinking in collections. Build repositories that are specific, immutable abstractions over your domain.
Ditch the 'Interface' suffix—let abstractions have pure names and implementations be specific.
Interfaces are like electrical outlets - they remove complexity and make components easily swappable. Learn how to use interfaces to decouple your software components.
Fat interfaces lie about their capabilities—split them into focused contracts that use types, not boolean checks.
Stop polluting your code with 'Interface' suffixes, pattern names, and namespace taxonomies—less noise, more clarity.
Singletons are convenient until you try to test them—but they have their place in bootstrapping code where coupling is expected.
Rules say that for unit testing we should not access the filesystem, but what if you don't have a filesystem abstraction you can stub?
Four rules I try to sacredly adhere to when streaming data for reporting purposes in PHP.