Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To be fair with three people in the company position titles are meaningless. You will not get to do only one thing, nor will anyone else. Each of you is required to wear many hats and contribute at all levels. Even if that means cleaning the toilet before an investor or potential client comes for a visit.

You maybe the most technical of the group hence your CTO title. So the team is probably looking to you to drive the core tech decisions. Other roles have their key priorities respectfully. But even than you should all work more closely than ever and collaborate at this early stage.



"So the team is probably looking to you to drive the core tech decisions."

Remember that "core tech decisions" include hiring and managing a development team - hopefully your company will grow to the point where you'll need one, and it could be very soon, so you need to be prepared for it. Those kinds of decisions are much more important than what stack you build on or what cloud provider you pick, and with a much higher cost of fixing mistakes. Do any of the founders have experience with hiring and managing people?


Agree with everything here. I’ve never been a CTO but have been the only other dev working alongside a CTO and you will wind up doing many non-technical as needed for the business. Laying a good groundwork for future employees and making a best effort in every task is the best thing to do.


Most of this makes perfect sense, but allow me to disagree with one point "Those kinds of decisions are much more important than what stack you build" the most technical founder should never lose focus of the importance of this. Of course, if you don't have a business it doesn't matter what stack you're using, to build a quick RAT (yes RAT, not MVP) you don't need to go deep on the stack, but once those experiments are moving forward you've to be careful. You've to pick the right stack and tools to build your company, focus on that even more if you are a technology company (not a consumer one). This won't only be part of the scaling plan of your company but it'll also play a big role on recruiting if you're using new technologies you've to train people if you're using more mature technologies you probably have a better hiring pool in one than another.

Plus, you need to be able to share with your team the importance of picking one stack over another, the cycle of development and the times to invest in refactor or why to re-build something that started as an experiment but now needs to scale.


Agreed.

I'd add that if someone is (a) unwilling to wear any hat at any time or (b) trying to take over people's hats without reason then you should drop them, quickly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: