121–130 of 246 posts
Earlier quoted context omitted.
Indeed, laying off the CEO too screws over the entire company, not just the portion of people who got laid off.
Most CEOs are quite disposable.
Earlier quoted context omitted.
Can you even take responsibility for something if you don’t face any consequences yourself? Like a surgeon killing a patient “taking full responsibility”…
Yes, that means that he takes full responsibility for a mistake, and it wasn't due to other staff, equipment, unforeseen events etc...
Isn't giving only a month of severance terrible for morale of remaining team members? I suspect I'd be looking for another job if this was me. Or conversely, why is every other company giving a minimum of 2 months of severance?
It gets to the point where it's hard to even know what to say about the nth tech layoff announcement. It's a good reminder, if we needed one, of how fragile the good times are, for anyone who is an ordinary professional working in an economy like this. I wish there were something more concrete we could do to support each other - like something more concrete than "sure I would recommend people from my network for jobs…
So I read their website and to my understanding, they make a DB interface layer, and have 100+ staff? How is this not a company of like 10 people.
Obviously they have a bigger vision for the tool and needed people to make it happen In all honesty, 100 people is not a big number, you need people like accountants, lawyers, office staff and so on
Using the ORM means I'm tied to this mess of an abstraction, migrations and scripts that require so many workarounds and experimentation to make it worthwhile when your app is not a simple CRUD or you want performance optimizations without ending up writing your own queries yet again. The generated TS API is the only pleasant feature, but doing things the Prisma way I noticed my app is now tied to this ecosystem and its quirks and I dread it. Being unable to check generated queries' SQL beforehand is also a huge issue that is not getting solved any time soon from what I've gathered on their github.
You could also use Prisma as a SQL client and leverage their data proxy, without needing to use the ORM and execute SQL migrations and queries directly, which is what I intend to do from now on. Please do let me know if there are any other generic alternatives database-wise (for "the edge"), I miss raw [Postgre]SQL. Supabase's client is the closest I can think of and it also generates types from your db, but it's obviously not a generic solution.
Lastly, one particular thing that disgusts me (I believe it's not on Prisma but due to how the edge works) is that you cannot use a local database for development. Perhaps ngrok will work, but then you'd need to constantly update your data proxy project settings manually - I need to experiment more on that.
The issues with "enterprise offerings", is that they never tell about their "weakness, shorcomings or disadvantages" comparing to other tools. Why ? I found it's kinda like an "asshole" behaviour, because it tricks people into illusion of a "one tool to do it all". The reality is not, far from truth.
I had to find the gaping holes myself in a way that a typical open-source project would tend to be more up-front about.
It gets to the point where it's hard to even know what to say about the nth tech layoff announcement. It's a good reminder, if we needed one, of how fragile the good times are, for anyone who is an ordinary professional working in an economy like this. I wish there were something more concrete we could do to support each other - like something more concrete than "sure I would recommend people from my network for jobs…
> I wish there were something more concrete we could do to support each other Unionisation would help. We don't do ourselves any favours by not unionising. Almost all job security and employment rights were won by unions and strike action. No wonder unions are a dirty word—according to corporate America. Even when the jobs can't be saved, employment rights are helpful. The Google? Microsoft? announcement basically sa…
The American staff are also paid decently more than other countries. Is getting a 40% pay cut worth getting a few more months of pay before being laid off?
Earlier quoted context omitted.
You mean something like OKRs+KPIs, sales quotas, revenue targets, budgets…
All these that you mentioned are metrics for measuring responsibility towards the company and its shareholders. I mean metrics for measuring responsibility towards the people , especially the laid-off ones - there seems to be absolutely none of these.
First: The people being laid off are shareholders too. Prisma is offering part of their salary in equity.
Second: How would a responsible lay-off other than this look like?
Severance pay: All departing team members will receive one month of additional pay per year of service, plus the payout of any accrued PTO.
Healthcare benefits:
Prismas health benefits for US employees will remain in place through February.
International contractors who don’t have government funded medical cover available will receive an extra $1,000 severance.
Equity vesting: We are waiving the equity cliff for team members who have been with us for more than 6 months but less than 1 year.
Job search support: For all those who wish to, we will do our best to connect you with the various recruitment groups within our investor community.
Equipment: Keep all of the equipment that has been issued to you during the course of your employment with Prisma.
What is the alternative to this? Should Prisma keep the workers, which became unnecessary for reaching the company's goals?
Yes, it's most likely they over hired like every other tech company. But now are in an environment, where it's difficult to raise additional funds. Obviously, Prisma is now adapting and tries to lower the cash burn rate.
Furthermore, it is worth noting that most tech companies massively hired in 2019, 2020 and 2021. If it now becomes obvious, that they hired too many people, what should they do besides cutting?
So I read their website and to my understanding, they make a DB interface layer, and have 100+ staff? How is this not a company of like 10 people.
Obviously they have a bigger vision for the tool and needed people to make it happen In all honesty, 100 people is not a big number, you need people like accountants, lawyers, office staff and so on
From a technological point of view I can't fathom how anyone would add this level of bloat to their project. Just write your SQL queries like a normal person.