Recent submissions

Comment · 4 months ago
What's that? Any particular dosage?
Comment · 7 months ago
That may be, but I think you are missing the point of the outrage: this solution is not good.
Comment · 2 years ago
It can be great, but I've noticed lag during screen sharing. Other colleagues have noticed it too.

Even so... it's better than slack for audio/video and my organization uses teams as primary for calls and slack for text communications(group chats, channels, dms)

Comment · 4 years ago
What do you mean by "series A"? :)

I never hid the scripts. The automation was out in the open and everybody in the team was making use of them.

I quit because I didn't receive pay raise and wouldn't have in that position(EDIT: They wanted to promote me to team lead(people management), but it is something I'm not interested in). Plus with the skills I've gained I managed to get a better paying job.

Comment · 4 years ago
That's how I became a software developer. I was working for a big tech firm as a data entry "specialist". Everything (except some pricing calculations) was done manually. I was hired as the 7th member of the team. It started with copy/pasting some simple VBA scripts to automate small tasks. In a year I managed to automate most of the tasks. More notably: A monthly task that took 2 days(and quite prone to human errors) of the entire team into a less than an hour job for a single person. And automated discrepancy checks between the data sources.

It was quite satisfying and made me realize that I should be doing this for a living. I quit that company for way better pay as a software developer. I don't know if I'll be able to find such a job again, but I really enjoyed it.

Comment · 4 years ago
setTimeout doesn't guarantee that it will execute exactly after 3000.

  (() => {
    const targ = $(".setGo");
    const targ2 = $(".theSport > div:nth-child(2)");
    const observer = new MutationObserver((mutations, observer) => {
      if (mutations[0]?.target?.classList.contains('going')) {
        targ2.childNodes.forEach(c => c.click());
      }
    });
  
    observer.observe(targ, {
      subtree: false,
      attributes: true
    });
  
    $('.readyButton').click()
  })();
  
This gives me consistent Time: 0.001 in FF. "Time: not yet set" in Edge/Chrome.
Comment · 4 years ago
Nice :) What library did you use for the graphics?
Comment · 6 years ago
I don't know much about the history of these tests. Can Hanlon's razor principle be applied here?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton