As someone who's scared of all the lay offs happening, what should I do to calm down and keep going?
Prisma laying off 28% staff
161–170 of 246 posts
Re: Prisma laying off 28% staff
#162Re: Prisma laying off 28% staff
#163I don’t want to be another HN commenter saying I could build Prisma in a weekend, because I can’t. I couldn’t build Prisma in a year, in five years, in large part because I’m not smart enough. But bloody hell, VC backing and that many employees? I happened to recently give Prisma a whirl, and even for my simple toy project, the holes in the client functionality do not feel consistent with my understanding of what tha…
Re: Prisma laying off 28% staff
#164This is why I use no ORMs and use mysql like a man.
Re: Prisma laying off 28% staff
#165Earlier quoted context omitted.
FANGM all did layoffs. And many other companies as well. That they are all incompetent can't be the explanation.
Sure it is. Google for example increased headcount by 24% in a year and cut it 6% in the next year, a clear sign they made a bad decision. Further in Google’s case they have plenty of money to pay these people until headcount naturally shrinks, but they don’t have anything useful enough for them to do that waiting and avoiding a large severance package is cheaper.
it sounds like greed, not incompetence.
I just do not believe in a worldview where almost all CEOs of large tech companies are incompetent. Whatever the explanation for layoffs is, incompetence ain't it.
Re: Prisma laying off 28% staff
#166Re: Prisma laying off 28% staff
#167I'd be interested to know the age (or any other) demographic of HN'ers commenting on posts like these. Lot of people sounding very personally slighted by companies trying to remain profitable (or just in business).
In some ways we’re all consultants
Re: Prisma laying off 28% staff
#168I explained the other day to a friend how Prisma looks great but it's very unresponsive on Github [1], specially surprising since they raised a lot of money so I thought they'd have more resources. So he introduced me to the concept of FOSS-washing (in relation to greenwashing). Launch a cool open source piece of software, get big clients and funding thanks to it and then basically ignore Github or just dedicate enou…
For example, I want to add ltree support to Prisma (which could also extend to MSSQL’s Hierarchy). I’ve shepherded this whole thing through at least 4 repos, adding the necessary pieces in order to make it work.
Their communication and follow up has been generally poor. The engineers they have on staff are capable but they either don’t see the value in larger OSS contributions or don’t have the time to manage both the internal and external roadmapping?
Idk, I just want my PRs reviewed and merged lol
Re: Prisma laying off 28% staff
#169Earlier quoted context omitted.
Yes, that means that he takes full responsibility for a mistake, and it wasn't due to other staff, equipment, unforeseen events etc...
Responsibility without consequence is meaningless.