Not just another discussion on programming style, but program development, with a focus on data.
I like the idea of having models and enforcing themselves. For example, testing that three different API endpoints of a service match each other's idea of their objects. This is a sanity check when we verify the frontend state.
If we could separate scraping from modeling constraints, we could potentially collect data separately from the verification step. Then we aren't left waiting for UI DOM stuff when we verify the model. The latter can happen separately, and extremely quickly.
I like the idea of having models and enforcing themselves. For example, testing that three different API endpoints of a service match each other's idea of their objects. This is a sanity check when we verify the frontend state.
If we could separate scraping from modeling constraints, we could potentially collect data separately from the verification step. Then we aren't left waiting for UI DOM stuff when we verify the model. The latter can happen separately, and extremely quickly.
See also
Data-Oriented Programming. Sharvit, Yehonathan. Manning 2022.
Principles of Program Design. M.A. Jackson. 1975.
SAM Pattern. Jean-Jacques Dubray. https://sam.js.org/