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

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.

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.

Because of safety improvement they aren't comparable goods.

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

It it normal for startup in China?

https://dl.acm.org/doi/10.1145/2213836.2213946

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

small things like this have outsized effect

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

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.

Few questions: 1) For a supabase project can we setup replication slot on replica instead of primary? https://sequinstream.com/docs/reference/databases#using-sequ...

2) For a planetscale cluster are the replication slots on primary or the follower nodes?

I'm asking because isn't setting up slots on primary riskier than setting them on replicas/followers? Because If you have them primary In case of WAL buildup your primary will go down?

  Restate.dev:
    for payment integrations on northflank since its faster than cf workflows, independent of cf and its downtime and self-hostable vendor-lock-in free,
  Cloudflare workflows:
    for non critical stuff like csv/pdf report generations since it's very cheap.
  DBOS.dev:
    for workflows that need atomic messaging tied to a postgres db transaction for 100% reliabilty/durabilty(for example populating a materialized row or sending out critical email/push to a merchant).

It also has VirtualObject which is a nice vendor-lock-in-free OSS alternative to CF's single threaded DurableObject.

Where DBOS absolutely shines is

1) Atomic messaging in the same db tx as your business logic via dbos.enqueue_workflow! This is often the most brittle part of any solution and doing it atomically and durably with same tx that ran your business logic drastically reduces lots of complexity.

2) Since DBOS stores workflow state in db it should be easy to build dashboard for observability from metabase/looker(I wish restate exposed its rocksdb instance so it could be hooked up to metabase).

Again non affiliated with either.

    US: 77,000
    European Economic Area: 58,000
    India: 51,000
    China: 48,000(probably undercounted)
    UK: 9,000
    Canada: 7,000
    Brazil: 6,000
    Mexico: 4,000
    Aus & NZ: 2,000
    Eastern Africa: 300
    Western Africa: 500
    Southern Africa: 600
    Northern Africa: 1,000

    Within europe:
    Nordics: 3,000
    Germany: 15,000
    France: 8,000
    Italy: 3,000
    Poland: 5,000
    Romania: 2,000

That's not true? leetcode is crap, but usually you can learn a lot about a person from how they approach problems and on what kind of questions they ask.

There are be plenty of self taught developers who didn't need any "traineeship". That proportion will increase even more with AI/LLMs and the fact that there are no more jobs for youngsters. And actually from looking at the purely toxic comments on this thread, I would say that's a good thing for youngsters to be not be exposed to such "seniors".

Credentialism is dead. "Either ship or shutup" should be the mantra of this age.