A) You are in fact inexperienced and are damaging the product with your code. If you have less than a year or two of programming (that includes one of those code "bootcamps" too...), then he's probably right. I would probably view you as dead weight, and would not want you on the team.
Or
B) You actually aren't that bad and could contribute to the product positively... especially if it's something like a RoR or Django app which is not the hardest thing to pickup w/o an extensive programming/CS background. In this case, your CTO is possibly an elitist prick. I've worked for a CTO who had pointlessly high standards, especially it being a pre-funded startup where, for example, he shouldn't be freaking out about a few lines of redundancy. He churned through a lot of programmers, was all very inefficient, and I certainly felt like he was power tripping at times. Even if this CTO guy is really good, if he has an abrasive personality and does stuff like I described above, for the sake of the team he should be the one to go. If your product is going places he shouldn't be too hard to replace.
A) You are in fact inexperienced and are damaging the product with your code. If you have less than a year or two of programming (that includes one of those code "bootcamps" too...), then he's probably right. I would probably view you as dead weight, and would not want you on the team.
Or
B) You actually aren't that bad and could contribute to the product positively... especially if it's something like a RoR or Django app which is not the hardest thing to pickup w/o an extensive programming/CS background. In this case, your CTO is possibly an elitist prick. I've worked for a CTO who had pointlessly high standards, especially it being a pre-funded startup where, for example, he shouldn't be freaking out about a few lines of redundancy. He churned through a lot of programmers, was all very inefficient, and I certainly felt like he was power tripping at times. Even if this CTO guy is really good, if he has an abrasive personality and does stuff like I described above, for the sake of the team he should be the one to go. If your product is going places he shouldn't be too hard to replace.