Tech News

Article URL: https://rpeszek.github.io/posts/2022-08-30-code-cognitiveload.html

Comments URL: https://news.ycombinator.com/item?id=32666506

Points: 69

# Comments: 19

Article URL: https://blog.ericgoldman.org/archives/2022/06/will-california-eliminate-anonymous-web-browsing-comments-on-ca-ab-2273-the-age-appropriate-design-code-act.htm

Comments URL: https://news.ycombinator.com/item?id=32666995

Points: 137

# Comments: 188

Article URL: https://webkit.org/blog/13140/webkit-on-github/

Comments URL: https://news.ycombinator.com/item?id=32667619

Points: 69

# Comments: 37

Article URL: https://www.wsj.com/articles/saying-goodbye-to-my-parents-library-11661572861

Comments URL: https://news.ycombinator.com/item?id=32668081

Points: 21

# Comments: 14

Article URL: https://jebraat.com/blog/dealing-with-the-perfectionism-trap-as-a-developer

Comments URL: https://news.ycombinator.com/item?id=32668092

Points: 27

# Comments: 25

In the past month we've seen a dramatic, seemingly coordinated, increase in engineering applicants whose resumés and backgrounds appear qualified, but who refuse to use their cameras during Zoom interviews and who often can't answer specific questions about their backgrounds. We've wasted a significant amount of time on comms and interviews with over a dozen of these candidates. Anyone else experiencing anything similar?

Comments URL: https://news.ycombinator.com/item?id=32668694

Points: 91

# Comments: 135

Article URL: https://www.sfexaminer.com/news/why-did-garry-tan-the-new-ceo-of-y-combinator-block-you-on-twitter/article_3fdd1c1c-28b1-11ed-afa8-b3ba9ebc92cb.html

Comments URL: https://news.ycombinator.com/item?id=32669028

Points: 24

# Comments: 6

Article URL: https://www.sec.gov/ix?doc=/Archives/edgar/data/1045810/000104581022000146/nvda-20220826.htm

Comments URL: https://news.ycombinator.com/item?id=32669215

Points: 97

# Comments: 66

The service I am building is usage-based, i.e.

* I am charging per second the service was used, e.g. USD 0.01/second * I would like to give credits upon sign-up. * There is no monthly minimum. At the moment, I am thinking that I can achieve this with just a few tables:

* `billing_account (id, billing_rate_id, running_balance)` * `billing_rate (id, rate)` * `account_credit (id, billing_account_id, timestamp, amount, function_execution_id)` * `account_debit (id, billing_account_id, timestamp, amount, source [platform_credit or stripe])` When a user creates an account, I would create an entry in `billing_account` and associate whatever the current `billing_rate`. I would also create an `account_debit` entry with `source=platform_credit` and update `billing_account` `running_balance` value to reflect their balance after the `platform_credit`.

Then whenever they run a function that costs them, I create `account_credit` account with an entry equal to the amount they spent and update `billing_account` `running_balance` value.

When they top-up their account, I would just add entry to `account_debit` and update the balance again.

This appears to cover all my use cases, but I wanted to check with anyone who's designed such database schemas before.

Comments URL: https://news.ycombinator.com/item?id=32669344

Points: 16

# Comments: 8

Article URL: https://news.ubc.ca/2022/08/30/ubc-team-developing-oral-insulin-tablet-sees-breakthrough-results/

Comments URL: https://news.ycombinator.com/item?id=32669482

Points: 30

# Comments: 13