With more than three repetitions of the same algorithm the kid should’ve been automating the process.

Yeah but I was talking about the opposite. I can clearly spot composition in many frontend framework such as react or flutter but e.g. spring DI is a different thing to me.

I think you’re confusing composition with aggregation. DI can’t be composition because the injected object is shared/borrowed, strong composition on the other hand requires the object to be owned. A composed child does not exist without its parent.

True but due to the framework in use it’s more or less applicable and I can’t think of a single commonly used backend stack that’s relying on composition whereas I know a bunch of frontend stacks. I guess composition is handy for widget trees so that’s why you see it more often in frontend apps.

Works in frontend I guess but backend is a whole different story.