• Aceticon@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    The good ones: design and adjust software development processes, standards for cross-project functionality and reusability and in general try and improve at a high level the process of making, maintaining and improving software in a company.

    The bad ones: junior/mid-level software design with a thick layer of bullshit on top to spin it as advanced stuff.

    If you want to see bad software architecture, just look at most of Google’s frameworks and libraries.