dogear

enter for all results · esc to close

Engineering Team Management

363 items from kdeldycke/awesome-engineering-team-management ★2,615

  1. Dear Manager, You're Holding Too Many Meetings archive.ph

    “Employee productivity was 71% higher when meetings were reduced by 40%. This is largely because employees felt more empowered and autonomous. Rather than a schedule being the boss, they owned their to-do lists and held themselves accountable.”

  2. What do executives do, anyway? apenwarr.ca

    Paraphrasing Andy Grove's book, High Output Management, “the job of an executive is: to define and enforce culture and values for their whole organization, and to ratify good decisions.” The article also details the failures modes of a CEO: forcing his own decisions downstream…

  3. Meeting everyone on a new team annashipman.co.uk

    Right after inheriting a position at the top of an organization of 50 engineers, the author bootstrapped the relationship with that big team by meeting everyone in 30 minutes 1:1s. It was a huge time investment, and despite fears of being boring, it allows for recognizing…

  4. BLUF: The Military Standard That Can Make Your Writing More Powerful animalz.co

    “BLUF is a military communications acronym—it stands for “bottom line up front”—that's designed to enforce speed and clarity in reports and emails.”

  5. How I operated as a Staff engineer at Heroku amyunger.com

    A great window into the somewhat nebulous title of Staff Engineer, also called Principal Engineer or Software Architect at times. I.e. a role in which you are a technical expert, but know how to solve non-obvious engineering issues, most of the time because they are rooted in…

  6. The Framing of the Developer amazingcto.com

    Default framing is around the backlog, which leads to an asymmetry in which failure is blamed on lacks of developer performance, and success is celebrated as the full realization of the PM's vision. But “technology is the bank that gave credit”, and technical debt should be…

  7. There Are No Bugs, Just TODOs almad.blog

    Issue trackers needs to materialize ownership, queue position, state, task breakdown and aggressive closing. Priority, ticket type, software version, severity and long-life tickets are anti-patterns.

  8. It's time to start writing alexnixon.github.io

    On “Jeff Bezos's dotcom-era policy of banning PowerPoint within Amazon”, and how “this is neither about powerpoint nor about reading - it's about thinking.”

  9. source accu.org

    ) - This quote is from a review of Superdistribution - Objects as Property on the Electronic Frontier, in which the creator of Objective-C was advocating in the 90's for a new economic framework that rewards creation of components in proportion to their use. But software…

  10. GitLab's Guide to All-Remote about.gitlab.com

    “GitLab is the world's largest all-remote company”. Here is what it means and how it works.

    site link ↗