Silicon Valley startups rein in spending and prepare for layoffs
cnbc.com
cnbc.com
> Margaret Quigley, 27, a techie with some coding experience, is on the hunt for a job in San Francisco.
> Quigley, who previously worked at a popular consumer start-up, has been job hunting for five months. She recently rejected one start-up's offer, a one- to two-month tryout — without pay. Quigley said she has also rejected multiple sales job offers and an offer that was in the right field but came in too low.
I'm sorry but... what? Not everyone can do software development. This bit makes it seem like any person who is considered a techie can now land a cushy job.
If you don't know what you're doing, expect really bad offers. Maybe take an internship and make a name for yourself. I had to work basically minimum wage for about six months at my first startup gig and that propelled me to what I'm doing today. Not sure what that bit was about.
> It's a tough time to be job hunting in Silicon Valley, and things are about to get a lot harder for individuals with certain skills.
I just got a job in the Bay Area so again, I don't think these are valid points in this article.
An offer for a one/two-month tryout without pay has nothing to do with their skills. That's just someone trying to get some cheap labor.
I don't see any reason why it has to be without pay. "Under market" maybe but not without pay.
can yin define this; this means that knowing that you now make a lot or you don't make enough??
also, the above, regardless seems to me to only apply to those newly entering the workforce as opposed to those that, like me have 20 years in tech and three kids....
no way would I think three months "trial" was anything other than shady slavery
I'm assuming she's not on the hardware side.
"Techie" is such a vague term.
I'm guessing they're talking about the "startups" who hemorrhage money on a trendy office location and uncomfortable chairs.
It'd be cool if we had a different name for being several rounds deep, private, and profitless.
For examples, I didn't even have to leave the linked article:
- The link off the article: "Silicon Valley's reality: The party is over"
Yes, the whole 16 hour work-day for potentially valueless-shares "party." Excuse me if I'm not wearing my party hat. You'd never see "Coal miner's reality: The underground rave is over", nor would you see them taking a shot at executive compensation in the banking industry.
- From the article: "Margaret Quigley, 27, a techie with some coding experience, is on the hunt for a job in San Francisco...there is literally Airbnb — for cats!...'Do I see value in the platform?'.. she has also rejected multiple sales job offers"
Ah yes, the non-programmer vague "sales techie" living in the modern day political and corporate Gomorrah and a trivialization of the tech industry. Yes, quip about some startup no one has heard of and avoid talking about a company like SpaceX that is inarguably changing the world by doing things at the scale of NASA.
- "The candidate wanted more money, the opportunity to work from home three days a week and to set the hours. Six months ago the company scrapped free in-office yoga and massages."
Again, trying to paint tech workers (with these demands, he/she was likely an engineer) as spoiled, pampered children.
The rare/uncommon perks exist because it's hard to find people capable of doing the engineering work, and once you find those people, it's very easy for them to be ground down to a nub. Funny that CNBC isn't brave enough to talk about the perks that politicians receive from lobbying groups.
For I find the perks exist less to attract engineering talent and more to achieve that perfect blend of easy party money and college party life that serves as a nearly 100% efficient system of wealth redistribution from the top 0.01% to the top 10%. That said, I think the disappearance of facebook and twitter from the Internet would be approximately as inconvenient as a philosopher's strike.
"Script kiddies new reality: amateur hour is over."
The media calls these large companies "startups" because the companies themselves do it. Because it makes them sound hip and trendy and worth investing in.
No doubt there are companies like SpaceX doing notable stuff. No doubt they are a minority. AirBnb for cats exists. Vessyl exists.
Well, remember what working in the media is like. It's an industry where writing opportunities are contracting, advertising is stronger than ever, pretty much all but the top tier of newspaper is writing clickbait, it's perceived that there's little prospect of it getting better, and they compete with Congress for major institution least respected by the public.
I wouldn't consider schadenfreude a paranoid theory, I'd consider it the expected outcome. It's hard to avoid wondering how much of the general tone of opinion in the media is a direct reflection of the fact that they aren't doing well. (Are they worried about the "1%" precisely because a couple members of the .01% are buying up their entire industry, and they see the .01% showing up in the reporting chain? I've seen people similarly wonder if part of the reason academia is so pessimistic in their writing is that their world really is in terrible shape and the sense of immanent collapse is scaring everybody.)
The media's skadeglädje for tech could be because tech made media worthless. Easier than ever for anyone to publish stuff and block ads.
I think you have a very misaligned perception of the general world. Most people don't even know what a startup is unless your in a major city and the perception is pretty positive overall.
The job market is really great right now. If you're getting laid off, now is a good time.
Getting hired is not a problem - getting a really nice job though is much more difficult, especially due to all of the companies that like to talk a nice game but are disguising weak aspects of the company such as leadership/management, quality engineering, work-life balance, etc.
An aside, that popup iframe with video on the top as you scrolled down is one of the most annoying dark UX patterns I've encountered in a news site. It is one of a handful times where I used Chrome's element inspector to set display: none.
Can you explain this further? If by "high demand JS engineer" you mean "front end" and not just node (which is not bad or anything btw), and by "high demand" specifically you mean you are: * you understand JS well, doesn't mean we get to grill you on all the weird corner cases - but you understand the language * want to work with a modern stack (i.e. react, flux/redux/whatever, backbone, that sort of thing) * are mature and want to help grow a team, can communicate with PMs and all that effectively
we'd kill to hire you (250-300 person company.) Every friend of mine that has started a company asks me every time they see me if I know a good front end person (that isn't busy counting their RSUs at Uber, etc and isn't going anywhere.)
Our company (in general) and team has more than one designer focused on bringing a good experience to the table, before it even gets to the code level. To translate, that doesn't mean our reqs go from sales person to "make it do this now, code monkey", but rather we want to make good, long lasting products, in a thoughtful manner. And still, finding someone is tough.
So I find it hard to believe the hiring market for what you describe isn't great.
Personally, my experience is all back end. I consider myself a good engineer in general, and feel I could ramp up to being a decent front end engineer in 3-12 months time depending on how much depth we're talking, but think that things are specialized enough now that that would be a waste of effort, and plenty of people would still be better than me. However, from what I've seen, being a F.E. eng that understands CSci and what's happening under the hood should make you SUPER in demand right now.
I'm not trying to make this a hiring post, but if you'd like a fun job with a decent company trying to expand its front end capacity on this coast, with a relatively green field project (i.e. you get to build new stuff), and at a place making real money, not just selling to other startups, and not in a moon shot social space, PM me. If not, I'd still be curious why you think being a "high demand JS engineer" isn't a good spot to be in in the current market.
Finding a job is still pretty easy - I don't dispute that. Finding one that pays competitively, respects work-life balance, and focuses on quality of engineering & getting product right, even if it means pushing deadlines a little later is much harder I've found, unless you look to the Google/FB/Netflixes. My current job meets most of those bars (a little less on the salary side, but I was willing to accept that for everything else), but only dissatisfies me on wanting to move faster & having more influence on tech choices.
While there are no shortage of companies that want to hire, most haven't put their best foot forward I've found. The market is still good for software engineers, but it's noticeably not as compelling as it was just a half year ago - I feel like the balance has tilted a little more to the employer's side in the employee/employer dynamic.
I left Zenefits in December and had three job offers after about a month of looking, and they were all high-growth Series B/C startups.
Happy to connect you to any of the places I talked to if they're interesting to you, contact info in profile.
I honestly hope these companies start culling these non essential employees. When I left the valley, they were one of the biggest reasons. They were affecting the local intelligence culture in a very negative way.
As a developer, I appreciate the role recruiters play. Reaching out cold to people isn’t easy and the fact someone else spends time on this while I write code is great. And the fact that my LinkedIn has multiple leads from people about job opportunities should I want to move is fantastic. Are we so spoiled to scoff at people offering us jobs when so many people can barely find quality work.
Certainly there are some shady players, but not really more than I’ve seen on the Engineering side, and my main issues have been less with recruiters and more with the hiring managers who the recruiters work for. “Oh, your rocket ship hasn’t grown revenue for 6 months straight yet you told me 100% YOY growth.” It was two directors of engineering and not a recruiter that lied to me about growth at a well respected YC startup. I blame the people crafting the message more than the messenger.
Prices won't really go down unless people are forced to sell.
That said, I have sympathy for the LinkedIn engineers who were holding all their stock for a down payment. That's gotta hurt.
Both kinds of demand could easily be clamped down upon by raising property taxes - the victims of which would be wealthy foreign investors and people who have sat on one of the largest increase in property values in history.
Likewise, supply could be increased if local government were at all interested in doing so just by building 10,000-20,000 low income apartments.
If the government announced both, the cost of San Francisco housing would plummet within days.
We have this problem in Boston right now. We're building and it's doing nothing to the rents because it's being snapped up by foreigners.
Also, sales are open record - you might look at buyers with Chinese surnames that lack Americanized first names.
We've been here before: back in the 80s, Japan was buying up most of the real, tangible assets in the U.S.
http://www.businessinsider.com/japans-eighties-america-buyin...
The cause was the same: strong export products, an undervalued currency, and easy-money policies. The first signs of trouble were the same: high inflation, crony capitalism, and poor transparency in the market. Let's see if the rest of history plays out the same way.
"Average annual wages in high-tech rose sharply between 2001 and 2008 compared with overall average wages in the Valley. For the Silicon Valley, the average annual wage in high-tech industries rose from $97,344 in 2001 to $132,351 in 2008, an increase of 36.0 percent. (See table 2.) In comparison, average annual wages rose only 21.7 percent across all establishments in the area"
http://www.bls.gov/opub/regional_reports/200908_silicon_vall...
If a company goes bankrupt and it lays people off, it doesn't mean that salaries all fell, it just means those employees' salaries dropped to $0. This is what happened to you. I got modest salary increases during the same time.
http://www.bls.gov/opub/regional_reports/200908_silicon_vall...
If the data for this specific range is available, I'd love to see it. Perhaps I missed it.
This is not what happened to me. I kept my job, but my salary went down.
Various companies also enforced extended shutdowns (over Holiday periods). If you had no vacation left, you didn't get paid. This is effectively a wage cut.
I am aware that wages are "sticky" and companies would rather lay off than cut salaries. But the statement that "wages did not go down" is not correct.
The reason why they didn't is because they didn't want to give an arbitrary pay cut to their best employees, who would leave as soon as things got better. They would rather cut the fat and get rid of employees they didn't want.
Google, Yahoo, Amazon, Cisco, Oracle, etc, none of those companies instituted pay cuts, and wages did not go down in those companies. Some of them had layoffs but they cut salaries.
I wish someone actually had data for the time in question, as opposed to anecdote. I find the question quite interesting, and would like to know the answer.
If technology professionals ever find themselves in a position where minimum wage regulations are relevant to their incomes, we'll have been through something far worse than a few layoffs.
The myopia of tech people is really mind-blowing sometimes...
EDIT: phrasing.
No. Engineers are spoiled during up time because the market, so we have to bear the correction during down turn which is also from the market.
Yeah, no. As someone who hires on the east coast, and has a pretty extensive network of professional peers in generally "high" positions -- all these general assumptions about applying the SF market to anywhere else in the country is complete non-sense. And rightly so.
When leaner economic times come around and tech companies downsize their work forces, they speak about culling "nonessential" employees and "growing smarter". How do they deal with the political problems of admitting to having hired a sizable number of "nonessential" employees to begin with, and, moreover, the obvious implication that their previous growth strategy was indeed "stupid"?
Times go bad, revenue drops to 10 million. You fire the non-essential designer and take the 1%=100k revenue hit. If you had fired an essential employee, your revenue would have dropped some double digit percentage, so those you have to keep around.
You expand/contract the business to the point where the marginal employee costs you the same as the marginal revenue they can bring in.
Well that's the theory for stable profitable companies. For startups I guess you'd have to think of the marginal expected future revenue.
Of course that is hard to measure. It's all hard to measure.
"Wow. Usually it's just a figure of speech when people say 'I don't know how to say this.'"
When the price of oil tanks, but the price of coal rises, you downsize on oil production and ramp up coal mining.
I think it's a valid question whether that's still a valid approach in a modern, high-value knowledge economy (and yes, I'm including oil well operators in there).
Honestly interested from companies that have been through grow-shrink-grow. Is it as clear as that, re: being able to find new people when the time is righr? Or is there enough of a ramp-up time for new employees that the equation is more complex?
I think oil is actually complicated and rare enough that it might actually be an example where you don't want to lay them off, since finding replacements may be quite hard if you lay off those positions for a few years, so you may want to try and weather the storm while the Saudis flood the market with oil.
Having said that, companies make bad decisions all the time since making good decisions is a lot harder than everyone seems to think.
I have a devshop and have sent his over and over again. The actual cost per employee isn't really paying them salaries to do stuff, but rather the salaries you pay them to learn stuff and get acquainted with the system. We call it ROL (Return on Learning). We've learned that on average it takes 3-8 months for an intelligent person to become fully productive within any system.
Since we started hiring for the capacity to learn and culture fit, rather than existing technical skill, it's changed our business for the better.
That said, turns out even if you're in the Bay area with all that great talent pool, chances to find local people who just happen to want to work with you are practically nill. Once you truly internalize this concept of ROL, there is no other way but to work globally with remote people and teams. Without that, you can't access a sufficiently large talent pool.
I think the ROL is actually the leverage factor people have in mind when they say "10x" engineer.
The amount of un- or poorly-documented things in decade+ legacy systems can be a minefield, but so easily solves with a quick "Oh, X, we always do Y because Z."
I've heard of companies doing the opposite. Instead of laying off, they hired more. Sure, you cut shot term cost by firing, but you also lose the human resources to develop any long term value. What of your product? If every of you competitor is laying off, and you decide to actually hire more and double down, you might be able to get the competitive advantage.
1) any employee who asks runs a good risk of getting fired, so they don't ask. If anyone is crazy enough to do so, what I've seen happen is this : everybody immediately looks at the guy asking, wondering if he'll get his head lobbed off. Everything goes very, very quiet. Management moves to the next question as if nothing happened. The guy is never heard from again.
2) any shareholder who asks approved the stupidity (this, of course, doesn't stop them from blaming others, but generally not publicly).
3) the big shareholders, who make the decisions, control who can film the shareholders meeting and who can report on it, and they make sure reporters who get to enter agree beforehand on what questions to ask. This means that if you go to a shareholder meeting of a large company, you'll see that question asked, and usually it turns the whole meeting into a shouting match (and once, I've seen it turn into an actual fight). Then the next day you open the newspaper or online sites and read a reporter describing a serene and cool meeting echoing almost exactly the press release of the earnings.
Management of long-running companies is stupid. Management that just left long-running companies is stupid. Well, perhaps stupid isn't the right word, but they're looking for very specific outcomes, which don't usually have anything to do with running the business well. Poking holes in how they're running things is easy, because people who do the hole poking are looking at the interests of the business itself, not of the people investing in it (they may want an exit, or even an entry : they want to buy extra shares, so it'd be real helpful if a "medium-size" business disaster happened).
And why not hire smarter management ? Senior management isn't hired (in most cases). They buy themselves in, then get to write the "reason" they get hired. It's never that they paid good money (usually in the form of shares, so technically they loan money to the business). Note that senior managers often don't use their own money to do this, but money of people they represent. Very often risky bank loans come with the string that a board seat and a C-level position must be given to a "to be named" individual.
(If you're working for a startup that got a bank loan and a sudden "weird" executive, I guarantee you this is what's going on. Same for investments. A good thing is that companies like Andreesen Horowitz are pretty forthcoming with that this is a requirement)
So the purpose of management generally isn't to run the business. It's to make the balance sheet look good for the duration of his investment. Making sure a loan is repaid at all costs. Making sure their company gets a good opportunity to buy shares (ie. break out news that kills the stock price, then sudden takeover happens, or at least gets closer)
Also, keep in mind hiring is partly done because open job openings that change regularly is something a lot of investors look at. This is one of the value-investing tricks in the category of tricks that everyone knows about. So it is gamed.
Not every company is running like this of course, but as a general rule, any company older than perhaps 20 years is. Or, more generally, any company whose stock has at some point really stalled is run like this. It'd be more accurate to say that any company that ever needed a bigger loan than their rating would justify is, but that's a very tough call to make.
Read this for an especially egregious example, bordering on fraud (but it isn't fraud. They never lied about the numbers, they just changed them so people who don't dig deep would see a huge improvement that wasn't real ...) https://foragerfunds.com/bristlemouth/dick-smith-is-the-grea...
When everyone and their buddy is signing up to spew cash into the coffers of services like Amazon, Heroku, and other hosted solutions (instead of doing it themselves), those services can spread and grow.
What happens, though, when that easy cash is no longer available? What happens when, for example, paying a lot for Docker or NPM no longer makes sense?
The outflux of customers has the--in some sense--real possibility of killing those businesses for the remaining users. Look at Github, for example, as a company trying to run ahead of the curve--it can happen.
I'm more concerned with what happens to ecosystems, like Node, that have VC-fueled companies as critical components.
I'd love to hear other opinions on this point of view.
If a company could inflict so much damage in the broader ecosystem by when it goes out of then it can charge high prices for what it offers. As a general rule if you're providing something people sttruggle to function without. then you can always stay in business if you want.
Of course, there are edge cases involving mismanagement, but I suspect they're extremely rare.
Perhaps what might be more likely would be acquisitions where the acquiring company kills the service for some reason - like what happened with Parse.
More seriously, they're trying to move into the enterprise/private space--but they took on a hell of a lot of funding to accomplish that. Not looking great for the good guys.
Performance benchmark summary: ("1X" is AWS)
Compute:
VMs Price: 30% less
Boot time: ¼ X
Network between VMs: Same region: 4X Across regions: 10X
BigQuery vs Redshift : ½ -20X
Big Data (Hadoop and Spark): 3X
Disks: Read throughput: 1X Write throughput: 4X (Ephemeral); 2X (Persistent)
Local SSDs: Read throughput: 8X Writes throughput: 4X
Storage (S3): Throughput: 2X Latency: 3X (initial); ½ X (for subsequent reads)
Tightly run ships, like smart remote companies without as much office space (lower salaries outside SV) or many employees or even generating revenue run will probably not even feel a blip in most cases. It is the ones that are a while from a product and paying the higher tag for office space, salaries and more for the chance to get funding in SV. If that funding isn't there for a while it could be problematic and is the risk with boom/bust cycles.
I'm curious, as I have no experience in this area, if that's really likely.
As an outsider, it feels like salaries would be the overwhelmingly largest monthly expenditure for most tech startups. Such that things like office space, even a lavish choice, wouldn't really be relevant.
If you were to break it down by "cost per employee" is there really a case where office space, perks, etc, really becomes the driver for failure? Where it is statistically meaningful versus the base salary cost?
If you're in SF paying market rate, with say a dozen employees, presumably your expenses BEFORE office space are in the range of 200K/mo+.
Unless they're gold plated, your "lavish" offices would represent <~10% of expenses.
Space and perks itself doesn't drive failure I don't think, but they can point to aspects that do.
There are plenty of disciplined companies that appear to be "lavish" with space and perks. There are plenty of highly profitable tech startups that really scrimp on space and perks. It's tough to generalize.
[1] https://37signals.com/remote [2] http://techcrunch.com/2015/11/14/at-github-you-dont-need-no-... [3] https://blog.stackoverflow.com/2013/02/why-we-still-believe-...
Salesforce, Google, Akamai also survived the dotcom bust and also killed when the market came back.
The conditions that create a company under tighter bands will always have a better indicator of limits than companies that don't. They understand the cutthroat nature of the market. Apple could be considered another initially and on their second rebirth since their second rise was after the crash. They were hustling during that on R&D and exploded out the gate when the market came back, part of the reason they hoard cash and control their ecosystem so much, when they opened it up in the late 80s/90s it nearly killed them.
"The economy may be heading into another recession."
I might not want to work at the crappy startups, but their additional engineering demand drives up salaries overall.
But in the transition period it will make VC/angels more risk averse making money harder to find for good startups as well.
Edit: Here is why Google Cloud can save 50% of your aws bill
"1X" is AWS
Compute:
VMs Price: 30% less + Per minute billing
Boot time: ¼ X
Network between VMs: Same region: 4X Across regions: 10X
BigQuery vs Redshift : ½ -20X
Big Data (Hadoop and Spark): 3X
Disks:
Read throughput: 1X Write throughput: 4X (Ephemeral); 2X (Persistent)
Local SSDs: Read throughput: 8X Writes throughput: 4X
Storage (S3): Throughput: 2X Latency: 3X (initial); ½ X (for subsequent reads)
There is an old saying in business: "overhead walks on two legs." People are expensive; everything else is cheap in comparison. This is particularly true for most software companies, where payroll (and other expenses directly sensitive to number of employees) typically dominates every other expense.
There are software companies which do $100 million a year in revenue on $50k a year in infrastructure costs. Bloat that crazily for a B2C startup making, let's say, generous time-to-market and inhouse-expertise-required tradeoffs. Even if you're spending $50k a month on Amazon, shaving off half of that buys you 1~2 extra FTEs.
* Ease of use: Google Wins(Cloud Shell, SSH into instance from browser). Its far easier to spin up an instance and manage it on Google Cloud than AWS with VPC mess.
* Platform Cohesivity: Google Wins (See the comparisio below)
* AWS has 2 storage solutions with different APIS: S3 and Glacier; Compare that to Google. Just one storage solution to serve all needs. You get a backed in CDN for free!
* AWS has two queuing systems (SQS and Kinesis) and still require the developer / admin to adjust the scaling of infrastructure. Google has just one Pub/Sub. You get push notifications on top. No need to tune knobs to get extra scale. It just works.
* AWS load balancers and persistent disks need warming up before high usage. If you are running a website on global scale, you need to use DNS geo load balancing on top. Google load balancers are global (as opposed AWS regional load balancers), no need of DNS tricks. No need of prewarming. Google persistent disks need no prewarming. You can mount a single persistent disk on multiple instance and share data easily.
* Security: Google encrypts data at rest and at wire by default. Try doing that on AWS. Google takes care of SSH key provisioning and management. AWS: You have to do it by yourself.
* AWS NATs and micro instance are known to be unreliable. Google has live migration. If something goes wrong with instance they work their magic behind the scenes so that you don't have to worry about migrating the instance to another physical host.
* Automation: Instance id are not global on AWS. Have fun creating maps and stuff inside CloudFormation templates. Google Cloud resources are global. All resources (images ids) have a global identifier. No more messing with zonal vs regional vs global resources.
Google Cloud can save money by saving your time too!
Also as a nitpick:
>AWS has two queuing systems (SQS and Kinesis)
This is a feature, they offer different promises/behaviors. In fact, Pub/Sub does not offer one of the important ones that Kinesis does (strictly ordered delivery).
One may also say that Google has a single Global seamlessly scalable durable message delivery service and Amazon has two that are neither global nor seamlessly scalable. Firehose is AWS itself admitting to this argument... And then there's firebase :)
I don't think it actually does that.
I'm not certain, but I'm reasonably confident that strictly ordered durable, globally replicated delivery would have to make extreme latency & availability comprimises.
That said, one may order and dedupe the message stream with Dataflow using message metadata, time windows, watermarks and triggers.
PubSub offers at least once delivery semantics.
And I agree with your last statement.
It turns out that while AWS doesn't offer a single "Global seamlessly scalable durable message delivery service", Google doesn't offer a single strictly ordered, at least once delivery message delivery service.
Personally, I think thats ok, as a variety of solutions is great for all of us, but its hard to say one decision is better than the other when they are solving different problems.
There's an interesting blog in the works by one of our customers, who "surprised" PubSub with 4.5 million messages per second, and kept on this test for about a week. One hell of a load test :)
And this is especially true when looking at the product I work on, BigQuery.
It reminds me of 1999 or 2000 were I saw at my local book shop a book titled something like "are you ready for the next 20 years of uninterrupted economic growth ?" written by 2 Nobel price winners, no less ...
Then there was the (should I say first ?) tech bubble pop one or two years later ...
The very fact that 20 people jump in and warn us at the slightest hint (like this) that this is a bubble tells me that we are not in a bubble. Even if people get laid off they will find work else where. Funny thing is that this article talks about laid off tech workers finding work in Finance, which as we speak is getting decimated.
A tech bubble would look different than in 2000 because companies didn't go public the same numbers as last time. That blunts the impact a bit. But it also hides the impact. If VCs go into panic mode you won't know about it until start ups start failing in high numbers from running out of runway.
This betrays a lack of trust that VCs are able to judge the value of a company. That they really only invest in companies because others invest in them. Or that they invest in something they are very familiar with and are unable to recognize technological disruption.
I've a startup so I've never been on the other side of the table, but I can't imagine that there is not also a survival of the fittest on the VC side. Perhaps being very early in a company doesn't pay off in an extraordinary fashion? How would the system not be autocorrecting for VC failure?
IMHO that's the business world in a nutshell. Being scared of innovation and changing the status quo.
Really? I left out the commentor name because of how stupid the comment is and how well banks and the like are doing.
Re: startups, a bit of culling isn't a bad thing, painful yes, but not every idea is pursuing above all else.
What sucks is that many companies that are healthy and not facing layoffs are going to use all this doom and gloom news (that really seems to be trying to feed off itself and spark a downturn that is smaller than they want it to seem) to ride their employees harder, depress salaries, etc.
I strongly advise anyone with any power over salaries and such to consider strongly that if your business is healthy, continue paying a fair market wage. The job market is still strong, and your employees loyalty will disappear overnight the moment you start trying to knock down their pay if you are clearly not in the same boat as over-funded/valued startups and just trying to take advantage of the situation.
(To be clear, I think "SV" implies the style of software companies found in SV that may be found elsewhere in America.)
But seriously, some trepidation like this in the market is probably good for stabilizing some of the office space and housing prices [employers being more fiscally responsible when leasing and employees renting more affordable places in the suburbs anticipating instability and reining in extravagant housing spending --I wanna be able to walk from my flat to the baa that charges me 16 per drink]
This statement seems excessively judgemental. What exactly is wrong with someone wanting to walk from their flat to a bar to pay X for a drink, and pay what housing cost they are OK with for that privilege? And what's wrong with companies paying to be in the same environment? EDIT: rewording
In other words, save your money, maybe you'll have to commute and maybe the bar won't be as close or have all the cool people, but it's worth having money for when there is a collapse.
I see a lot of startup stories here. I fear that part of the problem is that stories get posted, have good discussions, and fall off the front page before many readers see them.
That's it, and I share your fear. I don't know how to solve it. Maybe it's what the majority wants on the top, maybe it's what a vocal minority with high karma points doesn't want (flagging/whatever negative news). I just see the end result. I would just like to get the big picture on the frontpage and not have to rely on algolia search for that.
One thing I realized is that HN front page has very different topics depending on which time I check HN. It shifts its focus depending when people tend to visit HN from east cost, west cost, europe, asia. A useful function would be to check out the HN frontpage how it looked at a specific time. Let's say I would like to see HN as it looked like 8am Pacific timezone yesterday. I know about https://news.ycombinator.com/lists , maybe add another filter to that list.
sigh, kids these days. first of all, i'm sure this exists somewhere on the internet. start with archive.org and go from there. if not, witness:
0 * * * * curl https://news.ycombinator.com -o /tmp/hn-`date "+\%Y-\%m-\%d-\%H:\%M:\%S"`
for bonus points, version control it with github so everyone can see it. even better, send it into elasticsearch. hint: curl -X -F -H
you could implement a website that does this in literally an hour with today's tools. hell, you could even run it through some basic tools like python NLTK and matplotlib and twilio to text message you a fucking color-coded n-gram frequency pie chart every time it runs. you don't need ruby on rails, rabbitmq, redis, and a huge sql schema to do this, just a few lines of bash and python.
this would be more useful than 85.1% of startups operating today, which is probably part of the problem. feel free to steal it.
And.. no-one was really that interested. I used it every now and then to catch up but when HN moved to the new API I didn't bother updating it (although it would be trivial to do so if anyone were interested).
It would be better if everyone can find insightful news stories and comment more. HN is so great because of the smart community and their comments.
Maybe the date time (UTC) like https://news.ycombinator.com/front?day=2016-01-26T08 to view the frontpage as it looked like at 8 am UTC that day. ( ISO date and time: https://en.wikipedia.org/wiki/ISO_8601 )
About the "fall off the front page before many readers see them" problem: that's a serious problem, as the discussion is what makes HN such a great place. Maybe reduce the options to "downvote" a news. It should be enough to upvote a news. If a news fall of the frontpage because certain members don't like it, they shouldn't be able to downvote such news in the first place.
You can already do something like that with hn.algolia.com by doing a query for stories by popularity with a custom date range of a single day.
For example, this search gives you the highest-ranked stories for Feb. 1 - 2:
https://hn.algolia.com/?query=&sort=byPopularity&prefix&page...
Other ideas we've pondered for surfacing good content: letting users mark posts as favorites and share their lists; or letting people nominate posts as "good but overlooked" and assembling lists of those.
Though, if more users of HN could see insightful news, some news would have more comments. And HN is all about comments. I often find out about a news like 8 hours late, and rarely users check back the next day to follow up. (the "threads" link on top definitely helps)
Google isn't a startup. In fact, a company ceases being a "startup" once it finds a business model with which it can sustain itself. If a company can layoff a percentage of it's employees, slow growth, and still make money, they aren't a startup.
We really should stop putting ourselves in double binds with stupid statements like this and reject them when we hear others parroting them.
They're saying that when Google was still a start-up / very young company, it thrived in the post dotcom bust after 2000.