this post was submitted on 21 Nov 2023
1 points (100.0% liked)
Entrepreneur
0 readers
1 users here now
Rules
- No Personal Attacks - criticism of ideas is allowed, attacking people is not.
- Self Posts Only - links can only provide supplementary material. Your post must contain enough content to have a discussion.
- No “How To Get Rich Quick” posts - This community is not about making a quick buck. Posts asking the community how to make $X, without making specific reference to a reasonable idea, are not tolerated.
- Avoid unprofessional communication - Please treat fellow entrepreneurs like respected coworkers, label conversations if NSFW and avoid deliberate provocations.
Please feel free to provide evidence-based best practices, share a micro-victory, discuss strategy and concepts with a frame work, ask for feedback, and create professional conversation. Treat every post as if you're at work and representing the best version of yourself.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
We can disagree on that. I've done 2 startups. One is past Series A, and I did the method above. The second, I tried to cody code, and for reasons above it failed.
In the early stages, the problem is, the CTO's job is extremely diverse, and the business job is focused. As time progresses, the trend reverses (Business becomes diverse, tech becomes focused.). Day one is a good example:
Choose the best tech stack. Even from there, in the failure example, I spent weeks on tech selection, getting it wrong. However, in the Series A company, we tossed 5K at a handful of experts.
So my advice to all tech people starting out, is to discover and leverage expert talent, not to be the expert.