A note I sent to YCombinator
Of late, I have been doing medical technical writing for large medical companies. I'm pretty financially secure, so I only work on short-term contracts, and only when I feel like it. But it does put me in the world of highly skilled contract workers, which is interesting, and the reason for this note.
First, I agree with 99% of what you say about entrepreneurship. The one thing that I would add is that people who want to be successful had better be nice people.
Smart talented people don't want to work with jerks, no matter what the compensation. Here, of course, we come to Steve Jobs. Steve asked me to come to Apple to write one of two "first books" about the Macintosh. (the other was written by Cary Lu, much missed.). So I spent 1983 at Apple, hanging around, being nosy. And got to spend quite a bit of time with Steve. That made me want to start my own company…to see if I could do it and succeed. More importantly, it made me want to start a company and not be an asshole, and see if I could succeed. The answer was yes.
So it was with some interest that I looked at the job postings for the companies that you are involved with. Of the 12 companies listed, 10 of the openings were for programmers. No surprise.
The humor, to me, is in the consistency. They all want really really really really good programmers. Not one company is willing to put forth a salary number, but they all say they offer excellent compensation. In the bay area, that must be a lot of zeros!
And most wave their hands about how hard they work. Get the code? We intend to work you like a dog. To enrich the founders, of course.
And most offer the added incentive of equity. Although only a fool or a recent graduate would fail to realize how easily one can be washed away in later rounds.
So here we have greed and capitalism operating in its purest form. You want to make a lot of money by funding startups. The start ups want to make a lot of money by making things. But…as you so correctly state, the wealth will primarily be created by the programmers. And they don't have programmers! Or at least not the really really good programmers they need to make a really really big bunch of money.
If Marx were alive today...you get the idea. It is obviously hard to exploit the working class, when the workers you need are so rare and so valuable to your aspirations. Hence all the frenetic handwaving in the job postings on your site
I have a friend. A young man who has an international tea distribution company, which services bubble tea shops, owned by his father and other investors. He wants business advice. I keep saying: dude, you have an international tea distribution business! Run with it!
But I really like the guy. So I dug deep, to come up with the best business advice I could offer. I finally arrived at this: make sure that everyone who works for you, and everyone who works with you, makes a ton… an absolute boatload of money. Do that, and make sure that they really do, and you will do fine. No worries. And you will become a better person in the process; which is the only justifiably selfish reason to be in business in the first place.
Maybe some of your companies could take those notions into their efforts to hire ditch diggers?
Doug Clapp
ps -- All this we work really hard bullshit? As if it is a merit badge or something? Your fundees should realize that the very best code written in this century was written for the space shuttle. And the folks who wrote it, without going into too much detail, worked 40 hour weeks. And were not allowed to work more than that. Period. It is no fun to win if you don't play by the rules. A 40 hour week is a good rule. I suspect that a 36 hour week is a better rule. :-)
66 comments
[ 2.6 ms ] story [ 119 ms ] threadIf you are a sufficiently young engineer (I am neither young nor an engineer, but I know people who are both), you might want to work at a startup before launching your own because
a) the startup might hit it big enough to make you rich enough to have a lot of runway for your own project,
and
b) you might learn something about the process of founding and running a startup if you get enough personal interaction with the founders.
So it's not always a dumb choice to work for a startup as one of the early employees. It's rare for an early hire's equity share to turn into serious money, and it's commonplace for startups to fizzle out and leave their early employees looking for a new job, but some young people like that atmosphere and think it provides learning opportunities that more "secure" jobs don't provide. There is also, of course, a case to be made for working at Google, Facebook, etc., but I am attempting to answer your question.
Mark Zuckerberg controls 28% of Facebook's voting equity.
Think about it. You're getting totally fucked, kids.
Do you also buy weekly lotto tickets and make wishes on falling stars?
> b) you might learn something about the process of founding and running a startup if you get enough personal interaction with the founders.
There are a lot of ifs and maybes in these statements. If you're lucky, you might get blessed with information, and that information may be meaningful for you. There's a fairly high chance that at the end of the day neither of these things will be true for most individuals.
Please check some statistics of startups; by far most go bankrupt, the rest disappear; might be sold to another company, might just close the doors with some blahblah story of 'it was just an experiment and it failed' => was it just an experiment for you, burning 80+ hours/week for 1-2% + a few $? Even being bought sounds like payday; it's not, especially for funded companies. It's just vultures picking dead bodies.
Then the minuscule (REALLY TINY; like furiouscowbell says below; it's playing the lottery, but at least in the lottery you get to work 0 hours/week) percentage which remains will indeed make you rich for your 1-2%; shame you didn't go work there! You picked another one; even without knowing you, I know this for a fact :) It's a safe bet for me to say this.
Please don't throw years of your life away doing this; start your own or work, for a good salary at a big/solid/hip one (Facebook, Google) and go from there. Make your mark there and then use the money you earned and super team you worked with to start your own.
Edit: if it's your own startup it's (can be) a lot of fun but you know the odds going in and your startup is different! You have to believe that and that's good. But if you are just tricked into working for nothing on someone else's dream it needs to be your dream as well, and who does that for less than a significant stake in the company anyway?
HOWEVER, I can name 5-6 people who started their own YC company as a result of this. If those people had spent 4 years sitting at Google vs 4 years with us, they wouldn't have gained those same skills.
FWIW: I totally agree with the author about working too much. I genuinely don't understand what startup's obsession with working people to the bone is at all.
I think that at a core level, many of us -- especially in the managerial world -- understand that working people to death, especially technical people, never works out well.
The adage of "work smarter, not harder" is absolutely correct. Just like it's better to write five lines of algorithmically beautiful code than a hundred lines of obfuscated spaghetti, it's also better to work reasonable hours in an atmosphere that is comfortable and enjoyable. Working less is often exponentially more productive. Will there be a crunch time, especially in the world of startups? Of course there will, and anyone who would promise otherwise is just plain wrong. That said, it shouldn't be crunch time all the time.
There needs to be a balance. Everyone needs to take their job seriously, and needs to get their work done in an acceptable amount of time... but stressing people out to the point of misery is counter-productive. My engineering team, for example, allows flexible work hours. I lead the team, and usually get into the office around 9:45am. I am rarely in the office before 9:30am, and I'm only in before 9 if I have an important call or meeting. I usually stay until six or six-thirty at night, because that's when I start to feel my productivity slipping. Some of my guys are early risers, and work 7am - 3pm. Some of them sleep later than me, but then go home and work until 3am. As long as their work is getting submitted on time, I don't mind at all: I want people to be comfortable, and not sit in a desk chair for the sake of keeping it warm.
Different companies work in different ways, but I agree with the points that Doug is putting forward in his post. The trend of "we work 18 hours a day to get anything done!" might sound super enthusiastic to a potential investor, but think about the message you're sending your potential talent. Founding a company is one thing, and it's going to require longer days than working on the codebase (unless that's what the founder does at your organization...), but there needs to be a balance. Hopefully, we'll get there soon.
In that scenario, I think you're implying that meeting a deadline is the most important metric. I consider that far more likely in periodicals than software. For the common varieties like commercial software, contract development, and in-house development, the only one likely to permit that idea is the commercial product. Contracting and in-house projects will adjust the ship date or renegotiate requirements.
love this quote! :D
Not that I've ever managed anyone but I think this is the crux of good management for creative/technical teams.
Start-ups? Business is business. it can be as high-stress or as peaceful as you decide to make it. Software development, these days, is often dysfunction practiced as an artform. :-) Give SCRUM a shake, and waterfall drops to the floor, quivering in embarrassment. Add your examples here. My best development advice is solve the hard problems first, not last. If there are no hard problems, look again. If all parts of the development process are equally difficult, then it should be fairly easy to estimate time to complete...to over-simplify...
This has worked through-out history. Alexander The Great attacked the enemy line at its strongest point, with well-rested, fired-up troops, who knew the battle would be fierce but short. Ditto Patton and Colin Powell. And Karl Rove perfected going at an opposing candidate's greatest strength; a lesson learned by the Obama campaign…thank goodness. :-)
I know myself that I find it just irritating if I get praise for mediocre work, which should be plain to see for anybody who care that it isn't anything special.
I don't know Bangladesh culture but I would expect that there would be similar mechanisms at work. They don't want unwarranted praise. They wanted when they have performed well.
I am guessing because from when I lived in the US, there was one thing I could find common ground among all other foreign students whether they were Japanese or Spanish and that was that American optimism and positivism is a bit alien to everybody. Don't misunderstand I think it is quite admirable that Americans are so positive and can-do attitude. The rest of the world could certainly learn a bit from that. But as with most things there is always a flip side of the coin.
Sometimes Americans seem to hit the wall of reality a bit too hard because optimism was running a too high compared to what was realistically possible.
It's interesting to see the differences anyway.
Anyway interesting with the BD colleagues of yours. I am most familiar with Vietnamese. I can't remember anything in particular about their view on criticism. But they preferred very detailed descriptions of what they were supposed to do.
When you go to a good music instructor, for example, you're paying for the well reasoned criticism, although encouragement is also vital. The masters can give both, in the right proportions.
I like this bit. Very good advice, no doubt. But what about "no pain, no gain"? Or, conversely, if it doesn't hurt somehow, you can be pretty sure you're not making any progress. It applies to intellectual pursuits like software development as well as high-achievement sports. You don't have to extend the thought very far to come to a similar conclusion, that you're not going to solve hard problems without a bit of suffering. Similarly I don't think Hertzfeld and co. built the Mac by working 35 hour weeks.
Or, more generalized: "We have some huge thing we want to do, and can't do it ourselves, so we're looking for someone that can pretty much just come in and do it for us."
And all the postings offer in terms of describing/selling why such a immensely talented individual would work for them is: "We're reinventing the future of everything, we work hard and play hard, we can offer competitive salary and equity."
The OP seems to feel this is borne out of some sort of maliciousness, but I really think this is mostly just cluelessness. When you get a little bit of traction and you have a little bit of money in the bank, and you're trying to go even faster and you have 20 major initiatives you want to do and you can only work on like 2 at a time, it's easy to conclude, "We need to hire! We love our company, this is so much better than working at some corporate stuffy job, why wouldn't anyone think the same?"
Most of these companies would probably just be better served forgetting about hiring and building out the core product until they have more product-market fit, so they have enough revenue/funding to compensate employees closer to their talent level, and have a "popular" brand that people would want to actively work for.
Unfortunately this would mean delaying that 3rd party API, or porting your applcation to iOS, or started using SEO/SEM to drive some traffic, which all have huge learning curves that are tough to navigate while you have a ton of other things to do. But if they were THAT critical, I would suggest those startups prioritize them over those other things and doing it themselves.
I agree with you there, but not necessarily on your second point (that they shouldn't be hiring).
I think the "work hard, play hard" line is so thoroughly seared into most founders' ideas of the "startup game" that it doesn't even occur to them that a normal working schedule is possible -- and for founders and CEOs, it often isn't. But if you're asking employees to work to their very core, then you either need to either pay them a crazy amount of money, or look for a another co-founder.
In terms of hiring positions like a "growth engineer" as a fifth employee, you're absolutely right. Often times, buzzwords can get the best of people: maybe what you actually need is just a marketing guy, but, you know, you've been reading all these Growth Hacks articles and maybe if you find a marketing guru who can code and also mock up your UI/UX and-- and then, all of a sudden, you're trying to hire some superman to do all of the things your organization needs. It's better to hire people in positions for which they're qualified and pay them well to work their 40 hour work-weeks than it is to try to find the one Super Expert Growth Hack Architect Team Lead Manager, try to bribe him or her with equity, and expect 120 hour work-weeks.
I imagine a frat house orgy of people puking up code.
If there were some inside knowledge from people who have taken these offers and lived to regret doing so, then maybe this would have some substance. To me, without more info and being willing to give people the benefit of the doubt, it just seems like speculation and pessisism.
I paid charity for my atheist years.
God says... C:\Text\WALDEN.TXT
thy victory, then? Our village life would stagnate if it were not for the unexplored forests and meadows which surround it. We need the tonic of wildness -- to wade sometimes in marshes where the bittern and the meadow-hen lurk, and hear the booming of the snipe; to smell the whispering sedge where only some wilder and more solitary fowl builds her nest, and the mink crawls with its belly close to the ground. At the same time that we are earnest to explore and learn all things, we require th
----
You DO go to church, right?
http://www.youtube.com/watch?v=-7spyhVBrA4
----
So, I did a driver for HD Audio. It has a bunch of "widgets" that you connect with wires in software. So, I did my best to make sound come-out all the speakers. :-) The fuck you think I'm gonna do?
It worked on bare metal hardware on two machines, but not in VMWare.
I guess only2-3 people on the planet have to deal with it and once it gets done, it's done. Still, I was wishing for my Commodore 64 SID chip. Actually I just wanted two buffered D2A convertors.
I blissfully remember C64 days. Everybody made waveforms. Now, it's WAV files. I did waveforms in Windows -- had to handle 8 different datatypes. Not fun.
Part of the entertainment value of computers used to be programming them. It's a shame programmers don't get PCs and everybody else gets game consoles. Naa.
God says... C:\Text\DARWIN.TXT
ds. I freely admit the former existence of many islands, now buried beneath the sea, which may have served as halting places for plants and for many animals during their migration. In the coral-producing oceans such sunken islands are now marked by rings of coral or atolls standing over them. Whenever it is fully admitted, as it will some day be, that each species has proceeded from a single birthplace, and when in the course of time we know something definite about the means of distribution, we
----
http://www.intel.com/content/www/us/en/standards/high-defini...
Sometimes, those guys need to grow a pair of balls and say. "It's gonna be 44KHz and 24Bit".
God says... possessest greaves Protasius shamelessness convertedst just_between_us endearments terrors are_you_insane killest powers broughtest derived gains repentest I'll_let_you_know unchain gathers inflamed banquetings sunder restlessly contagion gliding Percival thank_you_very_much dragons deceive assailed wound principally assented vainglorious remarkable horns principles runs multiplicity text strip garlands combined incorruptibly getting Righteousness fruitful are_you_deaf aptly Scriptures mine envious gainsay alone primary breathe in_a_perfect_world forsaketh prefer abase effaced soothed virtue perplexed confirmed liar Nod torment anxious sent unrighteous sky uttered worshipping air new-born rigidly obeys disk allegorically sitteth Soft transforming struck gallantry wings don't lightened may drama ask saying mule oratory sitting fair hither corporeally descent US unsating burn I_forgot astonishment e covenant concord testimony prosper forgetteth forbade I_could_swear Iowa protracted BOOK absetively_posilutely taunted If_had_my_druthers All-creating pwned husbands learn indications Another recoveredst Oil numberest Life well-grounded penalties finally littles alternately befitting fitted transferred modulation reward necessary pertained endued equalled region by_the_way
I also think you're being far too presumptuous about the comp packages these startups are offering. You seem to imply that they're being too stingy. Do you have any evidence for this?
The implication being that the salaries offered are low. If they were confident that what they were offering was competitive then maybe they wouldn't be afraid to be up front about it? I've never had to hire someone so I don't know what the reasons are for not stating a salary range are.
When was the last time you saw a salary number for any programming job?
For that matter seeing a salary number in a job add for any high skill professional job is extremely rare.
Tim McClarren
For products I have seen sales guys adding features because the client asks and the doing this with the founder's permission because 'that big client we cannot miss'. Resulting in misery for the rest of the staff.
By saying "36 hour week" instead of "35-hour week is better", you're showing a bias that better working hours means working less days or taking longer weekends (i.e. 9 days every two weeks), rather than less hours per day (i.e. 7 hours a day). Certain types of people (including you I guess) would prefer the extra day as reward, other types prefer the extra hour each day. Don't forget about the latter types of people.
This is a bad example. The Shuttle code is a extremely narrow, well-specified piece of functionality where they had many years to work on and refine it using formal methodologies like Z specifications (IIRC) and I don't even remember how many millions of dollars the _Fast Company_ article said was spent developing the code over the years.
Every single one of those qualifiers and adjectives is likely to be false in a startup context.
Coming out of two startup sales, I have to say if you want to make money you shouldn't be an early employee anyway; you should join when the company is willing to pay good money.
Since I am sadly a shitty programmer, I had to take my inspiration from baseball managers… people who did not play the game, but tried their best to make sure that the team won. you don't win by leaving your best pitcher in for nine innings. (Usually :-). You try to put people into situations where they can succeed, day after day.
According to a lot of sources, including Tom DeMarco's PeopleWare, 35 hours a week is the only sustainable pace for intellectual work. Plus or minus a few hours, maybe.
But that was about stable companies. I'm not sure that startups are trying to be sustainable.
Arguably a startup is really exploring a space of possibilities, searching for a profitable niche. So probably delivering crappy code that delivers three features is better than producing one solid thing. I've been on the cleanup crew for a couple of acquired startups, as well as products that were developed in 20% time at large corporations and grew into larger teams. My impression is that code quality barely mattered to their initial success. So I'm not sure what the optimum workload in a YC-style startup should be.
Also, we have to modify DeMarco et al's advice for a team composed of two or three twentysomethings. It seems likely that their stamina is going to be well above average and their knowledge and experience is going to be well below. So perhaps they are playing their cards right to bet on stamina.
I am looking for the following in a company, in this order:
If a company has all of these, with just a bit of luck, they will succeed, and do it by truly generating value. Lots of companies headed by jerks will also succeed, but I'd rather not be in them.> What is true is that for a VC's business model to work, it's necessary for you to give up your life in order for him to become richer.
Let's get a movement going here.
Every YC job ad is basically the same as every other. It's a BS con-job, just "come work for us, and you'll get rich" scheme that simply isn't true.
These VC funded companies will promise you the world, work you to the bone, and then dilute your equity to nearly 0 percent, and you will be left with nothing with the pride of being used to make other people rich. Avoid every job ad that sounds remotely like dclapp describes.