saxenaabhi

That's not the only thing

Someone else mentioned TOTP codes that are hard to copy

My personal gripe is that NFC readers can't read wallet passes. That's also true for google/android.

Both apple/google restrict it and only few very big retailers are using it.

You mentioned elsewhere "But PL/SQL is a horrifying language. You have barely any facilities for modularity, encapsulation or composition"

That's not true about PL/SQL. You can modularize/encapsulate and compose multiple sql functions.

Even plain SQL can be composable in some cases via views.

Why wouldn't you use stored procedures for it? For internal teams why is it better to have a API?

I can see usecases in which API could make sense, but it doesn't matter in most cases.

SQL already has authorization/authentication built in. For rate limiting you can use something like planetscale's traffic control.

This is very poorly written and is wrong on basic facts.

> So what does a stored procedure get us? > Absolutely nothing! Well, I mean, headache for one.

> ... we have to deploy migrations to update our queries, and we have to run diff migration_for_my_sproc migration_for_my_sproc_n to see how things changed

1) You can version sql functions in your repo alongside your code and deploy sql function alongside your db migrations(even in the same transaction).

Have one file per sql function and you can also compute checksums to speed it up if like me you have a repo with 600 stored procedures.

2) With stored procedures you have no need to to db.startTransaction on server when executing multiple statements and wait for db round trips. That's often the biggest reason for preferring stored procedures.

3) I have seen systems in healthcare/finance where different teams have no access to underlying tables and the db only exposes sql procedures. Every-time a procedure is called it also adds a log entry to an audit table.

Databases are a great piece of technology! Learning how to use them properly can have huge payoff in terms of business value generation.

EDIT: not mentioned in this article but people often mention testing difficulties with stored procedures.

You can have normal vitest tests testing your postgres functions with in-memory pglite.

I have had many fitbits, but for my mom I purchased an Apple watch because it had sleep apnea notifications. I think that's essential for almost everyone.

I can't imagine why google would skip such a critical feature in Health Tracking.

Punjab and Rajasthan have the highest proportion of vegetarians and also rank on the top of male/female height charts.

Admittedly it's not fully vegan but still.

Indians have long recognized the virtues of a vegetarian diet: both the moral imperative & it's health benefits. That's something everyone should be able to admire.

I prefer following:

1) CDC for archiving/recovery or as an audit log

2) downstream consumers consuming a business-events table. Kind of like inverted event-sourcing pattern.

CDC is sound for sure but only in the lowest technically sense. Downstream consumers consuming business events gets you all the benefits of event sourcing(Namabilty, Replayability etc) while keeping relational guarantees and transactional safety.

with a much higher chance of dying in 1975 Cessna 182? I suspect most rational consumers won't.

Because of safety improvement they aren't comparable goods.

Maybe acceptable in some cases but the original example in this thread was about accounting and they use software to do the counting not humans.

And even id humans/llms do it there would still be a need for systems of record with things like audit log etc.

IPO within year of founding?

It it normal for startup in China?

> I'm having a lot of trouble with distribution

Maybe add a link to playstore/appstore under the generated promo code

small things like this have outsized effect

Your app didn't silently break when you upgrade rails or any other gem?

If ruby was statically typed the typechecker would have caught it.

Sure, but i don't think it's reasonable to hold given level of capability constant in a landscape where a give consumer of AI also has competitive pressures.

I can't use last year's SOTA model when my competitors can use the current SOTA model.

This is also baked in the eye watering valuations of model companies.