anybody: *mentions anything that a web framework can do* me:

“Automatic connection switching” The way most web apps solve this is by setting a short lived cookie (~5 seconds) after a write. On page refresh, presence of the cookie tells the app to query the primary.

Of course when my wife goes out of town both of my kids get sick, one of them twice 😂

blows my mind that something as simple as a good voice interface to your calendar is currently not available to consumers

Rails still chugging along very nicely for us

20 bucks a pop to drink some goo and go 1% faster

**new Ruby profiler frontend alert**: Puma contributor Joshua Yang is working on a Vernier/prosopite mashup github.com/joshuay03/dial

another new profiler for Ruby: SDB. The underlying design is sort of similar to rbspy. it's aiming to have very low overhead. github.com/yfractal/sdb

Has anyone migrated to PlanetScale and had a bad (or mediocre) experience?

Every ticket for Rails World was claimed within a minute.

Delivered this win by tag-teaming with Andrew Atkinson to help identify what indexes to add that would improve performance on this daily maintenance job. ~100 seconds of DB wait time removed. I've been bringing in a few people to help retainer clients on an ad-hoc basis

Incredibly common Rails perf anti-pattern: Rails.cache.fetch([complicated,cache,key], expires_in: random_interval) do dog_of_a_SQL_query end Cache hitrate: 10% (if anyone even knows what it is)

I hate all wireless tech. The performance and reliability just isn't there. My wireless mouse dips on update rate from ~120hz to ~5hz randomly. Lovely stuff. Very fun.

Show me a hash with 10+ dynamic keys in an ActiveRecord model and I will show you a performance trash fire. 99% of the time this is a hidden view template for something like Intercom/LaunchDarkly/auth that tries to send 95% of the database state to the 3rd party on every req