Sam Ballantyne

earnest tweets no caps

[Sam Ballantyne @routinelover]

@zachlloydtweets Try conductor!

[Sam Ballantyne @routinelover]

@alitaylor Which hotel? We stayed at 京旅籠むげん and felt similarly.

[Sam Ballantyne @routinelover]

@stevekrouse I agree with all three statements

[Sam Ballantyne @routinelover]

@SCP_Hughes :wave: I'm just a software engineer, but a fan of your work. Was in Bilbao last week and thought of you — lots of interesting urban design in Basque country.

If you're in Brooklyn at some point I'd love to grab a coffee or go for a walk.

[Sam Ballantyne @routinelover]

@adamwathan One nit: it would be preferable if the paymentId in your example could be passed as a prop to openDialog. Useful for lists of things.

(You can always nest the Dialog in the list item component but that's a little less nice).

[Sam Ballantyne @routinelover]

@KabirCreates Looks like this paper https://t.co/brmk7YCHtw tried something like this, which then turned into a startup https://t.co/nt9cdHR1ks

[Sam Ballantyne @routinelover]

@KabirCreates But you can see how performance is the boundary here

[Sam Ballantyne @routinelover]

@KabirCreates Arbitrary database reads. I'm wondering there there's a way to implement event-sourcing in plain SQL with an events table.

So everything is write to an `events` table, then you do crud on top of that like `with users as (select id, name from events e where e.type = 'signup')`

[Sam Ballantyne @routinelover]

@KabirCreates Like https://t.co/n8ATgi0JoF is interesting but it's not consistent reads

[Sam Ballantyne @routinelover]

@KabirCreates Yes, append-only, but I'm not sure SQL cursors are it.

Imagine a heavily-written-to txns table, maybe you'd run
`select avg(amount) from txns`. It's a big table so this takes a long time. You'd like to be able to store the result as-of that query, so u can run it later cheaply

[Sam Ballantyne @routinelover]

@tarstarr @zenazn @stripe @edwinwee @patrickc Hey Tara! It's good feedback! We're rolling out a fix today: better copy plus we'll text you from the old number first so you know what to expect.

Keep the takes coming :)

[Sam Ballantyne @routinelover]

@martinkl Not trying to be a jerk, but I think the literal answer is that everything would cost more, and there would be a large cottage industry of folks estimating emissions, and occasional exposes on how that system did not work as intended.

[Sam Ballantyne @routinelover]

@tomlarkworthy @tldraw I'd love to noodle on it and/or test it out!

[Sam Ballantyne @routinelover]

@tomlarkworthy I'm excited about eg @XStateJS but it's targeted at the frontend and I haven't been able to figure out how to apply it on the backend

[Sam Ballantyne @routinelover]

@tomlarkworthy Out of curiosity, have you ever seen state machines actually adopted on the backend for used cases larger than just a single model? Eg an auth flow

[Sam Ballantyne @routinelover]

@spakhm In the context of the EMH, I think what’s he’s saying is “whatever your idea or interest is, don’t assume that someone has thought of it, or already tried it, or mastered it; imagine a village of 500, everything can be improved upon. Imagine you live there”

[Sam Ballantyne @routinelover]

@Austen Honest question: did you read the article? The $42M figure is misleading, and the bureaucrat running the enterprise is open and well-informed. It seems like above-par leadership from a civil servant tbh

[Sam Ballantyne @routinelover]

@ArtirKel vibes

[Sam Ballantyne @routinelover]

@AFarnsy @mollyfmielke Would be very happy to beta test for you!