• model_tar_gz@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    8 months ago

    No, this is incompetent management.

    Senior engineers write enabling code/scaffolding, and review code, and mentor juniors. They also write feature code.

    Lead engineers code and lead dev teams.

    Principal engineers code, and talk about tech in meetings.

    Senior Principal engineers, and distinguished technologists/fellows talk about tech, and maybe sometimes code.

    Good managers go to meetings and shield the engineers from the stream of exec corporate bs. Infrequently they may rope any of the engineers in this chain in to explain the decisions that the engineers make along the way.

    Bad managers bring engineers in to these meetings frequently.

    Terrible managers make the engineering decisions and push those to the engineers.

      • model_tar_gz@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        I’ve worked for startups too; everyone does everything all at the same time! Let the chaos reign! But it is fun in its own way.

        I work for a large company now after the startup I worked for was acquired. Hierarchy, bureaucracy, layers, we’ve got it all. For worse and for better though, it allows me to focus and specialize on what I’m awesome at and furgeddaboddit (ahem! delegate) the stuff that I suck at to those who excel at those tasks.

    • Aceticon@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      8 months ago

      I came here to say the same.

      People in the technical career track spend most of their time making software, one way or another (there comes a point were you’re doing more preparation to code than actual coding).

      As soon as you jump into the management career track it’s mostly meetings to report the team’s progress to upper management, even if you’re supposedly “technically oriented”.

      Absolutelly, as you become a more senior tech things become more and more about figuring out what needs to be done at higher and higher levels (i.e. systems design, software development process design) which results in needing to interact with more and more stakeholders (your whole team, other teams, end users, management) hence more meetings, but you still get to do lots of coding or at least code-adjacent stuff (i.e. design).

    • evatronic@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      There is a reason I keep refusing to take the “Lead” position. I know what I’m good at.

      • xor@infosec.pub
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        8 months ago

        Now I don’t know, but I been told
        It’s hard to run with the weight of gold
        Other hand I have heard it said
        It’s just as hard with the weight of lead…

    • 0x0@programming.devOP
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      Good managers go to meetings and shield the engineers from the stream of exec corporate bs

      Was lucky enough to work with one… once.

  • Nomecks@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I knew I finally made it to a senior role when I started to do nothing but paperwork.

    • RGB3x3@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      I work in the government and I honestly don’t know when anyone does any real work. It’s meeting after meeting overlapping other meetings. All week.

      How does stuff get done, seriously?

  • penquin@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I just got a Jr dev job about 3 weeks ago and I haven’t written a single line of code. It’s all been meetings and other shit. I’m kind of ok with that. Lol

    • smeg@feddit.uk
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      I think this is something a lot of people posting here don’t get. You can be a programmer, make apps or games in your spare time, set your own goals and be your own boss, and that’s great. Suddenly you get a “normal” job programming and you have you deal with customer requirements, business nonsense, and working as part of a team; that’s being a software engineer. One isn’t superior to the other, they are just different beasts.

      • penquin@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        Absolutely. There is very little programming involved in a normal job most of the year. I actually knew that before getting in. I have friends on the same team that have been there before me and they explained things beforehand. I have so many meetings and business stuff daily. We also reach out to users to help them fix issues on their machines, too.

    • nxdefiant@startrek.website
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      Have you considered writing your own projects that you have to hide from your employers, and be careful with whom you discuss, so as to avoid the legal complications of the company owning your work?

  • Alien Nathan Edward@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    not my experience at all across 3 separate companies. Ime senior engineers are the highest level that still spends most of the day heads down most days, and that’s why I’m gonna stick it out at this level as long as I can.

  • chiliedogg@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I work on the City side of the development world. We’re always getting screamed at for taking 3 weeks to review a plan set by the same developers who want to meet with me every minute of every fucking day.

    I’ve got 40 projects in my review queue and all of them are demanding a weekly meeting. When am I supposed to do the fucking reviews?

    • slazer2au@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      When you talk to your management and show them how overworked you are and ask for a helper. But don’t just say how much, show them in business lingo so they actually understand.

      Fill out your calendar with the meetings and show management how you have no time for meaningful work because of meetings.

      • chiliedogg@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        I’m on the Municipal side. City Council ain’t gonna raise taxes to hire more people.

        I’ll get burned out and leave soon enough. The longest-serving person in the development department has been here just over a year, and we pay nearly double what other cities in the area do.

  • 1984@lemmy.today
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I worked in places like this and I’m not going back unless consulting prices go back up again… The pain is real.

    • wizardbeard@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      Just find a place that hasn’t solidified their IT structure and processes enough for people to have time to invent BS overhead.

      THE STANDARD PRACTICE IS WHATEVER I SAY IT IS JANICE! how are business critical things no one knew existed breaking

  • Klanky@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    This is not the first time I’ve seen memes like this, and it makes me so glad I’m not involved in programming or software development. I would straight up die.

  • xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    Talk to your manager, they’re really fucking failing to support you. When I was a senior data architect I had about two hours of meetings a day.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    0900 till 0930 - 15 min standup meeting.
    0930 till 1000 - focus time.
    1000 till 1100 - Pre meeting for customer meeting at 1100.
    1100 till 1200 - Customer meeting.
    1230 till 1300 - Post Meeting catchup.
    1300 till 1330 - focus time.
    1330 till 1430 - JIRA board update meeting.
    1430 till 1500 - priorities review meeting.
    1500 till 1645 - focus time.
    1645 till 1730 - EOD standup.

    • AlternatePersonMan@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      “Are you don’t yet? Why aren’t you done yet? Help me update infinite plans that will be outdated in a week. Also, I just promised a bunch of stuff… all that stuff we already promised, I think you can do that faster.”

      When I was a dev, I once had a PM with no technical skills that decided he would “learn to program to help catch us up”… He did not succeed.

      • krashmo@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        Hey, at least he had the right idea. He saw that the delay was due to a lack of skilled workers and tried to fix that problem instead of just talking more about the project. That’s more awareness than most PMs have in my experience.

        • KevonLooney@lemm.ee
          link
          fedilink
          arrow-up
          0
          ·
          8 months ago

          PMs act that way because people above them ask for updates regularly. Bad PMs don’t know how to push back. If you need things done faster, the answer is usually “we need more resources”.

          • SolarMech@slrpnk.net
            link
            fedilink
            arrow-up
            0
            ·
            8 months ago

            “we need more resources” is bounded by the rate at which you can incorporate new teams members without absolutely destroying your productivity, or having a bunch of untrained fools running around breaking things (of course the later is standard at many places already, so I guess it doesn’t always matter).

            The right answer is usually : “No”. Or at least “Prioritize”. Or “This is what we need to get it done” at which point they might start to get software takes time to make decently, and they don’t want software that doesn’t work decently in the first place.

            • Aceticon@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              8 months ago

              “Sure! You just have to choose which of these other things you want deprioritized since we’re already going at full tilt”

        • Maalus@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          8 months ago

          If a PM has enough time to try to learn programming on the side, then they are a shit PM. A PM should shield the team from unneccessary meetings, be the main initial contact point and the initial refinement guy. Those are 4 seperate jobs at once.

    • EatATaco@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      We do standups twice a week. At worst they run a half hour for my team of about 10 people. Usually we’re done in 15-20 minutes. Please tell me it’s just an absolutely made up joke that you have an hour and 15 minutes of stand up meetings every day. I would shoot myself.

      • slazer2au@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 months ago

        Don’t worry mate, it is a joke. But judging by the other comments it is closer to reality than a joke for some.

      • Daxtron2@startrek.website
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        I had a job that had > 1hr standups for our two man project because we met with QA, BA, and management and they wanted everything changed every day so we had to explain why we couldn’t do anything with constantly changing requirements every morning.

    • 9point6@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      You get focus time?

      Also, what the hell is the point in an EOD standup if you’re gonna have another one in zero working minutes?

      • bamboo@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        Because even if you’re not working, you’ll probably think about problems overnight

        • 9point6@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          8 months ago

          So what’s the point of the EOD one?

          I honestly see zero benefit in it unless it’s a 24h operation with a shift handover.

          • MNByChoice@midwest.social
            link
            fedilink
            arrow-up
            0
            ·
            8 months ago

            I hate to defend the EoD standup, but some people forget everything overnight. The only way to know what they did is to ask before the rest.

            Yes, they truly are amazing. Yes, everyone should not be punished.

            Mostly, it it to keep people from going home early. As such is indefensible.

            • poinck@lemm.ee
              link
              fedilink
              arrow-up
              0
              ·
              8 months ago

              “I cannot attend EOD daily today, I have to get the kids from school early.”

      • poVoq@slrpnk.net
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        8 months ago

        You get focus time?

        They need to give you some time to answer emails from management 🙄

      • krashmo@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        8 months ago

        That concept is lost on so many people and I don’t understand why. One of the last teams I was on had two weekly meetings. One was 9:00 AM Monday morning and the other was 4:00 PM on Fridays. They were both running through all of our projects and always seemed surprised that the Monday update was the same as the previous Friday update.

        • OpenStars@startrek.website
          link
          fedilink
          English
          arrow-up
          0
          ·
          8 months ago

          It is to their advantage to be act surprised, therefore they are “surprised”, see? This was your “opportunity” to show how dedicated you are the company, having worked all weekend long…

          • KevonLooney@lemm.ee
            link
            fedilink
            arrow-up
            0
            ·
            8 months ago

            It isn’t particularly hard to call this out. Just say “I haven’t done anything since Friday.” And leave it at that.

            Be comfortable with silence.