141–148 of 148 posts
Earlier quoted context omitted.
...you just found one and talked to him.
not always a him
https://github.com/kuchin/awesome-cto
Maybe I have few more useful links here:
Earlier quoted context omitted.
I mean this is decent advice, but slightly odd given you could easily have plugged your site here AND actually given the OP what they asked for :-) Maybe it’s some reverse psychology thing. Ok I’ll do it, you evil genius… https://hackernewsbooks.com PS CTOs aren’t always chosen, many are self-appointed as founders or co-founders (possibly in this case too). Chosen implies you’ve been subject to external assessment, s…
That is a very interesting line of thinking, my comment was kind of the opposite - I find that after reading a couple of good books on a certain topic, the rate of learning goes down rapidly compared to the steady amount I get from HN comments and experience. About hackernewsbooks - it's not mine since many years and I am not affiliated with it, I am just the one who built it and sold it. It's still nice though.
It just seemed a shame not to mention hackernewsbooks since it is probably a good resource for the OP :)
It makes more sense though if you have sold it! Congrats on that.
From my exp CTO in small startup is marketing tool and it does not mean real "the CTO". In small org CTO is simply "do it all in no time" type of job, that includes hands on coding, infrastructure, but also hiring, overseeing and managing people. You also need to understand code lifetime and methodology of your choice, how to use it to provide good enough time estimates. And all of this will lead you to be probably replaced once organization grows.
As others have said, joining a community has been helpful to me. I would recommend CTO Craft. You get to hear what issues others are dealing with and how they solve them. https://ctocraft.com/community/