develwoutacause’s avatardevelwoutacause’s Twitter Archive—№ 187

          1. Had to go through an annual mandatory training today (1 hr). I think I clicked around 150 "next" buttons, each of which took AT LEAST 3 seconds to load the next page. So let's do some #math: 150 presses * 3 seconds each is 450 seconds = 7.5 minutes of wasted time (per user)!
            Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -3 🙁
        1. …in reply to @develwoutacause
          Wikipedia says there are ~115,000 employees at Google. So 115,000 * 7.5 minutes = 862,500 minutes lost annually. That's 14,375 hours or ~1,800 (8 hr) working days! To put that in perspective, there are 250 working days in 2020. 1,800 / 250 = 7.2 employees' annual working time!
          Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -3 🙁
      1. …in reply to @develwoutacause
        In the world of #software, 7 employees is a reasonably sized team; they could ship the next great #mobileapp or #webapp. Want monetary value? Indeed says the average US software engineer's entry salary is ~$115k. 7.2 * $115k = $828k per year *annually*. indeed.com/career/software-engineer/salaries
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +4 🙂
    1. …in reply to @develwoutacause
      That's using **entry** level salary numbers, a real team would have senior and mid-level engineers making more than that, this is easily over $1 MILLION dollars per year, just waiting on page loads! Supposedly, Google pays well above market too! I can neither confirm nor deny...
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -2 🙁
  1. …in reply to @develwoutacause
    **And** this is just one (admittedly large) company. This particular training was from a third-party provider, presumably used by a lot more companies than just Google. These numbers add up fast. How much time and money is lost globally to this one bug?
    On twitter.com Twitter logo develwoutacause’s avatar Mood -3 🙁
    1. …in reply to @develwoutacause
      The sad part is, this is completely avoidable. Trainings like this are mostly a railroad; there's only one "next" button and it knows I'm going to click it. The solution: just preload the next page! There's just no excuse for loading times this consistently long.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar ♻️ 1 Retweets ❤️ 1 Favorite Mood -1 🙁
      1. …in reply to @develwoutacause
        If one engineer took the time to implement proper preloading, they could be saving MILLIONS of dollars of productivity annually! If that were me, I'd ask for my cut and get an early start on retirement. 😌💰🏖️🌅
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -1 🙁