dogear

enter for all results · esc to close

Engineering Team Management

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

  1. Work at different management levels larahogan.me

    A great progressive breakup of what it feels like to work at different levels of management.

  2. Manager Energy Drain larahogan.me

    “How do I handle how tired I am as a manager? 1. Defrag your calendar; 2. Delegate messy and unscoped projects; 3. Say no.”

  3. Questions for our first 1:1 larahogan.me

    A personal list of high-level questions from a manager.

  4. Dear Startup: You have no idea how much that costs kyleprifogle.com

    “We are completely clueless about how long things should take.” Here is a trick to handle expectation of unreasonable estimates.

  5. The Good, the Bad and the Ugly Standup kristoff.it

    Author experienced 3 formats of stand-ups before ending with one working for his team, and concludes that “the details that make up a good meeting are subtle and the pursuit of an artificial standard of aesthetics will prevent you from doing the necessary experimentation to…

  6. Managing Remote Teams - A Crash Course klinger.io

    Compilation of easy rules and processes to bootstrap a remote team.

  7. On Being A Senior Engineer kitchensoap.com

    “I expect a 'senior' engineer to be a mature engineer.”

    site link ↗
  8. Culture Queries keyvalues.com

    A sample of question to ask in job interviews to try to understand the values of a company.

    site link ↗
  9. UX Core keepsimple.io

    105 cognitive biases with simple descriptions, brief and detailed examples.

  10. Rethinking the Hiring Process karllhughes.com

    “Testing programmers at something they aren't actually expected to be good at and expecting to learn something about how they would work at your company is delusional, and I think these kind of interviews only serve to make the hiring team feel smarter and ensure better…

  11. Salary Negotiation: Make More Money, Be More Valued kalzumeus.com

    “Your salary negotiation — which routinely takes less than 5 minutes to conclude — has an outsized influence on what your compensation is.”

    site link ↗
  12. Get your work recognized: write a brag document jvns.ca

    There's this idea that, if you do great work at your job, people will (or should!) automatically recognize that work and reward you for it with promotions / increased pay. In practice, it's often more complicated than that.

  13. When your coworker does great work, tell their manager jvns.ca

    Highlighting unseen work in public allows managers to recognize efforts their reports are doing. Still, there is some cases in which it might put your colleague in a tight spot. So always ask if it's ok first.

    site link ↗
  14. Noise, Cognitive Function, and Worker Productivity joshuatdean.com

    “An increase of 10 dB reduces productivity by approximately 5%.”

  15. LEGO blocks and organ transplants johndcook.com

    “People have been comparing software components to LEGO blocks for a couple decades. (…) Integrating two software systems is usually more like performing a heart transplant than snapping together LEGO blocks.”

  16. Incentive Pay Considered Harmful joelonsoftware.com

    “Incentives (or bribes) simply can't work in the workplace. (…) Most software managers have no choice but to go along with performance review systems that are already in place. If you're in this position, the only way to prevent teamicide is to simply give everyone on your team…

  17. A high-resilience org chart jessitron.com

    “If you know what problem you're solving and you know how to solve it, a bureaucratic organization will do. Stick with what you know. If you're writing software, that's a generative activity. You need a high-resilience org chart. Fewer boxes, more flexibility.”

  18. Failed #SquadGoals - Spotify doesn't use "the Spotify model" and neither should you jeremiahlee.com

    “Why it didn't work? 1. Matrix management solved the wrong problem; 2. It fixated on team autonomy; 3. Collaboration was an assumed competency; 4. Mythology became difficult to change”.

    site link ↗
  19. Why it's difficult to build teams in high growth organisations jchyip.medium.com

    Describes 3 different approach a manager can take to accommodate new people in the team: 1. Sink or Swim; 2. Split and Absorb; 3. Absorb and Split.

  20. My questions for prospective employers (Director/VP roles) jacobian.org

    Be prepared to ask them as a recruiter or being asked about them for senior management roles.

    site link ↗
  21. CTO vs VP Engineering: What's the Difference? ivyexec.com

    CTO manage a small staff of hackers. VP of Engineering lead an organization of engineers.

    site link ↗
  22. Programmer Moneyball: Challenging the Myth of Individual Programmer Productivity insights.sei.cmu.edu

    “Since software project managers have limited ability to evaluate individual developer capability, they should rely on a productive environment and developing talent.”

  23. Do engineering managers need to be technical? increment.com

    Yes. “Looking forward to the next 30 years of management trends, only a few things seem certain: Managers should be technical, and the definition of technical will continue to change.”

    site link ↗
  24. A guide to distributed teams increment.com

    A nice wrap up on the numerous dispositions required to have a highly effective distributed team.

  25. Developers can't fix bad management iism.org

    “Why do so many software projects fail? Software development is much closer to creating a new factory than running an existing factory. (…) Software development is made up of many unknown duration tasks, this fundamentally unpredictable nature makes traditional management's…

  26. Power Bends Light honkathon.com

    “Most things at most startups are perpetually on fire, but if you can accept that, there is a lot to like. One well-known one: at a fast-growing startup, a hard-working, talented person who has some support from company leadership can often acquire an impressive title (or at…

  27. Job Interviewing Guide homerun.co

    A detailed description of a hiring process, a great source of inspiration for when your company gets big enough to start to formalize things up.

  28. Fundamentals of Product-Market Fit holloway.com

    A complete overview of the concept: what is product-market fit and to measuring it.

  29. Equity Compensation holloway.com

    Stock options, RSUs, job offers, and taxes—a detailed reference, including hundreds of resources, explained from the ground up and made to be improved over time.

  30. Ten Rules for Negotiating a Job Offer haseebq.com

    “First part will be about conceptualizing the negotiating process, about how to begin the process and set yourself up for maximal success. The second part will be advice on the actual back-and-forth portion of negotiating and how to ask for what you want.”

    site link ↗
  31. How Not to Bomb Your Offer Negotiation haseebq.com

    “A good negotiator is empathetic and collaborative. They don't try to control you or issue ultimatums. Rather, they try to think creatively about how to fulfill both your and their needs.”

    site link ↗
  32. Laws of Tech: Commoditize Your Complement gwern.net

    A step further from the previous advice, in which is detailed an aggressive strategy to consolidate monopolies.

  33. Narcissistic CEOs Weaken Collaboration and Integrity gsb.stanford.edu

    “The prototypic visionary leader profile is so similar to that of a narcissist, if boards aren't careful, they're going to end up choosing people who are narcissistic as CEOs”.

    site link ↗
  34. The Psychology of Design growth.design

    An extensive list of cognitive biases and design principles with examples and tips to fine-tune your product and UX.

  35. Google Engineering Practices google.github.io

    Explains how to perform code reviews and how to submit them.

  36. Paper we love: Software Engineering Organizations github.com

    “The practice of software engineering, and its history is, itself, a complex study in humanity, coordination, and communication.”

  37. How to exit vim, the Product Manager way github.com

    A satire with a grain of truth, especially the comparison between the basic vs experienced level.

  38. Code reviews at Google github.com

    “Why Should Code Reviews Be Fast? (…) To optimize for the speed at which a team of developers can produce a product together, as opposed to optimizing for the speed at which an individual developer can write code.”

  39. The 4 Worst Software Metrics Agitating Developers in 2019 gitclear.com

    The worst KPIs to track a software team output: Lines of Code, Commit Count, Issues Resolved (aka “Shipping Velocity”) and Code Churn (aka "Efficiency").

  40. How to be a Manager – A step-by-step guide to leading a team getweeklyupdate.com

    A full, detailed guide on modern management practices.

  41. The Best Way to Make Intelligent Decisions fs.blog

    A collection of 109 models.

  42. Gigerenzer's simple rules foundingfuel.com

    The reason we often relies on these simple heuristics: “outside the lab, in real world, we cannot do well with just with logical rationality, we need ecological rationality - the kind of thinking that helps us get what we want in an environment that's uncertain and dynamic…

    site link ↗
  43. Flying Circus Platform - Disaster recovery flyingcircus.io

    Critical infrastructure which aims to be available 24/7 needs a Disaster Recovery Plan. It generally takes the form of a document providing an overview of the expected severe failures and a set of procedures on how the system and the team operating it is prepared to deal with…

    site link ↗
  44. The Efficiency-Destroying Magic of Tidying Up flocrivello.com

    “Efficiency tends to look messy, and good looks tend to be inefficient.” A reminder that sometimes we should just accept the messiness of the world.

    site link ↗
  45. Army Leadership and the Profession fas.org

    Establishes and describes what leaders should be and do.

    site link ↗
  46. What Makes A Great Software Engineer? faculty.washington.edu

    Doesn't conclude on a definitive answer to the question, but details a model based on 53 attributes (!). Still a good source referencing other papers on the topic.

  47. HiPPO FAQ exp-platform.com

    HiPPO stands for “Highest Paid Person's Opinion”, a trait of dysfunctional culture, in which power politics trumps data.

    site link ↗
  48. Building a data team at a mid-stage startup: a short story erikbern.com

    Story of a manager trying to distill the concepts of a data-driven company while growing a tiny team of 3 people. Each step covers the evolution of the technical pipeline and interactions with existing stakeholders.

  49. next page of items loading…