Intro
Since [Dijkstra initiated the structured programming revolution](https://www.cs.utexas.edu/users/EWD/transcriptions/EWD02xx/EWD215.html), we split software in components. Sometimes these are made explicit, either by a module system supported at the language itself or by a convention system, but even when no such formalisation takes place we have some sort of logical grouping. A component by itself won’t be useful to the *end-users* of the software. In order to become useful, we group software co...

My understanding of the evolution of software components
## My understanding of the evolution of software components

Historically, programs were thought of as a single, self-contained, and monolithic piece.

As systems, projects, and teams grew in size and complexity, we looked for better ways to manage our software and its development cycle. Initially we started opening the black-box of applications and logically grouping code and assets based on having similar responsibilities. There are many philosophies around how and what to split, but what ma...

Monolith Days

The single-page app