Skip header to navigation
a head full of caching issues by
Timo Mämecke
Jump back to navigation
  • , 2 minute read

    There’s a new bug in the YouTube TV app for Google TV that is so utterly stupid that I need to rant about it.

    When you play a video and press back on the remote, it should jump back 10 seconds. Well, now it now jumps back 10 seconds… and then immediately skips forwards 10 seconds to where you were before. So pressing back is basically doing nothing anymore, other than glitching a bit. You have to press back multiple times, or pause first and then press back.

    The same thing also happens when you press forwards: It skips forwards 10 seconds, and then jumps back to where you were before.

    This is already pretty annoying. But now comes the best part:

    There’s this “Jump ahead” YouTube Premium feature that entirely skips a commonly skipped segment. You press forwards once, it knows that many people skipped this segment as well, and then jumps ahead to where other people usually jumped to. It basically allows you to skip sponsor segments quickly. So you press forwards once on the remote, it skips to the end of the sponsor segment, and you can immediately continue. That’s a really great feature! The UX is a bit meh but in theory it’s a great idea.

    But now, with this freaking new bug, it skips the sponsor segment, then glitches back, and then thinks that you didn’t want to skip the whole segment (because it looks like you jumped back), so it removes this skipping point so moving forwards won’t skip the whole segment again. Which means you can’t skip the segment again. So this whole freaking feature is now not working anymore.

    There are some UX lessons here about these “magic features” that sometimes appear and disappear that I might want to write about in the future, but for now I only care about how the actual fuck it’s possible that the YOUTUBE APP—the official app for THE SECOND MOST VISITED WEBSITE ON THE WORLD—developed by FREAKING GOOGLE is constantly shipping broken crap that’s noticeable within seconds of using a core feature. When did software turn so shit?

  • Build the Goddamn Product

    The number of times I still see “Loop Engineering” popping up in any of my feeds is truly upsetting.

    The amount of effort you spend on meta-engineering is an illusion of a return on investment that will allow you to build the product better, faster and with greater ease.

    It’s the same as building your own framework, or framework-in-a-framework, because you think that all other frameworks out there are slowing down your ability to build the actual product.

    Read more
    • Timo’s avatar

      Trying to get back into latte art and doing something that’s not just a simple heart!

      A feather is still pretty close to a heart though.

  • Software Engineering won’t be over

    Every few months, software engineering will be over in a few months again. It can’t be, but for reasons you might not expect.

    When coming back to work in the beginning of 2026, organizations everywhere were going crazy. So many people, including lots of upper management, had used the winter break to build software with AI and felt that software engineering was over. They had experienced it first-hand. Everything had changed, because look at what they built! Why couldn’t work feel the same?

    Their experiences were real, but they happened in isolation. Building software by yourself is orders of magnitude easier than building it in a team, or across multiple teams. The hard problem at work was never just about writing code. Their experiences didn’t reflect the challenges of the organization they worked in.

    Read more
  • Hang on, loading more…