• nxdefiant@startrek.website
      link
      fedilink
      arrow-up
      0
      ·
      2 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?

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 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.

    • 9point6@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 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?

      • krashmo@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        2 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.

  • model_tar_gz@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 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.

    • Skullgrid@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      Ex test lead, this 100%.

      My job was to organise the work between the workers, keep the business away from my subordinates, and only waste their time when they had the complete information being asked for the specific reason.

      And if I wasn’t doing one of the things above, my job was to pick up the horrible things that no one else wanted/I had experience and domain knowledge in (eg : accessibility testing)