Conversation

Notices

1. Embed this notice
   Rusty Crab (rustycrab@clubcyberia.co)'s status on Monday, 16-Oct-2023 04:43:11 JST Rusty Crab

   in reply to

   • a7
   • PunishedD
   @a7 @PunishedD I have never looked at UML and said "oh that explains it"
   • Sexy Moon likes this.
   • Embed this notice
     a7 (a7@miss.mouse.services)'s status on Monday, 16-Oct-2023 04:43:12 JST a7

     in reply to

     • PunishedD

     @PunishedD@clubcyberia.co @RustyCrab@clubcyberia.co I just don't realize how this many words could be written about it, I sometimes have referenced UML diagrams to get an easier picture of some shit CRUD im working with but I never sat down and asked my self about the philosophical design decisions around it.

   • Embed this notice
     a7 (a7@miss.mouse.services)'s status on Monday, 16-Oct-2023 04:43:13 JST a7

     in reply to

     • PunishedD

     @PunishedD@clubcyberia.co @RustyCrab@clubcyberia.co the entirety of UML could be summed up as "a bunch of boxes with lines drawn between them" yet some psychopath wrote this

   • Embed this notice
     PunishedD (punishedd@clubcyberia.co)'s status on Monday, 16-Oct-2023 04:43:13 JST PunishedD

     in reply to

     • a7
     @a7 @RustyCrab UML is very important if your job is drawing diagrams, and very useless if your job is literally anything else. I have never had a UML diagram affect or improve any system I've worked on in my career.
   • Embed this notice
     PunishedD (punishedd@clubcyberia.co)'s status on Monday, 16-Oct-2023 04:43:14 JST PunishedD

     in reply to

     • a7
     @RustyCrab @a7 UML was one of the 3 tools Satan uses against the righteous.
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Monday, 16-Oct-2023 04:43:15 JST Rusty Crab

     in reply to

     • a7
     @a7 none of these words are in the bible
   • Embed this notice
     a7 (a7@miss.mouse.services)'s status on Monday, 16-Oct-2023 04:43:16 JST a7

     UML is organized around the object-oriented concept of namespace, which refers to a collection of objects to be treated as a named group. The architecture of object-oriented programming is predicated on this concept. The problem with this, however—as described above in the section on relationships—is that it makes it extremely difficult to treat a subject/predicate/object as a logical unit, since the object class cannot be contained in the namespace that is the subject class. A “property” of the subject class is the rolename only, without the class that is being named. For example, in Figure 2-11, above, “an example of” can be a property of Internal Organization, but “an example of Internal Organization Type” cannot. Moreover, since in the object-oriented world, there can be no duplicate role names, there could not also be “an example of Internal Organization Class”, or some such—even though the total meaning of the predicate is not duplicated. Here is another place where the architectural entity/relationship modeler must part company from the object-oriented designer.A bunch of words dreamed up by the utterly deranged