Ask the CTO why they made that decision.
It doesn’t come lightly to switch backend languages, at any stage of a company.
CTOs make decisions that are often sound for the sake of the project, but they often fail to forget other things. (That’s why we have CEOs.)
For example: what resources are currently available to the CTO? Do they have enough money/time/and People to change the architecture from node to rails? If you are bootstrapped, and they know rails and no one else does, they are effectively putting all of this on themselves until it is done.
Have you done any market validation? Do you even know that you will have users to justify the cost of the switch?
I am a big proponent of “get someone to pay you” for the work you do. It’s great to have ideas, but if you are iterating in a vacuum, then it is useless.
Design With purpose. Ask him his reasoning for this and how it affects your users now and in the future, and how it affects the cost of development now and later.
Now everyone on a team needs to be a developer, by the way. some people need to lead it.
Originally Posted: https://www.quora.com/Our-CTO-said-we-should-change-our-backend-language-but-I-dont-know-it-What-should-I-do-if-I-want-to-still-be-involved-in-the-development-process-I-am-the-founder-of-the-startup
Originally Posted On: 2015-12-08