News for hackers. Stuff that matters.
Re:Every time an engineer joins Google, a startup dies by nfnaaron on Thursday February 11, 2010 @10:00AM (#1117723)
"Whenever I see a brilliant kid decide to join Goldman Sachs, McKinsey, or Google, I think to myself: a startup just died, and as a result our world is a little less wealthy, innovative, and interesting."

Or, a future founder just began the process of gaining experience and perspective.

Re:Every time an engineer joins Google, a startup dies by philk on Thursday February 11, 2010 @10:25AM (#1117770)
This is a bit of a trap. It's easier to take big risks if you have little to lose. Once you're established at McKinsey, Goldman Sachs or Google you have a comfortable standard of living and a job that gives you both challenges and social status. Letting go of all that to be the guy slaving away at a crazy idea is often harder than trying the crazy idea because you have little else.

Also when you're busy at work time can just fly by. It's easy to look up from working and find a few years have gone past.

Re:Every time an engineer joins Google, a startup dies by nfnaaron on Thursday February 11, 2010 @10:39AM (#1117810)
"This is a bit of a trap."

Yes, it can be. The truth is, some of those brilliant kids going into BigCorp are lost startups, some are future startups, and most won't be startups regardless, because most people aren't founders.

"Also when you're busy at work time can just fly by. It's easy to look up from working and find a few years have gone past."

Roger that.

Re:Every time an engineer joins Google, a startup dies by EricBurnett on Thursday February 11, 2010 @10:54AM (#1117857)
The truth is, some of those brilliant kids going into BigCorp are lost startups, some are future startups, and most won't be startups regardless, because most people aren't founders.

Exactly. I will be starting at Google in June, but I am not a "startup lost". I have thought about it, and eventually came to the conclusion that I am not startup material for a number of reasons. This may change in the future after I have worked for Google, and if so, I can always join a startup then.

Re:Every time an engineer joins Google, a startup dies by huherto on Thursday February 11, 2010 @11:36AM (#1117963)
You probably know this already, but it if you dream of eventually doing a start up make sure to keep your expenses under control now. Your expenses tend to grow along your paycheck. It can be really hard to downsize if you decide to go the start up route.
Re:Every time an engineer joins Google, a startup dies by mikepurvis on Thursday February 11, 2010 @12:26PM (#1118105)
I agree with this. Even if your paycheque is $5k a month, practice living on half of that or less—maybe a lot less. It won't hurt to save the rest anyway.
Re:Every time an engineer joins Google, a startup dies by ojbyrne on Thursday February 11, 2010 @01:02PM (#1118225)
One of the rules of thumb I heard somewhere and try to do (though it's pretty damn hard) is to save 1/3 of your gross salary.
Re:Every time an engineer joins Google, a startup dies by MrFoof on Thursday February 11, 2010 @01:56PM (#1118420)
This is/was more popular in eastern Asia, particularly in China when Confucian culture was in its heyday. I remember growing up a Chinese family bought a house in our neighborhood with cash. He was a garbage man, they had two kids, and his wife didn't work.

I've managed it since I was 25. Here's what I found.

* If you're making below or well below the median salary for your state, good luck getting past 10% of your net pay. 30% of net is much easier when you're at or just above the median. 33% of gross requires you to have made those "long-term purchases" already, such as furniture and a vehicle.

* On cars, try to buy the first "long term" one in cash. Yes, this takes time to accomplish, but the reality is once you can do it the first time, you'll be able to easily continue doing it for the rest of your life. Buy what you truly want, otherwise you'll find excuses to replace it earlier. 18-35 year olds in America would be much happier if they had bought a Miata or a Mustang or what they had actually wanted instead of their Corolla or Taurus they felt was a "more responsible" choice.

* Learn to cook. Last night I had a steak, homemade biscuit, asparagus, couscous, drink and a homemade cookie for just under $3. Packaged foods and mixes are never cheap, and the cost of prepared foods is staggering.

* If you don't love it and see yourself using it 10 years from now, why are you buying it? The pricier the item, the longer you better see yourself using it A huge sink in consumer culture is buying "disposable items", particularly furniture, gadgets, and even cars in some cases. Buy once, take good care of it, and avoid having to buy it again for some time, if at all. Furniture especially - go used to save money if the piece is still in production (typical for modern classics), because odds are even if it's already 40 years old it'll still handily outlast you.

* Live as close to work as possible. Mass transit is cheaper than anything (I can go all over Boston, as much as I want, for $59/mo). The higher cost of living is more than offset by the extra time to cook, relax, and decompress.

* Reassess your budget, in full, every year. Prune possessions and figure out why it was a waste. Repeat until your friends refer to you as that really cheap person that somehow has really nice things.

Re:Every time an engineer joins Google, a startup dies by patio11 on Friday February 12, 2010 @04:14AM (#1120135)
On cars, try to buy the first "long term" one in cash.

You will be absolutely amazed what it does to your finances if you don't have a car payment. Too many people treat them like they're laws of nature. Google for [Drive Free, Retire Rich], which aside from poor math due to overly optimistic assumptions of investment returns is an amazing video.

Re:Every time an engineer joins Google, a startup dies by whatusername on Wednesday February 17, 2010 @09:09PM (#1133218)
I don't think the maths was wrong, just the assumptions were possibly optimistic. A $1500 car doesn't really depreciate much (unless it dies), but a $12000 car does. And then there's the 12% investment return figure.

(Still - the overall point is very valid)

Re:Every time an engineer joins Google, a startup dies by jasonkester on Thursday February 11, 2010 @01:23PM (#1118305)
I don't have a rule of thumb, but my actual number is usually more like 2/3 of gross saved.

It helps to have the car paid for and not have a mortgage or apartment lease though.

Re:Every time an engineer joins Google, a startup dies by ojbyrne on Thursday February 11, 2010 @02:43PM (#1118543)
That seems impossible for me - taxes and other deductions are over a third of my gross salary.
Re:Every time an engineer joins Google, a startup dies by potatolicious on Thursday February 11, 2010 @04:40PM (#1118847)
Ditto, my taxes are about a third of my gross, but I do save about half of my net, making for about a 1/3 savings rate overall.

Honestly, I haven't hut to cut on many things to get here, so I'm pretty happy about it. One key thing has enabled this:

No car. None, no desire for one. I pay extra to live centrally in the city near good public transit, but the extra I've paid (compared to living in a burb) is a tiny fraction of the cost of car ownership.

By my estimates that alone gets me an extra 10% savings rate at the very least. I have all the spare cash in the world to travel, buy cool toys without ever digging into the rainy day/startup fund.

Being childless certainly helps, too.

Re:Every time an engineer joins Google, a startup dies by ojbyrne on Thursday February 11, 2010 @05:57PM (#1119020)
Yes, I mostly save "about" a third. The hard part is getting to above a third consistently. I agree with the car part, but with the proviso that it doesn't work so well when suddenly you end up with a job in some industrial park that doesn't have good public transit.
Re:Every time an engineer joins Google, a startup dies by orborde on Friday February 12, 2010 @06:02AM (#1120264)
True, but you can always wait to buy a car until you need it, and the savings will* still outdo the cost of a rental to tide you over while shopping for one.

*Estimating here. Looking at Hertz.com, you can rent for ~$250/week, which for me equals about 4 months in minimal car insurance.

Re:Every time an engineer joins Google, a startup dies by nostrademons on Thursday February 11, 2010 @07:34PM (#1119242)
2/3 of net, however is very possible. Works out to something like 50% of gross, maybe a little less.
Re:Every time an engineer joins Google, a startup dies by jasonkester on Thursday February 11, 2010 @04:43PM (#1118852)
You're right. I guess I don't factor taxes in at the time, since I pay them out of savings.
Re:Every time an engineer joins Google, a startup dies by b3b0p on Thursday February 11, 2010 @10:16PM (#1119641)
I save very close or more than 2/3 of my current salary.

I own my car, I bought it in cash. Where I live I need it (I already tried the whole Vespa thing, I lasted one winter and was exhausted).

I don't have a mortgage. I sold my house.

I rent. I don't want the baggage a house brings (time, maintenance, stuck in one place). My rent is ~ half of my old mortgage which was not that much and in a much more enjoyable community (behind campus and about 2 min walk from the video store, coffee shops, and grocery store).

I only buy what I truly believe I will hang on to and be happy or content with.

Why do I do this? I don't know, maybe to retire early. Maybe do the whole start up thing someday.

However, I think it's mostly because it's comfortable for me. I don't feel comfortable in one place and like the ability to just throw everything in my car and go. I don't like things that hold me back or slow me down.

Edit: this is after taxes and whatever else they take off. I'm going by what my paycheck says.

Re:Every time an engineer joins Google, a startup dies by ojbyrne on Thursday February 11, 2010 @11:44PM (#1119790)
For me it is the startup thing. 1 year of saving 1/3 of your gross (1/2 your net) is one year of runway when you quit.
Re:Every time an engineer joins Google, a startup dies by sailormoon on Thursday February 11, 2010 @12:34PM (#1118134)
Agree, agree, 100x agree!

You do not need a BMW, buy a corolla. You do not need the loft, live in the cheapest decent unit you can find. Don't get into the showy lifestyle trap.

Re:Every time an engineer joins Google, a startup dies by eru on Thursday February 11, 2010 @12:52PM (#1118187)
If you live in Europe (or New York), you don't even need a car.
Re:Every time an engineer joins Google, a startup dies by gcheong on Thursday February 11, 2010 @03:47PM (#1118710)
Or San Francisco, or Tokyo...
Re:Every time an engineer joins Google, a startup dies by derwiki on Thursday February 11, 2010 @06:51PM (#1119148)
and for everything else, there's ZipCar (I just sold my car :)
Re:Every time an engineer joins Google, a startup dies by brlewis on Thursday February 11, 2010 @12:47PM (#1118180)
I agree, and will add that kids are expensive, especially if you want good education. "Ramen profitable" is a lot harder to reach when your life gets to that point.
Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:18PM (#1119528)
I've got kids myself, and I blogged recently about how having a family is forcing me to keep my fulltime job longer than I would like to:

Most startups seem to embrace 60-80 hour weeks, you keep reading about them and begin to believe that this is normal. After 12 hour marathon coding sessions ‘typical entrepreneurs’ walk 10 metres from desk to bed and collapse in their shared accommodations. Living in such lean conditions makes those crucial first months of business far cheaper. This work ethic and minimial living costs maximises the runway before the seed money runs out.

Paul Graham is one of my favourite bloggers, and his essay entitled The Other Road Ahead he paints a clear picture of how lean a start-up can be, stating "You can literally launch your product as three guys sitting in the living room of an apartment, and a server collocated at an ISP. We did."

No matter how much I’d love to take the lean ramen noodle approach it’s simply not practical for me. I’m a father of two, a husband of one, and an employee. I’ve got a beautiful family with young children, a modest house with a mortgage, and a full-time job to pay the bills. In short, I have a standard existence that I imagine many of my readers share. Living off noodles in a cheap apartment with my co-founders is not the only way that start-ups are built. I’ve taken an alternative route that involves just as much hard graft (harder maybe?) and allows me to remain employed full-time. The food sure is better!

Read more here: http://blog.gridspy.co.nz/2010/02/part-time-entrepreneur.htm...

Re:Every time an engineer joins Google, a startup dies by MrFoof on Thursday February 11, 2010 @05:25PM (#1118937)
> agree, and will add that kids are expensive, especially if you want good education.

These factors aren't linked if you're willing to put in the effort.

When growing up we lived in one of the worst parts of the state regarding school districts. Parents began to teach us how to read, write, and do basic arithmetic before we ever were sent to public schools. I think I entered first grade reading and writing at an 8th grade level and knowing long division. Took until about 8 years old for me to grasp basic algebra. They held back after that point, otherwise we would've had a mind-numbing experience until at least high school. However the school board was made aware that these first graders could be head of the 6th grade class, so we were allowed to freedom to learn other things (and sit in a few other classes once a week - mostly English, math and history).

Oh, right. College. That was our responsibility. They would help with loan payments a bit, but they certainly couldn't afford to even put us through a state school. We were expected to get scholarships. If we didn't, well, it was that much more we'd have to borrow.

Honestly, I can't blame them. We were certainly a lower-class family. They couldn't afford to move near a nice school district, private schools, or help with private colleges, so they decided to get us WAY ahead of the curve (even though I have memories of crying because at 3 years old I was having obvious difficulties with multiplication. ultimately we were incentivized with spare change). Even then, the nice school districts aren't all that great. What my folks did will still allow any child to get far ahead of any child in the best private schools in your area.

In the end we ended up with extremely large scholarships (that I didn't bother with because I'd still have to take out the equivalent of a home mortgage) and teenage years with an enormous amount of free time. Cost to my parents who only had a high school degree (mom) and a GED (dad)? Some of their free time every night.

Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:25PM (#1119542)
Cool story, it is good to look back on your childhood and be proud of the decisions your parents made.

As a parent though, you have to remember that even basic play has a very high value to children. My little 2.75 yr old has dinosaurs in the bath and can count one, two, three, four, lots. He knows the lifecycle of the butterfly.

But I'd much rather that he did what some might consider "useless play" and mastered his social skills and self confidence than any curriculum ideas such as maths or reading. Those can wait until he is ready, though he is a very engaged and switched on little boy.

I think that forcing your children to do certain things that you expect from a 10yr old now is just ruining their childhood and can reduce their delight in learning new things.

So be careful whose advice you take, even mine.

Re:Every time an engineer joins Google, a startup dies by MrFoof on Thursday February 11, 2010 @10:46PM (#1119686)
Actually, childhood was a blast. The first 8 to 10 years of schoolwork being completely trivialized meant I could be over at some friend's house every day, futzing around in the backyard, or playing with action figures and legos. All the time.

I have few memories of before I was 4 years old.

* Rolling around some cookie monster thing. * Being sick of flash cards. * Spraying my grandfather with the hose, and thinking it was hilarious. * The dog knocking me over to take the entire bag of snausages. * Playing random games we made up in the backyard with the kids next door.

How much do you vividly remember from when before you were 5 years old? I'm guessing not a whole lot.

Re:Every time an engineer joins Google, a startup dies by gridspy on Friday February 12, 2010 @01:21AM (#1119920)
Interesting thoughts about memory. My early memories aren't quite that good.

I never found school particularly difficult, and I didn't learn how to read or do maths until school. There is a good chance you wouldn't have found it difficult either - even without the flash cards. Perhaps you are just smart.

It sounds like your childhood was still fairly moderate, it is not like flash cards is the only thing that you did. My main motivation for commenting at all is that I don't want any other parents to get weird, extreme ideas.

Anyway, I think I better gracefully bow out of this discussion before I step on any nerves.

Re:Every time an engineer joins Google, a startup dies by jasonkester on Thursday February 11, 2010 @01:21PM (#1118294)
Ah, but if you have managed to make yourself ridiculously employable by proving yourself at a few high-profile companies, then you suddenly have "little to lose" again.

One of the reasons I feel like I can safely Entrepreneur myself down to a few grand in the bank before looking for a contract to top up the finances is that I know I'm pretty much a single Twitter post away from a good job offer.

Had I not first established a bit of a reputation before taking off on the startup track, I wouldn't have that safety net, and might be a bit more quick to grab any contract job that came along.

Re:Every time an engineer joins Google, a startup dies by gaius on Friday February 12, 2010 @12:01PM (#1121046)
Exactly. And having a "name brand" on your CV helps more than having been to a top college. 3 years at McK or GS and you will never have trouble getting anyone to take you seriously in business. It doesn't excuse you from anything important, but it does mean you don't need to waste time establishing your credentials to everyone you speak to.
Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:20PM (#1119532)
That is a pretty good safety net right there.

Though in some ways it is great to "burn the boats", because having your back to the wall and being forced to make it work (even if that involves a week of cold calling) can be the difference between success and giving up.

Re:Every time an engineer joins Google, a startup dies by huherto on Thursday February 11, 2010 @11:30AM (#1117944)
That is exactly right.

I wish to start up a company. Or devote more time to the companies that I already started. But mostly because I don't feel I fit any more in the corporate bureaucracy and politics that drains my energy every day. Yet it is hard to trade the security of a good paying job for the risk of starting up a company.

Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:27PM (#1119543)
Then the only other option is to go hell for leather on your start-up in your free time, even if that means you don't have a life. If it doesn't get you that fired up, perhaps you need to brainstorm a better opportunity.

I can't leave my cushy job yet either.

Re:Every time an engineer joins Google, a startup dies by ALee on Thursday February 11, 2010 @03:08PM (#1118609)
Same with startups. One moment you're in college starting a startup, the next you're 3 years older still doing the same thing. Startups are a more difficult path because they don't always have forward momentum because of the high risk.
Re:Every time an engineer joins Google, a startup dies by tetha on Thursday February 11, 2010 @12:02PM (#1118041)
Plus if it is a goodcrazy idea, chances are that it might be built as a google application.
Re:Every time an engineer joins Google, a startup dies by hello_moto on Thursday February 11, 2010 @10:26AM (#1117773)
I'd love to see more people to pursue this stream (Join Google, learn, and become a founder in the future).

There's a lot to learn from Google (especially in terms of code review, writing good, clean, well documented code).

Let's rephrase that: "Every time I see a brilliant kid going to a chaotic startup that encourage shortcuts and brilliant hacks, I see our industry dying slowly."

PS: I understand that not all startups are like that, but what are the odds/ratios?

Re:Every time an engineer joins Google, a startup dies by strlen on Thursday February 11, 2010 @03:43PM (#1118706)
There's a small caveat though. It may have been a clearly good choice to go to Google in early to mid 2000s, but since then there's already an incredible amount of legacy code written supporting business critical functions at Google. This isn't a criticism of Google at all, but it is a limitation on the new things you could do at Google or any other company with legacy systems. Working at Google doesn't free you from the responsibility (not just to yourself, but to the people using your work), as an engineer, to learn on your own what you aren't learning at your workplace.

That being said, I have incredible respect for Google for being a few engineering/science driven Internet companies out there, which respects great hackers and beautiful, quality code. Most Internet companies (including many startups, with few great exceptions) are solving social, rather than scientific or technical problems and treat developers the same way Google treats servers (as a commodity, where the ability to replace them quickly -- and make do if they're unavailable -- is more important than their quality).

Re:Every time an engineer joins Google, a startup dies by hello_moto on Thursday February 11, 2010 @04:13PM (#1118770)
Speaking about legacy code, I read somewhere (probably via twitter) that new hires were given Michael Feather's book: "Working Effectively with Legacy Code".

I have a lot respect to companies that acknowledge these kind of issues and try to fix them.

I know there are many companies that just tell the engineers to quit whining/complaining about the current system and keep patching issues (fire and extinguish).

Re:Every time an engineer joins Google, a startup dies by babycakes on Friday February 12, 2010 @09:53AM (#1120648)
They have me a copy of that book during my orientation at Google, along with a series of other books on the core languages used within Google. Obviously, it's up to every engineer to put that to good use, but the company is making an effort to have people do things the right way.
Re:Every time an engineer joins Google, a startup dies by hello_moto on Wednesday February 17, 2010 @10:28PM (#1133323)
May I know the titles of the other books?
Re:Every time an engineer joins Google, a startup dies by strlen on Thursday February 11, 2010 @05:44PM (#1118981)
That's very interesting! I'll have to check that book out (just given some of the open source projects I've dabbled in), anyone else have an opinion on it?
Re:Every time an engineer joins Google, a startup dies by vorador on Thursday February 11, 2010 @12:05PM (#1118050)
Not necessarily. After all, Unix was built by brillant kids who glorified shortcuts and brilliant hacks.
Re:Every time an engineer joins Google, a startup dies by strlen on Thursday February 11, 2010 @05:43PM (#1118978)
The other thing is that UNIX wasn't built a start-up, it was built at Bell Labs. Google could be argued t be a modern bell-labs.

Most modern start-ups avoid, at all costs, any systems programming (or doing anything at all beyond using a scripting language to read text from a database and display it on a screen).

Note, however, I said most. There are startups solving serious scientific and engineering challenges. It's just "start-up" does not equate "lasting technological/scientific contribution".

Re:Every time an engineer joins Google, a startup dies by nostrademons on Thursday February 11, 2010 @07:37PM (#1119249)
"Google could be argued t be a modern bell-labs."

Particularly given the ridiculous number of ex-Bell-Labs employees at Google. One of the SVPs of Engineering at Google was formerly the VP in charge of the organization that birthed C, C++, UNIX, etc.

Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:29PM (#1119545)
I think the key here is to avoid doing any work at all that is not your value proposition. If scripting languages are good enough and will benefit you, use them.

We use Python, Twisted, Django, Matplotlib, JQuery, Movable Type, Postgresql all for this reason. Even our firmware is built as much as possible on a 3rd party neworking library and high level hardware building blocks.

Re:Every time an engineer joins Google, a startup dies by strlen on Friday February 12, 2010 @02:04PM (#1121408)
That's great for you (if it's money you're after), but it does make the start-up fairly uninteresting to someone who's interested in systems level development (and not just glueing together a product based on work others have done).

Generally, top scientists/engineers are not motivated by money, which means given an offer from a typical ("glue a product together") start-up and Google they'd choose Google, unless they're looking for the "start-up experience".

If you want top technical talent (who will always be able to find fulfilling and challenging work at the whatever the current Google-like company is, e.g. SGI in early 90s, Netscape in mid 90s, etc), you have to give them top technical challenges (which is how these companies have themselves been able to compete for talent when they were start-ups).

Re:Every time an engineer joins Google, a startup dies by gridspy on Friday February 12, 2010 @09:07PM (#1122380)
Yes, that is my frustration also. I would rather be doing low level optimisation work, but I haven't yet found someone who wants to pay me for it.

In the next 6 to 18 months, I am going to have to start swapping out the big building blocks with parts meant to scale. At that point there should be plenty of room for the systems engineers to join me.

Re:Every time an engineer joins Google, a startup dies by strlen on Saturday February 13, 2010 @12:13AM (#1122592)
That's fine then. It's better to use high level components to build a product that's correct (i.e. does what customers want it to do well) and then make it fast then build a fast, but incorrect product.

Be careful, however, with treating scale as equivalent of performance. You have to design for scalability, not optimize for it: given the same algorithm, sorting a list of items in python might take 50 times as long as doing it in C; yet using an n^2 vs. n log(n) algorithm a 1 000 000 item list would take 50000 times as long to sort.

Re:Every time an engineer joins Google, a startup dies by gridspy on Saturday February 13, 2010 @06:13PM (#1123755)
Please excuse the tone of this post. I have spent a lot of time thinking about potential performance issues, and rationalising my choices.

I'm a ACM ICPC (programming contest) finalist, and have competed in the Google Codejam, so I know about big-oh.

Anyway, who implements a sorting algorithm in pure Python? I use the builtin sort() function, which is implemented in C (making callbacks into python for comparisons for some types). It uses TimSort - an approach designed to minimise the number of comparisons. http://svn.python.org/projects/python/trunk/Objects/listsort...

I thought you were going to point out that I should ensure that my system is modular (stateless, partitioned, etc) and I can spread the load across several machines - I can.

You are right that I could make a screaming fast bubble sort and still end up with major issues. Fortunately I already have had that epiphany while solving ACM practice problems.

I appreciate your advice, there are far too many who haven't yet understood it.

Re:Every time an engineer joins Google, a startup dies by strlen on Monday February 15, 2010 @07:21PM (#1127937)
Sorry if I sounded condescending. I didn't know the specifics of your system (is it mostly on the server side, embedded, etc...?) so I couldn't give you any specific advise.

The sort example was merely a metaphor for design for scalability vs. optimization for performance. Perhaps better examples would have been dividing the server side portion of your application into asynchronously invoked services is design for scalability. Rewriting some of these services in C or OCaml, switching from JSON to Protocol Buffers, switching from an HTTP server and a layer 7 load balancer to a custom non-blocking server and ZooKeeper (for cluster membership) are optimizations for performance/stability/cost.

Re:Every time an engineer joins Google, a startup dies by strlen on Thursday February 11, 2010 @02:00PM (#1118431)
I understand this is an ironic thing for me to say, given my alias, but is UNIX (along with C and C-descended languages) the best we could do?
Re:Every time an engineer joins Google, a startup dies by peterwwillis on Thursday February 11, 2010 @02:29PM (#1118506)
For the PDP-7/11? Probably.
Re:Every time an engineer joins Google, a startup dies by strlen on Thursday February 11, 2010 @03:34PM (#1118681)
Certainly agreed, it's amazing what they've accomplished on such limited machines, just it shouldn't be held as a pinnacle of engineering or computer science (else, why would the people who built it be at working on plan9 and go?)
Re:Every time an engineer joins Google, a startup dies by jmtulloss on Thursday February 11, 2010 @04:01PM (#1118737)
The best we can do is usually not the goal. Good enough is the goal.

People look at great products and say that sentiment isn't true, but you always have to release. Take the first iPhone. When it came to feature checklists, it was embarrassed by every competitor out there. It nailed the interface though, and that was Apple's definition of "good enough". The shipped, took the industry by storm, and have since added most of those checklist features that everybody thought they needed in the first place.

Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:30PM (#1119548)
Every feature you add makes the menu more complex.

There comes a point where removing a feature is itself a feature.

Re:Every time an engineer joins Google, a startup dies by hello_moto on Thursday February 11, 2010 @04:09PM (#1118759)
Were they kids though? I thought they already grew beards and some might have a tiny bit of grey hair here and there...

There may be beautiful hacks in UNIX but the building principals (UNIX Philosophies) lives on and I don't think kids these days that go straight into startup even know these things.

Re:Every time an engineer joins Google, a startup dies by kvs on Thursday February 11, 2010 @09:00PM (#1119494)
Don't go into Google to learn to code. Go into Google to learn to lead. That's what you will need the most as a founder.
Re:Every time an engineer joins Google, a startup dies by mortenjorck on Thursday February 11, 2010 @10:54AM (#1117859)
1. Get recruited by Google

2. Work at Google for a few years, start a 20% project

3. Leave Google, become a founder

4. Get funding, hire more employees

5. Launch a successful product, build a big userbase, get favorable media coverage

6. Get acquired by Google

Re:Every time an engineer joins Google, a startup dies by jules on Thursday February 11, 2010 @11:50AM (#1118013)
Isn't the 20% product owned by Google already?
Re:Every time an engineer joins Google, a startup dies by ejames on Thursday February 11, 2010 @12:15PM (#1118075)
Yes, but once you're "the guy/gal who wrote $SUCCESSFUL_GOOGLE_PRODUCT", you have a lot of credibility, experience, etc. as resources to make your own product that you do own.

The point of the 20% products for Google is to give the company startup-style flexibility. It works the other way, too - if you take a product from whiteboard doodling all the way to an official Google product, well, a startup is like that, except 100% of the time, on your own bank account, and with no admins/middle managers to take care of the business side for you.

Re:Every time an engineer joins Google, a startup dies by gridspy on Thursday February 11, 2010 @09:32PM (#1119555)
Yes, but given the 20,000 employees at Google, how many $SUCCESSFUL_GOOGLE_PRODUCTs have you seen per employee?
Re:Every time an engineer joins Google, a startup dies by mortenjorck on Thursday February 11, 2010 @12:27PM (#1118117)
I'd guess ex-Googler startups tend to draw more from their founders' general experience at Google than from specific products, but I've heard of rebooting the idea of a 20% project outside with a broader scope.
Re:Every time an engineer joins Google, a startup dies by bgraves on Thursday February 11, 2010 @01:21PM (#1118293)
Interesting timing :) Looks like this is what happened with Aardvak. I'm just speculating, but the formula seems to hold true in this instance.

http://news.ycombinator.com/item?id=1118214

Re:Every time an engineer joins Google, a startup dies by dasil003 on Thursday February 11, 2010 @11:27AM (#1117934)
Funny you should mention Goldman Sachs. The startup I work for is founded by a former Goldman guy, and I'm looking out my apartment window at a startup founded by a bunch of Google guys (BloomReach).
Re:Every time an engineer joins Google, a startup dies by iron_ball on Thursday February 11, 2010 @11:54AM (#1118026)
Not to mention that if you're successful at Goldman Sachs, you can quit and spend the rest of your life doing startups and still have enough left over for a golden pyramid when you die.
Re:Every time an engineer joins Google, a startup dies by frederickcook on Thursday February 11, 2010 @11:24AM (#1117932)
I think the fact that this comment keeps getting up-voted is an indicator of the high ratio of Google employees to startup founders on HN this morning.
Re:Every time an engineer joins Google, a startup dies by sjs on Thursday February 11, 2010 @11:05AM (#1117883)
Not to mention that startups can't do everything a company the size of Google can (such as start their own ISP providing gigabit service).

There is a place in our society for all shapes and sizes of companies.

Re:Every time an engineer joins Google, a startup dies by frederickcook on Thursday February 11, 2010 @10:53AM (#1117855)
I absolutely disagree. With YCombinator and the dozen similar programs out there, the traditional barriers to starting companies, namely "not knowing what you don't know" are being removed. For a web start-up especially, the only cost associated with the startup for a group of young founders is time.

The goal at Google, Goldman Sachs, and McKinsey is to recruit top talent, and give them enough money and benefits that they are completely content and never have a reason to leave. Some still will, but most are probably destined for a career as a middle manager.

Re:Every time an engineer joins Google, a startup dies by wakeupthedawn on Thursday February 11, 2010 @11:12AM (#1117910)
Maybe this is true at Google, but you need a fair amount of dedication to stick around at Goldman or McKinsey. Nobody becomes a career middle manager there. Well, maybe some back-office jobs at GS.
Re:Every time an engineer joins Google, a startup dies by silverlake on Friday February 12, 2010 @10:50AM (#1120818)
According to friends at Goldman, it's quite easy to be a career middle manager at Goldman in IT. There are many people there for 20+ years, the only job they've ever had.

I've been told that McKinsey has an "up or out" culture (get promoted or leave).

Re:Every time an engineer joins Google, a startup dies by dagw on Thursday February 11, 2010 @10:27AM (#1117780)
Exactly, most truly successful entrepreneurs I know had a few (or a lot of) years in a larger company before starting their company. This gave them not only vital experiences, but also a lot of insight into the problem which their company tries to solve.
Re:Every time an engineer joins Google, a startup dies by mattm on Thursday February 11, 2010 @03:51PM (#1118720)
Including Steve Jobs (although I'm not sure on the number of years for him)
Re:Every time an engineer joins Google, a startup dies by mkramlich on Thursday February 11, 2010 @10:33PM (#1119668)
And gaining contacts and cash. Which in turn help him later to build a startup. So I agree, it's not all bad.
Re:Every time an engineer joins Google, a startup dies by rbanffy on Thursday February 11, 2010 @12:35PM (#1118139)
Don't forget Microsoft.
Re:Every time an engineer joins Google, a startup dies by Sukotto on Thursday February 11, 2010 @01:50PM (#1118404)
Looking back over the last decade, it seems like Microsoft is a lot closer to IBM than to Google.

People don't go there to learn how to innovate. they go there to work a full-time job for the rest of their lives.