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

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

    Seems kinda weird to me. It’s completely legit to ask for documentation before making it yourself. Some people are just more visual and need to see diagrams - they certainly help me.

    That being said, I haven’t used formal UML in twenty five of professional development. I mostly use class diagrams and flow diagrams. Could be he was reacting to something that he feels is more academic and less practical.

  • Kissaki@feddit.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    This is such a broad question. It’s normal and not normal to do so, it’s also normal not to do so.

    If it turns out / becomes evident you need a diagram now now’s the time to create one. You may push quality even without seeing the value in it. In some places or with some people it may be unwanted.

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

    As others said, in-depth design is often skipped, especially if the dev team started very small. Sounds like your intuition is right, though - the lack of design bit them on the ass when they realized they missed a part.

    I have also been laughed at when I suggested a UML diagram in the past. However, it is helpful. For more visually oriented people even more so.

    I’d suggest to go ahead and do it, unless your boss is adamant that it is a waste of time. When they see the result they might be happy.