Skip to content
DevMeme
3526 of 7590
DevCommunities Post #3862 · source on Telegram

Why search tabs when Google will relink you to Stack Overflow again

Description

The image uses the well-known two-panel orange-puffer-jacket meme template. Top panel: a person in a bright orange jacket turns away in rejection; the adjacent text says, "Finding the tab you already have open." Bottom panel: the same person smiles and points approvingly; the adjacent text says, "Googling the same keywords to find the same Stackoverflow post." Faces are blurred, background is solid yellow, and the meme was generated with the "mematic" app (small watermark in the lower left). Technically, it pokes fun at developers who keep countless browser tabs open yet still rerun the same search query to reach the identical Stack Overflow solution, highlighting habitual workflow friction and knowledge-retrieval inefficiency

Comments

28
Anonymous ★ Top Pick Chrome tabs are my immutable event log - appending a fresh Google search for the same Stack Overflow answer is way cheaper than running the ‘find existing read model’ query
  1. Anonymous ★ Top Pick

    Chrome tabs are my immutable event log - appending a fresh Google search for the same Stack Overflow answer is way cheaper than running the ‘find existing read model’ query

  2. Anonymous

    The 247 tabs in my browser are a distributed cache with eventual consistency - I just prefer the lower latency of a fresh Google search over implementing proper indexing

  3. Anonymous

    Senior engineers know the real productivity metric isn't lines of code per day - it's the ratio of Stack Overflow tabs opened to tabs actually closed. We've all achieved that zen state where Googling the same error message feels more natural than Ctrl+F through our 47 open tabs, because let's face it: Google's search algorithm is better than our memory, and Stack Overflow's purple links are the only documentation we trust

  4. Anonymous

    Browser tabs are like microservices: they proliferate uncontrollably, defy orchestration, and nuke your RAM when the monolith crashes

  5. Anonymous

    My brain's tab index is O(n), but Ctrl+L -> retype is O(1) to the same Stack Overflow canonical, eventually consistent after every context switch

  6. Anonymous

    Finding the existing tab is a linear-time search across a distributed monolith called Chrome; re-Googling the same StackOverflow post is an idempotent request with better p99 latency

  7. @azizhakberdiev 4y

    That's why everyone keeps 9999+ tabs opened

  8. @freeapp2014 4y

    Why do I relate so much

  9. @BreadCrumberWay 4y

    XDDD

  10. @Dark_Embrace 4y

    Modern browsers search in opened tabs too. And yes. Sometimes I find out that I already have my question opened somewhere.

    1. @freeapp2014 4y

      Usually if you have all that much tabs browsers would just offload most of them or put to sleep mode, so depending on the level of snappiness of your computer it may actually be faster to open the page again than to reactivate that tab

      1. @RiedleroD 4y

        I think no workflow ever makes it actually faster to keep more than 15 tabs open

      2. @Dark_Embrace 4y

        Oh? I have an extension to destroy them completely after 10 minutes of inactivity. So I load it again every time. The speed is not a problem for me.

    2. @casKd_dev 1mo

      reading this and seeing the history search function in modern browsers being a default makes me sad

      1. _ 1mo

        That's a feature I use quite a lot and would relly miss. I can open most sites I use regularly by typing just two letters. And that's an easy way to find back something I read a while ago, usually easier and more reliable than to try to remember specific keywords to search or the path I took to find that page

        1. _ 1mo

          Of course you can disable it if you don't like that

      2. @Dark_Embrace 1mo

        I have >600 tabs. And I can't remember jtc1 sc22 wg21 p2996r13 in https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2996r13.html

        1. @casKd_dev 1mo

          the browser indexes the page title too

          1. @Dark_Embrace 1mo

            Good. But I don't want to rely on it. I want to have it be 100% reachable. Bookmarks will do better. But I just don't have a habbit to use them.

            1. _ 1mo

              In my experience firefox's history search has been very reliable, better than searching again with Google. Thanks to that I can close tabs I don't need right now and be confident I'll reopen them when needed. I don't need to ask myself whether to bookmark a page, as it's already in the history index anyway. The only case where I use bookmarks is for lists of pages I'll want to all open at the same time

              1. @RiedleroD 1mo

                oh yeah, I do that pretty often. I'm pretty sure that it forgets visited URLs sometimes tho, I guess it occasionally cleans old history?

              2. _ 1mo

                But I've just had a bad experience with Chrome, which is more or less imposed at work. Because it deletes history older than a few months (not sure if that's by default or a company policy).

        2. @RiedleroD 1mo

          maybe have less tabs and instead use bookmarks? idk

          1. @RiedleroD 1mo

            to each their own I suppose

          2. @RiedleroD 1mo

            oh wait I misread, my b. I guess searching page contents in bookmarks wouldn't work.

            1. @Dark_Embrace 1mo

              You can use raindrop or some other bookmark utility.

              1. @RiedleroD 1mo

                oh, that sounds neat. maybe I'll take a look at raindrop, thanks for the recommendation

        3. @death_by_oom 1mo

          Scrape it and search with fzf?

Use J and K for navigation