Building software these days has way too many rules. I don't follow rules I don't agree with or understand - I prefer to do whatever gets the job done. That's pragmatic, that is.
The term YOLO Architecture refers to, essentially, the complete lack of consistency, guidance, or rules within a software system. Or at least, the lack of enforcement or application of whatever rules might ostensibly exist or be given lip service.
The result of a YOLO approach to architecture is, invariably, the Big Ball of Mud architecture, basically by definition.
Building software these days has way too many rules. I don't follow rules I don't agree with or understand - I prefer to do whatever gets the job done. That's pragmatic, that is.
The term YOLO Architecture refers to, essentially, the complete lack of consistency, guidance, or rules within a software system. Or at least, the lack of enforcement or application of whatever rules might ostensibly exist or be given lip service.
The result of a YOLO approach to architecture is, invariably, the Big Ball of Mud architecture, basically by definition.