5 ms·
Everyone has different reasons for their choices, but speaking only for myself, none of those things matter much to me. Here's why I'm currently at a big compan
by luu 13y ago
Everyone has different reasons for their choices, but speaking only for myself, none of those things matter much to me. Here's why I'm currently at a big company instead of a startup (and I've done the startup thing in the past, so I have some idea of what I'm missing out on):
1. Research-y projects. Big companies have the resources to place long-term high-risk bets on research projects that will probably fail. Some startups have a single such high-risk bet, but you can't just decide to work on whatever crazy idea you come up with because the company can't really absorb your salary for years if the bet doesn't pay off.
2. Really broad scope. One cool thing about working at a startup was that I could do whatever I wanted as long it was relevant to the startup. In fact, that was the biggest reason I went with a startup just out of school; I would have been some tiny cog on a giant team at a big company (that's not inevitable, but that's what the offers I personally had entailed). But I now have enough credibility that I can go off and do whatever I want at a big company. Since the big company has a much larger scope than a startup, there are many more things I can work on.
3. Resources. At the startup, I could take 100 machines to run an experiment and it wasn't a big deal. If I wanted to use 1000 machines I'd have to get people to ok it because I'd be eat into resources that were necessary for the company's operation. Now, if there's something I'm curious about, I can run a map reduce across the entire internet.
4. Relaxed environment. The vast majority of my team is married with kids, so the office is deserted by 5pm. There are a couple of folks I've seen stay late for a week or two to hit some deadline, but that's like one or two weeks out of the year. The startup was one of the most relaxed startups I've ever seen, but there were still month long crunches of 50+ hours/wk as some emergency came up. In principle, a startup could be as relaxed as a big company, but that's extraordinarily rare. At the big company, one of the most respected people in the office casually remarked to me that he's been at negative available vacation for all but his first two weeks at the company (and he's been here for seven years). At the startup, the most respected people all lost vacation every year because pushed up against the vacation cap.
5. This should really be like 25 or something, since it's not in the same league as the others, but I'm making a lot more money than I was at the startup.
Don't get me wrong -- there are a lot of advantages to being at a startup, and I'm glad I spent a good chunk of my career at one. I'm just saying that there's a lot I'd have to give up to go back to a startup, and the things on that list don't even make the top 30.
- rfnslyr 13y agoWow that's awesome. I work at a big bank and we have none of those things. Everything is shit and I can't wait to leave. Our mobile development environment is a locked down internal Windows XP laptop that doesn't let anything in or out, so we had to write our own tools to package code to leave the laptop. We wrote a simple little "chat" client in Node, but before sending the code off, it was packaged into a .jpg, and unpacked on the other side (my development macbook). This is how we've been dealing with code for over a year now. Shit pay, 0 resources basically. Can't wait to leave.
- artmageddon 13y agoI've been there(working at a big bank with a lackluster development system), so I know how it feels. Keep pushing and get yourself out!
- blibble 13y agoI work for a large bank, and whilst my desktop is completely locked down, our development is done on remote (but still internal) boxes where we're essentially given free reign. each team is essentially autonomous, and they pick the tools they wish to use. yes, there is lots of paperwork, e.g. getting anything deployed requires multiple people from across the firm to agree, but it's mostly automated and doesn't take more a few hours of background time, and it's understandable: the amount of money the firm would lose if something went drastically wrong is eye boggling. the problems are challenging and interesting, I get to experiment with extremely high end equipment that isn't available for general purchase, and the hours are good (as is the pay). (though I admit there are parts of the organisation that don't have this freedom: you have to be careful when interviewing)
- ExpiredLink 13y ago> each team is essentially autonomous, and they pick the tools they wish to use. This will lead to a maintenance problem shortly. I worked in similar environments. Technically clueless managers think that they only have to throw requirements over the wall and let the developers figure out how to implement them. When someone leaves the team the replacement needs to become acquainted with totally unfamiliar code, libraries and tools.