Log inSign up
Log inSign up
rumdash.io
91 posts
rumdash.io profile banner
@rumdash_io

rumdash.io

@rumdash_io
building rumdash.io, a Real User Monitoring (RUM) service
Denver, CO
rumdash.io
Joined May 2023
178 Following
27 Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·US TIDA·Ads Info·© 2026 X Corp.
  • @rumdash_io
    rumdash.io
    @rumdash_io
    Dec 2, 2025
    I've started sprinkling dictation into my (mac) workflow, and one place it's become really valuable is when having to submit 2FA verification codes sent to my phone. Reading them out is way nicer than writing them out, though I only recommend you do so when in private.
  • @rumdash_io
    rumdash.io
    @rumdash_io
    Sep 3, 2024
    The 2014 NFC Championship
    @TheStalwart
    Joe Weisenthal
    @TheStalwart
    Sep 3, 2024
    What moment in history or in your life deradicalized you?
  • @rumdash_io
    rumdash.io
    @rumdash_io
    Aug 27, 2024
    The *majority* of performance issues in web apps are from over-bloated front-ends. Optimize your FE application's bootstrapping before you go fixating on a 300ms API call.
    @nateberkopec
    Nate Berkopec
    @nateberkopec
    Aug 27, 2024
    > "Ruby isn't high performance enough for us" > Their website downloads 7mb of JavaScript to display a blog post, makes 3 network requests in a row to hydrate data, re-layouts twice
  • @rumdash_io
    rumdash.io
    @rumdash_io
    Aug 24, 2024
    Show them the performance impact of using styled-components or all the BEM victims wandering the streets speaking in tongues.
    This post is unavailable.
  • @rumdash_io
    rumdash.io
    @rumdash_io
    Jul 31, 2024
    Tell me you don't believe the Next.js marketing claims without telling me you don't believe the Next.js marketing claims.
    @nateberkopec
    Nate Berkopec
    @nateberkopec
    Jul 31, 2024
    People will continue to believe marketing claims made by framework/library authors about performance because it means that their own app is blameless when it comes to perf problems, it's just that pesky 3rd-party code that's slowing them down! Of course, the reality...