The other day I asked for an analysis or at least an UML diagram since we are having quite some troubles and my boss looked disgusted at me for asking such a question. I’m not a professional backend developer, so I don’t know how it works professionally

  • atheken@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I haven’t made a UML diagram in years. Or an ER diagram, for that matter.

    Getting a schema dump and/or generating a diagram from an existing system would be useful, it won’t be UML, but can convey similar information. At a certain point, keeping an updated UML diagram is extra work that is almost guaranteed to go out of data instantly.

    • nitefox@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Yeah but knowing why something was made in that way would greatly help. The problem here is, the design is unreliable (just today we found an error in the design which changed an INSERT to a simple SELECT) so if we knew why certain things were made that way it would make our job much easier (in the end we have to ask if something weird was meant that way or it’s a design error)

      • atheken@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        I have no idea what you mean when you say you found an error in the design that says it was an INSERT instead of a SELECT.

        If you are relying on a design doc with SQL in it, that’s a massive waste of time.

        How many tables are in the schema? Have you reviewed them? Are there any naming conventions being followed, or is everything inconsistently named? Are there specific cases where tables are not normalized properly that you can ask specific questions about why they are that way? If the person that designed the schema is making “trivial” mistakes, there’s no reason to expect that stuff that doesn’t make sense to you will be something they intentionally did.

        I guess what I’m saying is, you need to do some due diligence and survey the schema and write down some specific questions and that may lead to writing a UML or other doc to identify errors, but it doesn’t sound like you’ve done that.