Comments by "MrAbrazildo" (@MrAbrazildo) on "What Software Architecture Should Look Like" video.

  1. 11:40, I use to think the general flow of data as a simple thing. But in practice, some ugly measures have to be done. Splitting classes to keep data security, more layers of data access to become clear, and so on. All things that I rather not do, but technically I feel compeling to. People discuss how much inheritance can mess things up, but I don't use to have such issues: I start with a simple thing, focused on what I need now, and throughout time I come back to make little upgrades. It's a kind of "become forced by practice" motto. 13:15, there's a problem in multithread, called "false sharing": each time a process read a cache line (32 or 64 bytes), it blocks to all other threads the access to that line (those bytes). To solve this: put data from each thread in different cache lines. 17:20, someone said, in a recent presentation: "Classes work as black boxes: we put things there and forget about it" . I appreciate this in design: the less 1 needs to keep in mind, the easier it will be to upgrade the architecture.
    3