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

help-circle
  • Reminds me of my first big success at work. There was a weekly report that people wanted generated - it showed how much like each operator had done, how much each warehouse had shipped, how many orders we lost from stock issues, etc. it was a low tech company, so they had someone going through the limited UI, looking up each thing one at a time, copying it into excel, and making the report that way. It took hours, and was error prone from stuff like mis-pasting or accidentally skipping a user.

    Took a look at it and was like you could definitely automate this. Used some very primitive scripting to pull all the info out of the system’s UI and dump it into a TSV. Took like a couple minutes to run it, import into excel, and add the colors. But it was super janky because it was manipulating the UI like a user instead of, like, directly querying whatever underlying data store it was running on.

    Still, management was impressed. I later learned no one actually looked at the report most weeks, so that took some of the wind out of my sails.








  • 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.


  • Try not to think too hard about how most of the evidence points to shorter work weeks being better on pretty much every metric.

    Or that most of the “return to office” mandates are counter productive cruelty.

    I think I saw an article that claimed most office workers in the UK do like 3 hours of work a day, and the rest is puttering and looking busy.

    Our system is stupid and it’s stuck stupid because of people. It’s not physics. It’s not biology. Like there’s not much you can do to fix like humans need to eat and sleep, but the workday is just made up.






  • No. Your reading of it is unusual, in most contexts. It almost always means “agreement, and I have nothing of substance to add”.

    It can be rude if the thing you’ve said should warrant a substantial response. Like if you wrote “my brother just died in a car wreck”, a thumbs up (or probably any emoji) would be an inappropriate response. Heavier stuff warrants whole words.

    But if it’s like “Can you get cat food at the store? The kind we always get” then a thumbs up is an acceptable shorthand for "yes, I understand and commit to this request "



  • Depends on how it’s set up. If the setting is going into the env it’s a string, so I’d expect some sort of

    if os.getenv("this_variable", "false").lower() == "true":   # or maybe "in true, yes, on, 1" if you want to be weird like yaml
      this_variable = True
    else:
      this_variable = False
    

    Except maybe a little more elegant and not typed on my phone.

    But if the instructions are telling the user to edit the settings directly, like where I wrote this_variable=True, they’d need to case it correctly there.




  • moving mouse targets. Like let’s say you have two pinned items on the start menu, Firefox and steam. You click Firefox and it starts to open. You go to click steam, but Firefox finishes opening and the icon gets bigger. Steam’s icon then moves to the right, so you click where it was but instead just hit Firefox again. It’s stupid.

    Note how Firefox has solved this with tabs. Open a bunch of browser tabs. Enough so they shrink a little. Then rapidly close some, starting from the left. Notice how they don’t change size until you’re done closing tabs.

    Mouse tunnels. Like you click the “File” menu, and then mouse over “New” and a long sub menu opens. Longer than the original File menu. If you mouse directly from the top of File to the bottom of New, your cursor will briefly be outside either menu. This often will cause the entire menu to close. Mouse tunnel. Have to keep the cursor in the tunnel. Annoying.

    Had an old job that insisted this was fine and refused to let me or anyone change the interface to fix it (on a website)

    Focus stealing. Like you’re typing, and some other application pops up and takes focus. The absolute worst is when it pops up and puts focus on a dialogue box, and you just happened to hit “enter”. Instead of adding a new line to your document, you just accepted something. Awful.