Live data from Hacker News

Resources for chief technology officers, with the emphasis on startups

github.com

1–10 of 59 posts

Re: Resources for chief technology officers, with the emphasis on startups

#2
My biggest challenge as a CTO is that, by nature, I'm singular in focus. If I am developing something I find it hard to context switch and review other developers' work. The best strategy I have found so far is to block certain times in the week solely for reviewing everyone's progress.

Re: Resources for chief technology officers, with the emphasis on startups

#5
I like that it's short and somewhat curated, try to make it stay that way. Most awesome lists grow to be link dumps. For instance the awesome-js is over thousands lines long now, containing all sorts of random crap. It can be nice as a way to know what's out there, but when it contains 40 mvc alternatives in addition to react/angular and other big ones, it's just not useful.

Re: Resources for chief technology officers, with the emphasis on startups

#6

Quite a few articles by Joel Spolsky but missing what I believe to be his most important, Things You Should never Do, Part I. [0] [0] https://www.joelonsoftware.com/2000/04/06/things-you-should-...

Nowadays we don’t just rewrite from scratch - we create entirely new languages to rewrite IN.

Re: Resources for chief technology officers, with the emphasis on startups

#10
post #2

My biggest challenge as a CTO is that, by nature, I'm singular in focus. If I am developing something I find it hard to context switch and review other developers' work. The best strategy I have found so far is to block certain times in the week solely for reviewing everyone's progress.

I'm interested in hearing more about the idea of being an effective CTO while focusing on also being a developer.

I imagine it's necessary for small companies, possible for growing companies, and eventually impossible for sufficiently sized companies where the CTO role is at least 40 hours of your week.

Post reply on HN