An opinion piece arguing that larger components are often preferable to prematurely splitting code into many small sub-components. The author contends that over-componentization leads to wrong abstractions, harder navigation across files, and more glue code (Angular @Input/@Output bindings) that can introduce subtle bugs. Valid reasons to extract a component include measurable performance issues and genuine code reuse across multiple places. The post draws on Greg Young's 'write code that is easy to delete' philosophy, suggesting that code inside bigger components is easier to adapt and delete than code locked into premature abstractions.

4m read timeFrom timdeschryver.dev
Post cover image
7 Impressions