News for hackers. Stuff that matters.
Re:How my role as CTO has changed as we've grown from 1 to 1... by yarper on Thursday June 28, 2018 @04:43PM (#17420325)
At what point do you start calling people direct reports? I find this turn of phrase really jarring
Re:How my role as CTO has changed as we've grown from 1 to 1... by jp_sc on Thursday June 28, 2018 @04:56PM (#17420425)
When you are managing people that manage other people, so not everyone _direct_ly reports to you.
Re:How my role as CTO has changed as we've grown from 1 to 1... by stronglikedan on Thursday June 28, 2018 @04:54PM (#17420405)
Reporting hierarchy is there for a good reason. If you report to multiple people, you're the one that's going to have a bad time when they're not aligned with each other, each trying to give you a different list of priorities.
Re:How my role as CTO has changed as we've grown from 1 to 1... by yarper on Thursday June 28, 2018 @05:16PM (#17420549)
Why don't they know what's important and what's not?
Re:How my role as CTO has changed as we've grown from 1 to 1... by jcheng on Thursday June 28, 2018 @07:24PM (#17421293)
In a larger organization, "knowing what's important and what's not" at all times can be practically a full time job in and of itself. A lot of engineering teams like to protect individual developers from meetings and conference calls so they can focus on development, but that necessarily means developers will be missing context.
Re:How my role as CTO has changed as we've grown from 1 to 1... by shawn on Thursday June 28, 2018 @04:49PM (#17420365)
Why does it feel jarring?
Re:How my role as CTO has changed as we've grown from 1 to 1... by yarper on Thursday June 28, 2018 @05:05PM (#17420482)
I think it's because it implies that their job is to report to you -like you're really the brains of the operation rather than just in a different role