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

help-circle
  • I think a lot about something I read years ago. It said something like, “Some people love their country the way a child loves a parent. The parent is the smartest and the best and perfect. Some people love their country the way an adult loves a peer. They see the strengths, the potential, but also the weaknesses and problems that need to be addressed.”

    Conservatives are generally children. Driven largely by emotion with a very simple moral framework. Much like you will likely struggle to explain to a toddler that taking the other kid’s toys, screaming constantly, and shitting in the sandbox won’t make a lot of friends, explaining politics to a conservative is likely to be an ordeal. They don’t care. They have feelings and that is their reality.

    It’s also kind of funny how conservatives are the ones who typically say “reality doesn’t care about your feelings”. Everything is projection.





  • I’ve worked with a few people who are just incomprehensible. One refuses to write commit messages of any detail. Just “work in progress”. Cast him into the pit.

    There was another guy that refused to name his tests. His code was like

    describe(''. () => {
      it('', () => {
         expect(someFunc()).toEqual(0);
      }
     it('', () => {
        expect(someFunc(1)).toEqual(0);
      }
     it('', () => {
       expect(someFunc("").toEqual(1);
     }
    }
    

    He was like, “Test names are like comments and they turn into lies! So I’m not going to do it.”

    I was like, a. what the fuck. b. do you also not name your files? projects? children?

    He was working at a very big company last I heard.

    edit: If you’re unfamiliar, the convention is to put a human readable description where those empty strings are. This is used in the test output. If one fails, it’ll typically tell include the name in the output.




  • This doesn’t seem like a good idea.

    One, releasing should be easy. At my last job, you clicked “new release” or whatever on GitHub. It then listed all the commits for you. If you “need” an Ai to summarize the commits, you fucked up earlier. Write better commit messages. Review the changes. Use your brain (something the AI can’t do) to make sure you actually want all of this to go out. Click the button. GitHub runs checks and you’re done.

    Most of the time it took a couple minutes at most to do this process.






  • jjjalljs@ttrpg.networktoProgrammer Humor@programming.devNode Modules
    link
    fedilink
    arrow-up
    25
    arrow-down
    1
    ·
    3 months ago

    I don’t know about “fine”. It has a lot of weird stuff baked in. Hoisting. Unexpected type coercion. Too many ways to loop over something and I always forget which one is which. “There’s more than one way to do it” is kind of a recurring problem, come to think of it. Several function declaration syntaxes. Dot notation AND bracket notation for objects.

    Also it will forever bother me that object keys aren’t quoted.

    const foo = "hello"; const bar = { foo: "world" }

    That should be, in my mind, { "hello": "world" } . It’s not. It’s { "foo": "world" }

    But if you want to do that, you need to do const bar = { [foo]: world }. Which looks like your key is an array with one entry, a string with a value of “foo”

    You also end up learning a whole framework, with its syntax and idioms, every couple years. Angular. React. Redux. Whatever.

    There’s also a lot of people who have never used anything else, and want to use javascript for everything.

    Javascript is basically D&D. Wildly popular. Full of legacy jank. People try to use it for anything even though there are better or more specialized tools.


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