Sounds interesting. Will this be available as a podcast?
fredwilson
· 1 year ago
You know I should get one of those digital audio recorders that record to mp3 and record every talk I give and then upload it to the internet.
Not sure how many people would take the 45mins it would take to listen to the talk.
If there was demand for it, I'd do it
fred
Charlie Crystle
· 1 year ago
you should do it to see if there's demand. I think a good inexpensive one out there is the Zoom4 here: http://www.samedaymusic.com/product--ZOMH4 , stores up to 30 hours or so.
I absolutely agree with what you just said about finding a good manager to deal with egomaniacal developers. A few weeks ago I took the time to put together my thoughts on the matter in a rather long and mostly useless post ( http://thebigdeal.wordpress.com/2007/11/26/cele... ). Really great to have your 2 cents on the subject.
charlie crystle
· 1 year ago
CTO is about innnovation, vision, discovery, research, prototyping.
VP of Engineering is about recruiting and managing developers, programmers (there's a difference), testers, etc--the crew you need to ship product.
The difference between the two is staggering, and assuming you can mix the two is a big mistake.
fredwilson
· 1 year ago
Of course
But we often get the cto role in a founder and what we need in our companies is the vp engineering role
Names are a problem they confuse people. But the role is clear. The person who manages the developers
Fred
Nate Westheimer
· 1 year ago
Very important, this point.
I CTO is responsible for the technical direction of the company. What technology will be used. What are the standards. What is the configuration. What's the architecture the engineers are building?
VP Engineering manages the execution of the development/engineering plan.
charlie crystle
· 1 year ago
Right--we need a VP of Development, which is why I'm hot on this right now. The last thing we need is more innovation around product, APIs, vision, etc. We need to build and manage teams.
fredwilson
· 1 year ago
It seems like that is always the scarce resource until you find the right person. It makes such a difference
Fred
daryn
· 1 year ago
I agree with your distinctions, but in most (web) startups, the CTO & the VP of Engineering are one and the same. Additionally, the CTO/VP is often the lead programmer/developer/architect, at least out of the starting gate.
daryn
· 1 year ago
sorry, the threading and my use of pronouns is confusing. This is a reply to charlie crystle's comment, not fred's or nate's.
Anthony Stevens
· 1 year ago
Hi Fred -- mostly great post, but as a CTO/CIO, I have to disagree with your premise about the inevitability of the primadonna. See my fullish response here: http://xidey.wordpress.com/2008/01/09/fred-wils...
fredwilson
· 1 year ago
I hope I didn't suggest that the prima donna is inevitable, but we certainly run into them a lot in our companies
"bursts of creativity and equally long periods of uselessness"
Nail on head. And it's the CTO who can recognize this and create an environment where the developers can flourish more than not that make or break a development. When they aren't willing to put up with the uselessness and they inevitably settle for a more predictable but mediocre staff as a result.
Jeff Judge
· 1 year ago
+1 on agreeing with that.
i was talking to a friend (a friend who is also talented engineer) yesterday who told me that a few days ago his manager approached him and said "you seem to be spending a lot of time on the internet today, don't you have anything to do?". he found it ironic as he was researching monitoring tools for one of their applications. he quit the next day.
i think the cto sets the technical vision and his team executes that vision. i'm not saying the cto is sitting around beard stroking thinking of the uber architecture; he/she understands the business and has a vision to scale it. in a large organization, a vp of engineering is a direct of the cto and is all about execution. in that same large organization, the cto keeps pulse and is a pivotal communicator. in a startup, you won't find such division of roles as it's not practical for a small company. the cto (as fred said) is usually a founder, and is also an informal vp of a dozen other things.
great post fred. i love where we're at right now, and i think the future is even more exciting.
daryn
· 1 year ago
Amazon Web Services are "game-changing" for sure, and in theory (and increasingly in practice) I'm a huge fan. I think ultimately things like storage and compute will be commoditized such as bandwidth and connectivity. There will always be times when you need your own environment, for control, security, privacy, legality, etc, but I think the de facto choice will be the cloud.
What scares me is that many of the Amazon services that people are trusting as "infrastructure" are still in Beta, and at least in the cases of FPS and EC2, I've seen significant issues pop up. That's not to say you wouldn't have these issues and worse in you rolled your own payment gateway or server environment, but at least it'd be in your hands to fix and troubleshoot.
Raza Imam
· 1 year ago
The CTO has to be intimately involved in the business side of things to make sure that her team is solving the right problems the right way. I think the pressure is really on for CTO's to be innovative and see the world differently. I own a Chicago-based offshore software development firm that acts as a CTO for our clients as opposed to just cheap labor. Our problem is to find simple solutions to the complex problems that our clients need solved. The traditional thinking is that a complex problem needs a complex solution... it just ain't so. We also have to train our developers to think creatively and truly understand the problem they're trying to solve. We've had clients that said they wanted an SOA architecture but had no justification for it; they knew it was a buzz word so they wanted us to implement it that way... in fact he didn't really know what SOA was. Our job was to step back and get them to understand what they're trying to do and have our developers come up with an intelligent way to handle it. A great CTO should be able to instill a vision in her developers. To make rambunctious team of developers work cohesively to solve a problem is incredibly hard.
Seesmic's use of Twitter is a good example of looking at a problem and solving it intelligently, rather than trying to build something from scratch. Successful businesses in any industry know this... Henry Ford focused on a smart process to build cars.
Regarding scalability, Dharmesh Shah had a really insightful post on his blog called "Premature Scalaculation" talking about how startups focus on tangible and safe metrics like scalability at the expense of more ambiguous, yet crucial things like usability, innovation, and increasing adoption.
Looking at developers as artists makes a lot of sense. Creative juices can be hard to control. From my perspective CTOs can be likened to music producers. They have the technical (musical) chops to do develop (write and play music) as well as the ability to focus and lead a team of developers (musicians) to a finished product (song/album).
This excerpt from paragraph 5 sums it up:
I assume its a bit like managing high maintenance entertainers. The best developers are artists who are often moody, are anarchists who have bursts of creativity and equally long periods of uselessness. They are strong willed people who will fight with their colleagues over anything and everything. The people who have mastered the art of managing these kinds of people are a rare breed and every great technology-based business needs one of them.
Dustin
· 1 year ago
"why wouldn't you want to run on the same infrastructure that Amazon runs on"?
APIs are great and combining services/web apps/etc will make business and software that much more enjoyable. One problem comes up when reliance of said APIs 'breaks' your software once the use agreements change slightly. I would think twice before placing the core of the business or its software in the hands of other's code or legal documents.
Abdur
· 1 year ago
CTO's need to think about their business and stop recreating the wheel figuring out hosting and infrastructure. Any discussion or meeting that helps us towards that realization is great.
The Amazon services may not be ready for all situations but still move the industry forward in two important ways. First, it gives small compute needs the first viable means for commodity computing to the industry. Second, business that need resources that are not cost effective with Amazon now have an industry standard pricing for bandwidth and hosting to negotiate with.
I recently examined our needs (Summize) in comparison to what it would cost with Amazon on our blog (http://blog.summize.com/2007/12/compute-resourc...) and found that Amazon is still pricey for storage and CPU / Memory intensive applications. The benefit of posting the analysis, our hosting provider is actively working at getting costs to Amazon prices. I know in the end large compute services will free most CTO's from this nightmare of hosting and infrastructure thus Amazon's move is game changing.
C. Enrique Ortiz
· 1 year ago
great piece, thanks...
Bill Seitz
· 1 year ago
Really sorry I couldn't make it this month to the meeting.
Aruni
· 1 year ago
Liked the post on the Union Ventures blog. This post shows another side to one of your earlier posts where you seemed to indicate that you had to have a technical co-founder from the beginning in order go be successful in a VC backed company. I remember thinking that was an interesting filter criteria on many levels. I have a great dev team and PM in India. I have access to technical support & advice on critical issues locally. Would love to have a technical hands on full-time co-founder but you can't always get what you wish for right away. I found your original observation on having a technical founder interesting because of all the risks out there (Technical, People, Market) I've heard it said that most investors believe the technical risk is usually manageable (unless you are inventing the Start Trek transporter). If you have the right Market it will be easier to find People. If you have the right People they will adjust to the Market.
By the way, the last several times I come to this blog using IE 7 I get a "stack overflow at line: 0" error pop-up. I hit OK and then it's fine.
Mitchell Ashley
· 1 year ago
I've always said I have the best job in the company as a CTO. It's very creative and is all about producing fantastic results you want your customers and the market to feel passionate about. That's right up my alley – It’s what I love to do.
There's another philosophy I've adopted from the startups I've done; "as goes Engineering, so goes the rest of the company." If product engineering is hitting it on all cylinders, it not only produces product but it literally enables the rest of the company. Sales and marketing is more aggressive because they have a great team and product behind them. Sales people want their reputation associated with it, rather than hesitating in case the next release falls behind schedule or suffers from poor quality. The psychological impact to the company is huge, either positively or negatively.
First and foremost, VPE'ing is all about producing products, but it's also about connecting the development team to the business and the customer. It's easy to get isolated when you are so deep into creating software and products., and the more you can connect the team with the other important activities and events happening, both inside and outside the startup company, the better the team is positioned to make good decisions. “What” you are doing is very important, but I like to focus on bringing clarity to "why" questions; Why are we going after the market we are? Why did we make a certain change inside the company? Why is it more important to fill out the functionality in one area of the product vs. another? All of this helps the team create the best results.
Software developers want to feel empowered to bring their talents to creating products, not just writing code. I have this philosophy that if you deeply believe in people and you passionately focus on their personal growth, they will amaze you with what they can do. Often times they'll amaze themselves by doing things they themselves didn't know they could do! I think these things are essential to creating high performance teams.
The right kind of leadership is so important in a startup. I'm taking some time off in part of January to write an ebook about startup leadership, detailing my learnings and thoughts from startup experiences. I hope some of those writings will be helpful to others pouring their passion into creating great products and companies.
severus
· 1 year ago
ok
David
· 1 year ago
Ok, and for those of us ex CTO's what's the best way to land back at a startup as a CTO?
fredwilson
· 1 year ago
Send me an email please
Fred
David
· 1 year ago
I'm a world class CTO. Where are the companies beating down my door? Columbia MBA, 6 years IBM consulting, 3 .Com's under my belt, 1 of them IPO'd. (david@mondrus.com)
All Comments
mp3 and record every talk I give and then upload it to the internet.
Not sure how many people would take the 45mins it would take to listen to
the talk.
If there was demand for it, I'd do it
fred
http://www.samedaymusic.com/product--ZOMH4 , stores up to 30 hours or so.
or the H2: http://www.samedaymusic.com/product--ZOMH2
A few weeks ago I took the time to put together my thoughts on the matter in a rather long and mostly useless post ( http://thebigdeal.wordpress.com/2007/11/26/cele... ). Really great to have your 2 cents on the subject.
VP of Engineering is about recruiting and managing developers, programmers (there's a difference), testers, etc--the crew you need to ship product.
The difference between the two is staggering, and assuming you can mix the two is a big mistake.
But we often get the cto role in a founder and what we need in our companies is the vp engineering role
Names are a problem they confuse people. But the role is clear. The person who manages the developers
Fred
I CTO is responsible for the technical direction of the company. What technology will be used. What are the standards. What is the configuration. What's the architecture the engineers are building?
VP Engineering manages the execution of the development/engineering plan.
Fred
run into them a lot in our companies
fred
Nail on head. And it's the CTO who can recognize this and create an environment where the developers can flourish more than not that make or break a development. When they aren't willing to put up with the uselessness and they inevitably settle for a more predictable but mediocre staff as a result.
i was talking to a friend (a friend who is also talented engineer) yesterday who told me that a few days ago his manager approached him and said "you seem to be spending a lot of time on the internet today, don't you have anything to do?". he found it ironic as he was researching monitoring tools for one of their applications. he quit the next day.
i think the cto sets the technical vision and his team executes that vision. i'm not saying the cto is sitting around beard stroking thinking of the uber architecture; he/she understands the business and has a vision to scale it. in a large organization, a vp of engineering is a direct of the cto and is all about execution. in that same large organization, the cto keeps pulse and is a pivotal communicator. in a startup, you won't find such division of roles as it's not practical for a small company. the cto (as fred said) is usually a founder, and is also an informal vp of a dozen other things.
great post fred. i love where we're at right now, and i think the future is even more exciting.
What scares me is that many of the Amazon services that people are trusting as "infrastructure" are still in Beta, and at least in the cases of FPS and EC2, I've seen significant issues pop up. That's not to say you wouldn't have these issues and worse in you rolled your own payment gateway or server environment, but at least it'd be in your hands to fix and troubleshoot.
I think the pressure is really on for CTO's to be innovative and see the world differently. I own a Chicago-based offshore software development firm that acts as a CTO for our clients as opposed to just cheap labor. Our problem is to find simple solutions to the complex problems that our clients need solved. The traditional thinking is that a complex problem needs a complex solution... it just ain't so. We also have to train our developers to think creatively and truly understand the problem they're trying to solve. We've had clients that said they wanted an SOA architecture but had no justification for it; they knew it was a buzz word so they wanted us to implement it that way... in fact he didn't really know what SOA was. Our job was to step back and get them to understand what they're trying to do and have our developers come up with an intelligent way to handle it. A great CTO should be able to instill a vision in her developers. To make rambunctious team of developers work cohesively to solve a problem is incredibly hard.
Seesmic's use of Twitter is a good example of looking at a problem and solving it intelligently, rather than trying to build something from scratch. Successful businesses in any industry know this... Henry Ford focused on a smart process to build cars.
Regarding scalability, Dharmesh Shah had a really insightful post on his blog called "Premature Scalaculation" talking about how startups focus on tangible and safe metrics like scalability at the expense of more ambiguous, yet crucial things like usability, innovation, and increasing adoption.
Raza Imam
http://BoycottSoftwareSweatshops.com
Thanks
Fred
This excerpt from paragraph 5 sums it up:
I assume its a bit like managing high maintenance entertainers. The best developers are artists who are often moody, are anarchists who have bursts of creativity and equally long periods of uselessness. They are strong willed people who will fight with their colleagues over anything and everything. The people who have mastered the art of managing these kinds of people are a rare breed and every great technology-based business needs one of them.
APIs are great and combining services/web apps/etc will make business and software that much more enjoyable. One problem comes up when reliance of said APIs 'breaks' your software once the use agreements change slightly. I would think twice before placing the core of the business or its software in the hands of other's code or legal documents.
The Amazon services may not be ready for all situations but still move the industry forward in two important ways. First, it gives small compute needs the first viable means for commodity computing to the industry. Second, business that need resources that are not cost effective with Amazon now have an industry standard pricing for bandwidth and hosting to negotiate with.
I recently examined our needs (Summize) in comparison to what it would cost with Amazon on our blog (http://blog.summize.com/2007/12/compute-resourc...) and found that Amazon is still pricey for storage and CPU / Memory intensive applications. The benefit of posting the analysis, our hosting provider is actively working at getting costs to Amazon prices. I know in the end large compute services will free most CTO's from this nightmare of hosting and infrastructure thus Amazon's move is game changing.
By the way, the last several times I come to this blog using IE 7 I get a "stack overflow at line: 0" error pop-up. I hit OK and then it's fine.
There's another philosophy I've adopted from the startups I've done; "as goes Engineering, so goes the rest of the company." If product engineering is hitting it on all cylinders, it not only produces product but it literally enables the rest of the company. Sales and marketing is more aggressive because they have a great team and product behind them. Sales people want their reputation associated with it, rather than hesitating in case the next release falls behind schedule or suffers from poor quality. The psychological impact to the company is huge, either positively or negatively.
First and foremost, VPE'ing is all about producing products, but it's also about connecting the development team to the business and the customer. It's easy to get isolated when you are so deep into creating software and products., and the more you can connect the team with the other important activities and events happening, both inside and outside the startup company, the better the team is positioned to make good decisions. “What” you are doing is very important, but I like to focus on bringing clarity to "why" questions; Why are we going after the market we are? Why did we make a certain change inside the company? Why is it more important to fill out the functionality in one area of the product vs. another? All of this helps the team create the best results.
Software developers want to feel empowered to bring their talents to creating products, not just writing code. I have this philosophy that if you deeply believe in people and you passionately focus on their personal growth, they will amaze you with what they can do. Often times they'll amaze themselves by doing things they themselves didn't know they could do! I think these things are essential to creating high performance teams.
The right kind of leadership is so important in a startup. I'm taking some time off in part of January to write an ebook about startup leadership, detailing my learnings and thoughts from startup experiences. I hope some of those writings will be helpful to others pouring their passion into creating great products and companies.
Fred