News for hackers. Stuff that matters.
Re:Review of the .nz DNSSEC Chain Validation Incident on 29-... by tgv on Monday October 09, 2023 @05:22AM (#37818553)
> - Engagement surveys captured staff feeling fatigued and under resources at entire org level

This smells like an organizational failure. First, the survey doesn't tell if the tech staff suffered fatigue, because it was organization-wide. Second, the Executive Leadership Team has 5 people. Just the executive leadership. The Council itself has 9 members. I shudder to think how many (indirect) managers the 4 tech staff has to report to. Third, if there is a problem in your organization, you won't find it with a bloody survey. Those just exist to satisfy KPIs. Fourth, if there is a problem in a small team, that is fairly easy to locate. but if their manager doesn't know, or can't change it, something is wrong in the organization. Fifth, if there is a problem in a critical team, the organization as a whole has failed.

This won't be solved by outsourcing. If anything, placing critical employees at a distance creates more problems than it solves.

Re:Review of the .nz DNSSEC Chain Validation Incident on 29-... by martinald on Tuesday October 10, 2023 @04:22AM (#37829689)
Agreed. Over the past few years I've encountered more and more organisations with a ratio of management:developer/designer of >1, ie for every developer or designer, there is more than 1 "manager" (PM, EM, etc) involved. These organisations tend to have appalling velocity and very low developer morale.

Conversely some of the most efficient organisations I've seen have virtually no "management". Usually a lead developer who still works on the product managing tickets, taking requirements from a CEO or similar. These teams can deliver a mind boggling amount of work in comparison.