HN user
I don't think of those as business logic, per se. They're just validity checks on what the data should look like before it's written to disk - they're not actionable in the way L/N is. That being said, constraints usually end up being duplicated outside the db anyway, but having them where the data rests (so you don't have to assume every client is using the correct constraint code) makes sense.
This kind of issue always comes up when people put business logic inside the database. Databases are for data. The data goes in and the data goes out, but the data does not get to decide what happens next based on itself. That's what application code is for.
I go through this with my wife for every party we throw. She wants the house cleaned, table set, food spread ready, seasonal cocktails mixed, furniture moved around, decorations just so, etc.
I’m like here’s a giant thing of ice cold booze have fun.
The conglomerate of Big Furby™ will finally be taken down
It doesn't seem like the extra traffic is the issue. People don't want Google's AI from reading and summarizing their data and thus preventing clickthroughs. Why would I click on your site if google did all the work of giving me the answer ahead of time?
You’d be wise to avoid this place anyway. You can tell from the description it’s not a fun place to work.
I see. I was wondering where the hammer and sickle came in, since without those is it really a communist flag?
On the flip side I was at a startup using auth0, because as you said, not a core part of the business right? Until the traction hit and they had hundreds of thousands of users. Suddenly the auth bill became untenable - users are great but there wasn’t enough revenue to cover these costs. Auth0 didn’t budge. In fact they were outright nasty to deal with. They were holding our user logins and passwords hostage and they knew it.
I'm having a lot of trouble visualizing both the flag and the list modifications.
I am net negative in lines of code added to two different companies I've worked for. I wear that proudly.
I also ran into this trying to upgrade my company's auth strategy. The hardest part of auth is convincing people that... it's not actually as hard or dangerous as they think it is. It was an uphill and ultimately unsuccessful battle of mine. People can't even divorce JWTs as simple, verifiable json data blobs from the entirety of the OAuth2 spec. You see it on HN, with hundreds of circular comment threads and I've seen it in real life.
Did you go to high school, bn-l?
Why do these companies keep trying to fire remote employees? Is it so hard to let them keep working from home? Is the company's real estate portfolio that important? You could probably even pay remote workers less (or give non-remote employees a "bonus" for coming in) and everyone would still be happy.