• NigelFrobisher@aussie.zone
    link
    fedilink
    arrow-up
    7
    arrow-down
    4
    ·
    9 hours ago

    Cloud Architect means you tell the developers to use the services provided by your company’s cloud vendor for their intended purpose. It’s a vital role.

  • fubarx@lemmy.world
    link
    fedilink
    arrow-up
    105
    ·
    1 day ago

    It actually is pretty incredible. You get paid to draw boxes with icons, and arrows connecting them.

    • Prox@lemmy.world
      link
      fedilink
      arrow-up
      64
      ·
      1 day ago

      And you don’t even have to actually build the thing you drew! That’s someone else’s problem.

      • jaybone@lemmy.zip
        link
        fedilink
        English
        arrow-up
        7
        ·
        21 hours ago

        Not always. In some cases you create little prototypes or examples or partial implementations of various components, and then hand those off to the person or persons who will do the full implementation.

        And then they will completely fuck it up because they didn’t want to follow your example and/or they don’t know how to read or communicate. And then you have to go and debug their stupid bullshit.

        • Aceticon@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          9 hours ago

          And then they will completely fuck it up because they didn’t want to follow your example and/or they don’t know how to read or communicate. And then you have to go and debug their stupid bullshit.

          Alternativelly and having had the software architect responsability myself and also been on the other side, they fuck it up because they didn’t know how to properly communicate with people who can’t read their fucking mind, they didn’t do a specification with the smallest possible number of insufficiently defined elements and they did not maintain open communication with the implementation team for the invariable parts of the specification that turn out to not have been defined with enough depth or collide with the reality of what’s possible.

          IMHO, ultimatelly is the responsability of the senior person to figure out how much hand-holding the implementation team needs and adjust to them, rather than expect that for example a bunch of Junior Developers can just get a specification that consists a bunch of examples (or the other equally bad format for them: the massive wall of boring text) and not fuck it up.

          In my own career I’ve seen far more people with Technical Architecture responsabilities (and even the title) that did not know what the fuck they were doing, than seen Junior and Mid level Developers that were below what is expected of somebody at that level of their career.

        • ButtDrugs@lemm.ee
          link
          fedilink
          arrow-up
          6
          ·
          16 hours ago

          This guy architects. You also get to a spend a lot of time explaining to non technical folks why their ideas are bad or expensive to build. Lots of being the bad guy.

      • vane@lemmy.world
        link
        fedilink
        arrow-up
        15
        ·
        1 day ago

        And people who build it just flush it to the toilet because requirements are different.