A blog about modern PHP, the web, and programming in general. Follow my newsletter and YouTube channel as well.

Stitcher Engineering Blog offers insights, tutorials, and updates on building scalable, reliable, and high-performance systems for podcasting and audio streaming. Covering topics such as backend architecture, media processing, and content delivery, Stitcher Engineering Blog provides resources for developers and engineers working in the audio streaming industry. Developers can learn about building resilient systems, optimizing media workflows, and delivering high-quality audio experiences through Stitcher's blog posts and technical articles.

stitcher.io

The author discusses their frustration with the misuse of inheritance in object-oriented programming, arguing that inheritance should reflect real-world relationships while interfaces should describe technical behavior. The misuse is compared with Alan Kay's original vision for OOP, which emphasized simplicity. The author believes current practices complicate software design unnecessarily and offers a mental model to make sense of the issue.

Extend or implement

I love this thought process as a fellow object oriented design nerd.
I think this article could’ve benefited from better defining “technical” when choosing between interface and inheritance.
Does it mean implementation details? Architecture layer (domain / application / infrastructure)?
How does interface segregation play a role?
Sure, that gets a little further into the weeds, but that’s why OOP is hard to design. Tons of nuance.