catfood

I think it's one of those things where you have to work in the field to really get it and be productive. You just don't have the time or resources otherwise.

The should ask Claude to make the page scroll faster.

Letting it rip and give it full infra, db, dns, all the keys to the castle, drinking from a telemetry firehose the whole time, a huge tangled web of integrations that all kind of works. I think just offloading as much as possible is the state of things.

Practically free with any of the subscription plans.

>Auto-fix bugs and CI until green + thermonuclear review skill x3.

Gotta love this loop, I have it running while I'm asleep all the time.

I can't relate. It's so nice for quickly going deep on a subject you're interested in. Who cares if you typed the code in plain English?

It would be fun to plop Claude Code down on a phone and play with the baseband processor.

>And Web Serial reached mainline Firefox last week.

That's good news. I wish FF wasn't so conservative... they're missing a lot of cool APIs. Sometimes I wonder who they think their audience is. I suppose they would know better than I would.

One of the greatest texts ever written. Ok maybe just one of my favorites. I wouldn't mind a 2nd edition though... surely the system call interface has changed a bit since 2010.

A bunch of different ways probably. This method is stolen from SO (works for Chrome):

const detect = () => { var fs = window.RequestFileSystem || window.webkitRequestFileSystem; if (!fs) { console.log("FS check failed.."); return; } fs(window.TEMPORARY, 100, function (fs) {}, function (err) { console.log("Incognito"); }); };

You're in luck, Divinity 2 runs perfectly for me on linux with Proton (with a little bit of work). Check protondb.com.

I don't do anything special for prototyping, I just use what I normally do if I were creating the real thing.

> django-admin startproject > copy+paste my webpack config for React > copy+paste my general management scripts into the package.json (mostly scripts to build the client, and if working locally also start a server)

Then if I want to deploy it, I just install nginx and gunicorn and again copy+paste my configs for those.

If I want to use mysql it's not too much trouble, takes 10 mins to get it up and running and my application hooked up to it.

Yeah they must mean new accounts, if not then I'm lost. I guess it could have reset autoincrement but they said it didn't. The only other thing I can think of is that the signed token that's put in localStorage is sent to the server like "someuser|sometoken", the server inspects sometoken, says it checks out, then takes the client at its word that it's someuser.

The part of that that I don't get is how a new user could have the same ID as an old (truncated) user since "our system created new records for them, with primary keys generated from the existing sequence (PostgreSQL does not reset id sequences on truncate)."

Do they mean that the only potentially exposed accounts are those that signed up after the database was restored?