piannaf’s avatarpiannaf’s Twitter Archive—№ 3,924

                1. Structural Lessons in Engineering Management elidedbranches.com/2022/01/structural-lessons-in-engineering.html
              1. …in reply to @piannaf
                "You end up spending an outsized amount of time on management tasks when your direct team size grows much beyond this number [7–8 direct reports]; or, even worse, you just start doing a bad job at those management tasks because you don’t have the time to do them well."
            1. …in reply to @piannaf
              "Managers don’t just drift between teams depending on the immediate size of the organization, they have skills and interests that make them sticky to their group."
          1. …in reply to @piannaf
            "the idea that team interactions can be strictly defined by an API is as laughable as the idea that programmers won’t figure out a way to exploit every undocumented feature you provide in one"
        1. …in reply to @piannaf
          "While I agree that there is value to organizing your teams effectively, the marginal value that the teams might experience is likely to be offset by the unintentional friction that happens for the people who don’t fit perfectly into your structure"
      1. …in reply to @piannaf
        "if you don’t create growth opportunities or appropriate technical challenges even though it’s not the most optimal thing for the system as it currently exists, you will find yourself losing good engineers and managers"
    1. …in reply to @piannaf
      "it becomes important to accept that you may hang out in imperfect structures for many months or even longer, because you are trying to hang onto people for years."
  1. …in reply to @piannaf
    "don’t be afraid to break your perfect structures to accommodate their needs. They are your best source of learning, and your most valuable asset."