dogear

enter for all results · esc to close

the #1 bug predictor is not technical, it's organizational complexity

augustl.comsite

.

from
Engineering Team Management
added
2026-10-10
likes
0

similar

  1. Best project management practices in 2018? news.ycombinator.com

    There is no silver bullet.

  2. 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.”

  3. Technical debt as a lack of understanding daverupert.com

    “The problem lies in "never reorganizing (the code) to reflect your understanding." (…) Organizationally, you pay in velocity and turnover; talented people are going to leave after a few rounds of bullshit.”

    site link ↗
  4. Developers spend most of their time figuring the system out lepiter.io

    “A hand drawn picture about the current system is a belief. Decisions should never be based on beliefs. Not in engineering. (…) As software is highly contextual we cannot predict specific problems. We can only predict classes of problems.” And that's why it is hard to estimate…

  5. source news.ycombinator.com

    ), or why the key practices for achieving large professional goals is missing the parts about office politics.

  6. comment news.ycombinator.com

    on Why large companies are so difficult to rescue).

Engineering Team Management › Product Management > Product Strategy: “.”