pull down to refresh

I find framework/tool/infrastructure additions to be more trouble than they're worth at SN's scale.[1]

We currently construct time buckets of stats in a normal table. Instead of continuously refreshing those time buckets, I'm thinking of doing some kind of incremental update atomic with a payment's state transitions.

  1. my general vibe is to abuse what we have (frameworks/abstractions/whatever) until they can't do the job anymore

my general vibe is to abuse what we have (frameworks/abstractions/whatever) until they can't do the job anymore ↩

I think this is the way to go in general, even beyond your scale. New systems can be such a can of worms and should only be added with great care (of course there are exceptions)

reply