TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Numbers to Know for Managing (Software Teams)

54 pointsby _njuyabout 2 years ago

5 comments

cntainerabout 2 years ago
<i>500 - the number of employees before your CEO becomes a political figure</i><p><i>1000 - the size of company when you’re at risk of losing accountability</i><p>From my own experience and other sources (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35206141" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35206141</a>) those numbers seem too high. I&#x27;ve seen this happen 2 times in front of my eyes while both companies were in the 100-200 range.<p>One of them managed to go to the next level and adapt to the new reality the other is still struggling.
评论 #35266044 未加载
sponaugleabout 2 years ago
These numbers are probably the least valuable numbers you will see on Hacker News today. Almost every one is an exception to an anecdote, and an anecdote with exceptions.<p>Things like &quot;90 - the number of days a role should stay open 90 days is the industry standard time-to-hire metric.&quot;<p>So is 90 days the average in this industry? Do you want to be average? Is it really your goal to do things they same way all of your competitors do? A role should stay open EXACTLY as long as it needs to. Putting artificial numbers in front of it and acting like there is some magic &#x27;best practice&#x27; is ridiculous. There may be some jobs that take longer, and some that take much much less. The last thing you need to do is sit around answering questions like &quot;Why is this taking longer than the industry standard?&quot;.<p>If you really need to manage by following a list of &#x27;numbers&#x27; you are a fantastic illustration of why there can be so much differentiation among companies. Great companies can build great successes on the back of thoughtless process.
glonqabout 2 years ago
40 - The number of hours per week that you should &quot;expect&quot; people to work.<p>You can <i>hope</i> or <i>inspire</i> or <i>ask</i> for more. But don&#x27;t expect it. And don&#x27;t take it for granted.
nobodyandproudabout 2 years ago
I’m wincing at each number. I’ve been a manager for 4 years, and I think I’ve done worse and not better as my team doubled&#x2F;tripled in size.
评论 #35260130 未加载
ludovicianulabout 2 years ago
On a tangential note I&#x27;ve also asked here (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35245329" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35245329</a>) what will be some performance indicators to take into consideration when delivering software. That &#x27;50 PRs in 6 months&#x27; is interesting. You might argue that &quot;it&#x27;s important to deliver business value&quot; and &quot;as long as your hitting your market&#x2F;business capabilities targets&quot; everyone is happy. But my question is still: &quot;how do you know you are being efficient? can you still deliver with half the number of people?&quot;.
评论 #35260165 未加载