This here. If you follow Prisma ORM on GitHub, some of the pain you’ll see is missing features like “whereRaw”, but really most of the pain is forcing you to use raw SQL. And even then, Prisma is extensible, so build your own solutions on top of it. Like Zenstack which creates auth/role permissions on the Prisma schema.
This is an indictment on poor executive leadership, shareholders, headcount planning consultant hacks and internal comms. It's also an indictment on the law itself for allowing this style of layoffs, legal opinion and HR compliance risk assessment to fester at corporations in the US. Don't hate the player, hate the game.
I wouldn't even squarely place the blame on HR. HR is simply a (soulless) messenger. This is an executive level decision that likely has no basis in longterm strategy but rather financial pressures.
I saw it at the enterprise level during the last layoff hell when thousands were let go at my company. On the ground, there was almost little to no logic to the layoffs because the decisions were made by disconnected execs who sit in bullshit meetings all day.
In fact, it goes both ways. Even when teams are expanded out - a decision made in partnership some absurd headcount planning 3rd party consultants - it's almost as if they never talked to the team, but some exec who is 3-4 layers removed from the actual valuable individual contributors who understand the work, have frustrations and desires and should theoretically have a part in influencing planning decisions.
HR is in charge of minimizing risk to the company. One thing that is very risky is claiming performance reasons are a reason for firing when it’s really a layoff. Depending on where they are the state will not be happy that they are trying to game the unemployment system, and federally they may be in violation of the WARN act.
HR is the department responsible for knowing this and not allowing this sort of bs.
Having worked for years in the HR space and at the intersection of compliance, recruiting, legal, and business tech, it's not a complete argument to say that HR is to blame here. Executive leadership, shareholders (and likely consultants) are responsible for these "layoffs". They are the root cause. It most likely still holds true that their decision making is "bigger picture" nonsense based on budgets and short term gains. It also might hold true that they targeted the "low performers" even if that's an incredibly unfair judgment. Anyone who has worked with or knows Sales/AEs understand that 3 months over holidays is not a fair timeframe.
How HR decided to use the reason "low performance" doesn't look great at all, but from my collaboration with HR compliance folks in the past I don't think it's a violation because it's technically the "truth".
I have no doubt this came down from higher up. The reality is that telling someone that they are being fired for unspecified performance reasons when you could just as easily tell them that their position is being eliminated through no fault of their own is outright cruel. In their attempts to make it look like they aren’t doing layoffs they have made the whole internet aware that they are doing layoffs, and that they are treating their employees terribly.
And now they have created a bit of a pr snafu. How many talented people with good performance reviews at Cloudflare are now looking for the door.
It’s incredible there are still people like you who refuse to accept reality. Bug? Engineering issue? Have you considered that your leader is just a fraud and a hypocrite?
* Instead of exporting a file, I'd prefer to see the code in the UI and then decide if I want to piecemeal or just download the whole file with package.json, etc. As someone who iterates it would be annoying to continually download new zips
* Is it possible to define custom primary/secondary colors to use as hashtags? Almost like tailwind config file where I can set up my theme in advance and reuse or @apply through the hashtag. And like tailwind, it would be great to just do #[000000] to set a custom color or value on the fly for a button, etc. or explicitly define #bg-black #text-white etc.
- We definitely want to allow theme customization. I'm not sure exactly what that'll look like, but right now it feels pretty limiting without it. I think primary/secondary could make sense as a place to start.
+1 to this suggestion. It’s part of what makes the breathe app on the Apple Watch engaging, the stream of tapping on your wrist really helps. I’m sure the same can be achieved with the phone.
Crime is up after the lull that was the COVID lockdowns. Less crimes occurred when everyone was at home and the economy was essentially halted. Great argument.
Way too much ORM hate here.