sneakyPad
Having said that, I read (I think also from Luciana Ramalho) that inheritance can make sense when developing a library/package itself. Nevertheless, I would try to use static protocols as long as it seems possible. Inheritance for code reuse is an implementation detail. It can often be replaced by composition and delegation.
I hope this gives you a bit more context to the article and idea of using behaviour over inheritance.
How I build internal developer tools inside a small team
How bugs made me believe in TDD
Pytest Fixtures: How to Use and Organize Them in Your Test Architecture
The LLM Hype Train: A Pamphlet[?] You Should Read with Your Manager
Show HN: LemonSpeak – I created a Podcast Copilot that generates content for you
The app is very simple from a user perspective. You upload a podcast, specify the language and the names of the speakers and click start. Then you get a diarized transcript with VTT, show notes, summary, SEO-optimised titles, tweets and a blog post.It's not just a GPT wrapper, though. The architecture behind it is more complex because I have long running tasks (speaker diarization) that require...