• 0 Posts
  • 394 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle

  • Sidebar defaults are bad. There’s no home directory. How do you get to your home directory? Cmd+shift+H, but can you get there without that special shortcut? You can’t see the file system’s structure in Finder. The GUI doesn’t have a way to go “up” in the directory structure. I don’t think you can do it in the GUI alone.

    It won’t let you see stuff in like \tmp\ without a fight, too. I don’t know how to open stuff in places like that without cd’ing to the location in the terminal, and doing open . in the desired directory.

    The list view is the least bad, but it gets unwieldy if your directories are deeply nested. It’s also bad if you started in the middle of the tree and want to go up. Gallery and column view are really bad for anything non trivial.

    I often want to see the entire file path, and it really doesn’t want to cooperate. If I do find the file I’m looking for, and want the full path, it doesn’t want to give it. I don’t even know if there is a way to get it. Other than like cmd+clicking -> “new iterm2 tab here” -> pwd, which is not really that helpful of Finder.

    Contrast with windows’ default explorer. It’s not perfect and I think windows11 made it worse, but still. Open it up, there’s the “my pc”, click through to my user directory, music, some album, then i can click the top thing and get the path. I can also see the whole tree on the left.

    Whatever I was using in Mint was similar to windows’ Explorer. Had no complaints about it.









  • At one of my old jobs, we had a suite of browser tests that would run on PR. It’d stand up the application, open headless chrome, and click through stuff. This was the final end-to-end test suite to make sure that yes, you can still log in and everything plays nicely together.

    Developers were constantly pinging slack about “why is this test broken??”. Most of the time, the error message would be like “Never found an element matching css selector #whatever” or “Element with css selector #loading-spinner never went away”. There’d be screenshots and logs, and usually when you’d look you’d see like the loading spinner was stuck, and the client had gotten a 400 back from the server because someone broke something.

    We put a giant red box on the CI/CD page explaining what to do. Where to read the traces, reminding them there’s a screenshot, etc. Still got questions.

    I put a giant ascii cat in the test output, right before the error trace, with instructions in a word bubble. People would ping me, “why is this test broken?”. I’d say “What did the cat say?” They’d say “What cat?” And I’d know they hadn’t even looked at the error message.

    There’s a kind of learned helplessness with some developers and tests. It’s weird.







  • Not a fan. It admittedly can be an amusing toy - type something in and wow look what it did! But the costs are high, and our society isn’t a utopia where people don’t need to labor for survival.

    Maybe if we were post scarcity it wouldn’t matter that much. But we’re not, and this AI stuff is going to hurt labor, benefit the ownership class, and probably be mildly bad for end users too.