• MajorasTerribleFate@lemmy.zip
      link
      fedilink
      English
      arrow-up
      11
      ·
      9 hours ago

      As someone who used to work with “large” (to normal people; 10k-60k rows up to maybe 70 columns) datasets in Excel exclusively, I also hate Excel.

      • blindsight@beehaw.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours ago

        Me too!

        I hate working with other people’s spreadsheets.

        Or my old spreadsheets.

        The worst is “can you just add a small feature” to a huge, sprawling, mission-critical, often reused spreadsheet.

        But I love how quick and powerful it is to spin up a new spreadsheet to analyze something or clean up messy data!

    • MissJinx@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      2
      ·
      8 hours ago

      dude you can hate but 80% of “data” still.on excel. I’m in my third global company and people still control things on excel. and 5% power bi (some from excel) hahahahaha

      • djmikeale@feddit.dk
        link
        fedilink
        English
        arrow-up
        2
        ·
        39 minutes ago

        Yep, that’s true haha.

        It’s perhaps not so much Excel, as much as it’s just the symptom of a lot of bigger issues: working without version control, without column validation or access control, limited documentation (not necessarily better in data warehouse but at least the functionality is easily accessible), limited automated testing, etc etc.

        If only they could keep their data for themselves, then ok. but no no, we have to ingest it, and do work on top of it in dwh, and it just breaks so often due to a variety of different stuff.

      • Trainguyrom@reddthat.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 hours ago

        Wait you mean your organization doesn’t use some ludicrously expensive hosted database solution or 3 to aggregate data then instead of natively working with the data in that database it gets exported and transformed on a local machine which may or may not havd backups then ask the database people about weird data quirks coming from the local transformations performed on the data