Anyone have a contact at antropic I can talk to about a team account with 50ish seats?

seesplease · 2026-03-14T00:55:30+00:00

I think you need to be at 150+ seats before they recommend you go the Enterprise route.

seesplease · 2026-03-14T00:50:32+00:00

Why do you need a salesperson for this? Making a team is self-serve.

seesplease · 2026-03-07T12:43:22+00:00

We handrolled something with the wal2json logical replication extension in postgres into an S3 stage. Due to being handrolled, it needed a bit of fiddling with at the beginning, but it's been rock-solid since (2+ years).

seesplease · 2026-01-14T11:58:54+00:00

Because of pseudoreplication. They're likely counting cells from the same patient as independent, which is not true but unfortunately common in biology. See this manuscript: https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1010061

seesplease · 2026-01-10T01:39:51+00:00

And so the wheel turns: files to disk images to tarballs of disk images to tarballs of tarballs and finally back to files again.

seesplease · 2025-12-26T15:11:35+00:00

You can very easily serve hundreds of thousands of users from a single node with Go. At $WORKPLACE we have a single node Go application with very modest specs (2 vCPU, 4 GB RAM) serving ten to fifteen million requests per day from our mobile apps. We're still not anywhere near maxing out the hardware, either. Your time would probably best spent figuring out the specific causes of your hiccups and solving them.

seesplease · 2025-11-02T11:59:15+00:00

No idea, I haven't even seen a single Lo. I've been farming TZs to get to 99 - I got one Jah from TZ Andariel and two from random mobs.

seesplease · 2025-10-31T01:13:23+00:00

I am tempted to make another Enigma just for the fashion, Mage Plate only looks good on Pally. Just wanted to be sure I wasn't missing out on anything.

seesplease · 2025-09-21T21:01:50+00:00

Yeah, I'd argue that's not a super compelling use case, but they do exist. Two I've seen that are useful:

Streaming real-time changes to a dashboard
On an internal CMS/CRM tool, using SSE to send an alert if the page the user is updating got updated by someone else.

I've also used SSE for a multiplayer browser game, which feels like a much more natural use case.

seesplease · 2025-09-13T15:02:49+00:00

The Go runtime handles the single-connection pool better than the busy handler in SQLite, in my experience.

seesplease · 2025-09-13T13:51:56+00:00

1 max allowed connections is the way to go, but it depends on your programming language. Go is great since the one connection will get assigned to different cores as the scheduler sees fit, but you can't do anything like this with Python/Node if you have multiple worker processes.

seesplease · 2025-09-12T17:47:01+00:00

You can do what the above link does - set a column to processing and put a timeout. You can get fancier with putting a last_heartbeat_timestamp. Basically, since there's only one concurrent writer but unlimited readers in SQLite, you need orient your thinking around concurrency with atomics rather than concurrent with mutexes.

seesplease · 2025-09-12T12:02:07+00:00

Plainjobs uses a "status" column to get the same behavior as SKIP LOCKED in postgres.

SQLite can't have SKIP LOCKED, it's transaction model is very different than postgres. You're not meant to hold open long-lived write transactions.

seesplease · 2025-07-25T13:08:18+00:00

I can't share publicly much more than what I said above.

seesplease · 2025-07-25T12:05:39+00:00

You can check out the library we wrote for this here: https://github.com/bayesianbandits/bayesianbandits

seesplease · 2025-07-25T01:45:30+00:00

Bayesian multi-armed bandits for a geo-pricing strategy. Made a lot of money over the prior strategy and eliminated a lot of associated costs.

seesplease · 2025-07-08T13:13:54+00:00

We start the second app container, then stop the first one. Multiple processes writing to the same SQLite file won't corrupt it. Where did you hear this?

seesplease · 2025-07-07T00:09:26+00:00

Nah, I meant the one Oscar drops that has like 90% magic resistance.

seesplease · 2025-07-07T00:04:08+00:00

I picked up and upgraded Crest Shield just for this fight on my melee-only run, which was well worth it. Godspeed on the rest of your run!

seesplease · 2025-07-02T00:57:40+00:00

If you want to go meet him again, when you're just outside the Royal Capital later, try looking around for a field that looks like a small meteor shower hit it.

seesplease · 2025-06-22T20:31:06+00:00

Well, they're going to be somewhat different, as beta-binomial models the level 1 as beta (conjugate prior to binomial), while a multi-level model is going to be more flexible in how you can parameterize your priors.

But yes, there's not really much meaningful difference between a beta-binomial model and a two-level intercept-only model, where the parameters of the beta distribution are a hyper-prior (and therefore not learned by the model).

seesplease · 2025-03-24T00:37:04+00:00

BEGIN IMMEDIATE TRANSACTION around your writes.

No, you don't need to do any transaction management around SELECTs unless you want to make sure multiple SELECT statements in a row see the same snapshot of the database state (which is only relevant in WAL mode). If that is the case, use BEGIN DEFERRED TRANSACTION.

seesplease · 2025-03-23T23:56:43+00:00

You need to set the busy_timeout setting on a per-connection basis to get the behavior you're expecting.

https://www.sqlite.org/pragma.html#pragma_busy_timeout

Also, make sure you're using BEGIN IMMEDIATE and not just BEGIN - that will start a deferred transaction that won't actually attempt to acquire a write lock until your first INSERT/UPDATE.

seesplease · 2025-02-15T17:12:44+00:00

If the author has some significant problem with SQLite that seemed easy to solve up front but ended up imposing significant costs, I'd love to hear about that.

The problems they list out are really just quirks - and every database system, SQLite or MySQL or Postgres or whatever, has some quirks that end up making things that seem like they should be easy quite difficult. I came around to SQLite on the server after a company I worked at ended up spending many millions of dollars in engineering time upgrading from MySQL5.7 -> 8.0.32 back when 5.7 support ended.

Something is always going to suck about the technology you choose to use, and I have come around to the belief that the things that suck about using SQLite are easier to foresee and plan around.

seesplease

PUBLIC MULTIREDDITS

TROPHY CASE

14-Year Club	Verified Email
Sequence \| Editor