7 ms·
I think you've also just well described so much of startup software development as well. Great ideas, a grand pool of undiluted computer science theory, nobody
by falcolas 10y ago
I think you've also just well described so much of startup software development as well. Great ideas, a grand pool of undiluted computer science theory, nobody going "why do you need 120 servers to run a webpage?"
- jacquesm 10y ago> Great ideas, a grand pool of undiluted computer science theory, nobody going "why do you need 120 servers to run a webpage?" I actually untangled a mess like that (only it was some 200+ VMs on 20 fancy HP blades + SAN to serve 5000 users daily), don't even joke about it. If you arrived with something the size of a semi-trailer to squeeze some juice people would likely ask you if you're all ok in the upper department but if you do the same in computer land they call you 'architect' and promote you. So much of that complexity is hidden and your average business owners have no clue what is required and what is overkill.
- spydum 10y agoThe great sadness to me is that incentives in architecture almost encourage this... Hardware is cheap and good designers are few. So when guys like you can come in and squash down the complexity,, company thinks it won twice (first time for delivery.. Wow look how fast it is!; second time for efficiency)
- jacquesm 10y agoI strongly suspect there was more at play there (huge kickback to one of the people ordering the hardware). And no, the customer didn't think they won twice, the first time almost killed them. For all those goodies it still did not perform. You really wonder how they managed to burn all those cycles.
- ams6110 10y agoSo why is it then that 23 year old engineers are building everything in SV? It certainly explains a lot about what I see happening there.
- cheriot 10y agoThey have less to loose (already broke), are not accustomed to nice things (never experienced a real salary), and are enthralled by startup culture (so they'll accept shit equity and work all night). There's also a bias in which ones we read about. Nobody puts the age of a 40 year old founder in a headline. I think PG wrote an essay on why ycombinator started out primarily accepting new graduates, but I can't find it right now. Clearly he had a different take.
- onion2k 10y agoHiring ten 23 year olds and paying for 20 servers is cheaper than hiring five 40 year olds and paying for 3 servers. It only becomes a problem when you need to stop burning money, because you can't easily reduce the hardware cost.
- repomies691 10y agoAlso have to take into account that hardware is ridiculously cheap nowadays. You can rent quite a lot of raw computing power with the salary of one engineer.
- Cthulhu_ 10y agoNot to mention one engineer can spin up and operate a big horizontally scaling cluster.
- deleted 10y ago[deleted]
- TuringNYC 10y ago23yo engineers are often also willing to bunk up with three friends in a two bedroom apartment, which makes living in SF/SV more feasible. Once you have a family (generally, older engineers) you generally dont want to be sharing an apartment, so your minimum salary requirements go up.
- hinkley 10y ago
- quasse 10y agoI've worked professionally in both fields now, and luckily mechanical engineering seems to have a much less toxic attitude towards for older engineers. The amount of ways an experienced engineer will know not to do something is mind boggling and I am definitely still learning.
- diydsp 10y agoYes, elec engs are essentially hobbyists until completing their second decade in industry. Then, watch out! Most places I've been realize this, but a few, hint mainly sw shops, think 5 years exp suffices. And they suffer arching in pain. It hurts to watch.
- cbsmith 10y agoThere's a truth about this in software too. It's just not recognized.
- sidlls 10y agoNot just startup development. The entire software industry, aside from a very select few, seems to me to be plagued with this sort of immaturity.
- kabdib 10y agoYou can be immature going the other direction, too. "We need to squeeze every last cycle of performance out of this server before we buy another one." Well, sometimes you do (when it's someone else's hardware, perhaps). But often, happiness is a middle ground. Most hardware goes through phases, often planned far in advance: The expensive first version to get something out the door, then a series of cost reductions (bring many chips into a single custom chip, ditch unused features, get new vendors for subsystems) which improve profitability. That juicer looks like it was designed to withstand a direct hit by a bunker buster. Nobody gave a damn about profit margins or ever making it cheaper, I think they just wanted to IPO or get bought.
- sidlls 10y agoWell sure immaturity exists in every axis. I've seen "performance zealots" seriously suggesting moving a perfectly functional internal flask based API into some obnoxious, bloated Java Spring something or other to squeeze performance out of it. The thing served approximately 1 (internal) user at a time at a rate of less than 1 request per minute on average and was a read-only API. Flask was just fine for the purpose. I've also been guilty of this in my younger days, where I was very much "C++ all the things because performance." But that's kind of my point: it's immaturity at work, here.
- marssaxman 10y agoWell, sure, that's because this industry has spent the last thirty years growing like gangbusters. Give it some time to settle down and you'll see the mix of newbies to veterans balance back out again.
- pbreit 10y agoEverywhere I look, engineers are over-engineering everything. I just don't get it.
- killjoywashere 10y agoThere's a few reasons for that * no one ever got hired for under-engineering * a lot of people have died from under-engineering * you never notice how much was engineered juuuuust right (tm). Because it was. Just. Right.
- bluedino 10y ago>> * no one ever got hired for under-engineering I've bought plenty of low end products from China that I'm sure were intentionally designed as cheaply as possible with no regards to quality.
- killjoywashere 10y agoThat's not the same as under-engineering. They simply engineered for a different target. The engineering of the product is only part of the issue. The bigger issue is engineering the entire production system. They may well have optimized for maximum return on investment in the factory, not maximum quality for your headphones.
- i336_ 10y agoThis fact underpins so much inanity fundamental to modern life nowadays D:
- acdha 10y agoThere's a large social component, too: beyond simple resume-driven development engineers get social status by doing interesting technical challenges. You rarely see a project make the front page of HN, for example, because it has a really polished UI and great documentation. Since that's what the community generally respects and focuses on, people seek out areas to add complexity – who wants to work on a boring “solved” problem? – and, especially younger engineers, often feel they have to do things the same way Google or Facebook does (it's web-scale!) even if they have 0.001% of the engineers and 0.000001% of the traffic. It's easy to miss that most people with similar problems have so much less volume that they aren't forced to do the really cool (i.e. expensive) engineering and, since they're using something stable, it's not considered interesting enough to talk about it.