I'm showing my age; my initial reaction was "I had no idea Apollo Computer had anyone left to lay off" https://en.wikipedia.org/wiki/Apollo_Computer
Apollo Layoffs
141–150 of 219 posts
Re: Apollo Layoffs
#142I have no idea what Apollo Graph QL is, but it was interesting to search by URL and see the progression of related HN titles and their engagement. 2018 July. Apollo server 2 released woo! (mostly ignored) 2019 Feb. We switched away from Slack woo! . . . (Some PRs everybody ignored) 2019 June. We got a $22M investment woo! . . . (Many PRs everybody ignored) 2022 Dec. Oops, we are laying of lots of people...
Apollo is synonymous with Graphql at this point. If you need you consume a Graphql API you most certainly reach out for Apollo on the clientside to query data.
They’re certainly good at getting their name out there, but their libraries seem to be waning in popularity in most of the places people discuss GraphQL.
I’ve personally never used Apollo stuff in prod —- there’s always been a more suitable alternative, but I’ve always appreciated their code for being quite clean. Federation is an interesting technology, but I haven’t had cause to use it yet.
Re: Apollo Layoffs
#143Re: Apollo Layoffs
#144Earlier quoted context omitted.
Crazy. Usually it's just "Pay stops today, benefits at the end of the month. Hand in your badge - off you go."
No it's not. Severance is extremely common, while this package is quite generous.
Severance is common in high paying tech jobs. Severance is not common in general.
Almost 60% of US workers are hourly and most of them don't get severance. A lot of the other 40% dont either.
https://www.workstream.us/blog/hourly-vs-salaried-jobs-benef...
Re: Apollo Layoffs
#145Re: Apollo Layoffs
#146Earlier quoted context omitted.
I don't know about the company or how they make money with it (support?), but Apollo is pretty much the standard GraphQL client for frontends. It has pretty sophisticated cache and state management, type generation for typescript, etc.
It’s arguably the least sophisticated of the major clients (Apollo, Urql, Relay), but they’ve done a great job with marketing and documentation. But I’ve personally never used it in a real project because Relay has always existed and I know how to use it.
And for the server? What do you use instead of Apollo?
Re: Apollo Layoffs
#147I have no idea what Apollo Graph QL is, but it was interesting to search by URL and see the progression of related HN titles and their engagement. 2018 July. Apollo server 2 released woo! (mostly ignored) 2019 Feb. We switched away from Slack woo! . . . (Some PRs everybody ignored) 2019 June. We got a $22M investment woo! . . . (Many PRs everybody ignored) 2022 Dec. Oops, we are laying of lots of people...
Apollo is not _the_ GraphQL company, nor is it synonymous with GraphQL. Nobody is those things.
It's just a way of saying that they are all about GraphQL. They are there for all you GraphQL needs and everything they do is related to GraphQL.
Re: Apollo Layoffs
#148Earlier quoted context omitted.
Did anyone claim a linear (let alone 1:1) gain? This was the relevant part of what you replied to: > It doesn't certainly doesn't mean anything as broad as "a company cannot do more things by increasing its employee count."
There is a sweet spot for how many people should be on a team. That number depends entirely on a nature of tasks. I would even go as far as to say - in a good environment up to that sweet spot, productivity gain is linear. And yes, managers do expect close to linear productivity gain past that spot. Managers, that are a little smarter, start thinking about how spotify did squad (without actually knowing anything abou…
The term "Two pizza team" comes from Amazon and describes a team size such that it is the number of people that can be fed by two pizzas. The reality is that the term is not only a reference to team size but, rather, underscores the concept of "Accountability".
https://developers.redhat.com/blog/2022/10/21/coming-terms-t...
I think a well composed small team can have greater than linear improvement in effectiveness because of skill stretch and decreasing blindspots.
Re: Apollo Layoffs
#149Earlier quoted context omitted.
The "$300 mental health" seems odd - for any kind of counseling/therapy/etc sessions this is a drop in the bucket in terms of cost. It will easily cost 10x to work with a mental health professional (and insurance companies sadly pay a very small amount of it). So why add this to an otherwise reasonable package?
$300 is incredibly reasonable since it's more than $0.
To clarify why it bothers me: It tries to tell a story of "we as a company care about you", but at least in my experience, health care plans cover less than $100 per session, and in the SF Bay Area you easily pay $200+ per session for mental health professionals (as they are often out of network).
Maybe Apollo's health care plan has much better out of network coverage than what I'm familiar with, in which case I stand corrected (and agreed that its good to help cover copays, if this is what this actually does).
Re: Apollo Layoffs
#150Earlier quoted context omitted.
Employers are by dollar amount the biggest actual thieves by far in the US. Business owners ought to generally receive more scorn and critical evaluation than common property thieves who represent a thin fragment, if we really care about theft
Why don't you go start a business and become one of these rich employers you speak of? If taking such risks wasn't rewarded accordingly, then I don't think people would be nearly as eager to start a business.
I'm talking about a system at scale, not individual actors. You don't know what I'm doing as an individual and it's not relevant to a discussion of material reality as observed. If your solution to this problem at scale is for everyone to become a rich employer in order to avoid wage theft, I don't know what to tell you
Re: risk staked, I will add that for many business owners their greatest risk and fear is simply having to work for a wage themselves.