Yikes, that open office picture looks like my nightmares.
How my role as CTO has changed as we've grown from 1 to 100 engineers
101–110 of 142 posts
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#102Earlier quoted context omitted.
The reason why your advice is not as useful as you think is because chances are, if you google around, most of that lesson would be already out there. Don't take this the wrong way I mean no offense. I'm sure you've learned a lot of lessons and I'm sure they're all valuable lessons, just saying most of what I read online nowadays are basically rehash of what these failed entrepreneurs heard from someone else, who pro…
"The reason why your advice is not as useful as you think is because chances are, if you google around, most of that lesson would be already out there. Don't take this the wrong way I mean no offense. I'm sure you've learned a lot of lessons and I'm sure they're all valuable lessons, just saying most of what I read online nowadays are basically rehash of what these failed entrepreneurs heard from someone else, who pr…
Also, "You're wrong" is not such a mature way to engage in a conversation, and yet that's exactly how you start every comment you posted here. Could have been a productive conversation if you acted maturely.
And even though I said no offense and clearly meant it in a generic manner (and not attacking YOU), you actually sound very offended. Why are you so offended by some random guy on the Internet?
But I guess I'll never get an answer, since you're probably a man of your words and keep your promise to keep that last comment your last post :)
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#103Earlier quoted context omitted.
That would be great, but there's a structural limit: people running successful startups don't have time to write about it, while people who have wound down their companies do. When a company is going strong and HN sees a post like this, it's usually because they're hiring :)
>>people running successful startups don't have time to write about it This is both offensive and incorrect. Offensive because it implies that if someone manages to find the time to write about how they are running their company they probably aren’t successful. Incorrect because the startup world is in fact full of leaders who do manage to find the time to write about how they run their companies (kalzameus comes to…
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#104Earlier quoted context omitted.
That would be great, but there's a structural limit: people running successful startups don't have time to write about it, while people who have wound down their companies do. When a company is going strong and HN sees a post like this, it's usually because they're hiring :)
That's a bizarre claim. Writing about the company is one of the big PR tasks of a CxO or SVP. As you noted yourself, blogging is a form of marketing.
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#105Earlier quoted context omitted.
That would be great, but there's a structural limit: people running successful startups don't have time to write about it, while people who have wound down their companies do. When a company is going strong and HN sees a post like this, it's usually because they're hiring :)
That's a bizarre claim. Writing about the company is one of the big PR tasks of a CxO or SVP. As you noted yourself, blogging is a form of marketing.
I spend a lot of time giving feedback to people about how to appeal to HN's audience. Authors tend to be founders only for very-early-stage startups, such as the ones you see in Launch HNs. The authors from larger companies tend not to be founders or even execs. My sample is biased, of course, but if founders and execs of successful startups were writing informative articles about how they run their startups, readers here would be interested and we'd surely see them posted.
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#106Earlier quoted context omitted.
That's a bizarre claim. Writing about the company is one of the big PR tasks of a CxO or SVP. As you noted yourself, blogging is a form of marketing.
Absolutely. If a going concern can't make time for blogging and other similar ventures, they're not staffed appropriately for their success!
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#107it's refreshing to see someone who actually successfully scaled a company write an article about "here's how we did it", instead of bunch of failed entrepreneurs who write medium posts about why they think their startups failed to either feel better about themselves or to capitalize on their failure with the attention they get from the blog post (answer: they don't know why they feailed, and that's why they failed. T…
That would be great, but there's a structural limit: people running successful startups don't have time to write about it, while people who have wound down their companies do. When a company is going strong and HN sees a post like this, it's usually because they're hiring :)
Aren’t you kind of the one lowering it?
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#108Earlier quoted context omitted.
That would be great, but there's a structural limit: people running successful startups don't have time to write about it, while people who have wound down their companies do. When a company is going strong and HN sees a post like this, it's usually because they're hiring :)
https://news.ycombinator.com/item?id=17420230 Aren’t you kind of the one lowering it?
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#109Earlier quoted context omitted.
Absolutely. If a going concern can't make time for blogging and other similar ventures, they're not staffed appropriately for their success!
That's a pretty stupid claim.
Re: How my role as CTO has changed as we've grown from 1 to 100 engineers
#110This surprised me at first: > having difficult conversations with individuals is never fun But apparently "difficult conversations" is a Valley euphemism for "firing people" and doesn't mean "discussing difficult engineering problems".