alr

joined 1 year ago
[–] alr@programming.dev 3 points 1 year ago

I got news for you. If you're not a citizen of the country you're located in and you don't have a work visa for that country, you're probably working illegally, whether or not your employer realizes. (Some exceptions for EU citizens, Canada, etc.)

[–] alr@programming.dev 1 points 1 year ago

Re: too lazy for Let's Encrypt, a) last I used LE (for my personal site), your site had to be publicly available on the Internet so that you could prove you controlled the site. Most test servers are not public. and b) many (most?) companies would throw a fit if you started generating your own certificates for their domains.

But there are always solutions. I was able to talk my company into getting properly signed certs for our test servers.

[–] alr@programming.dev 1 points 1 year ago

I'm not sure I want my banking apps to store anything on my phone in the first place. But maybe that's just me. I don't even use banking apps.

[–] alr@programming.dev 1 points 1 year ago* (last edited 1 year ago)

If you use JavaScript, you've probably seen a monad, since Promise is a monad. Unit is Promise.resolve(), bind is Promise.then(). As required, Promise.resolve(x).then(y) === y(x) (unit forms a left identity of bind), y.then(Promise.resolve) === y (unit forms a right identity of bind), and x.then(y.then(z)) === x.then(y).then(z) (bind is essentially associative).

You even have the equivalent of Haskell's fancy do-notation (a form of syntactic sugar to save writing unit and bind all over the place) in the form of async/await. It's just not generalized the way it is in Haskell.

[–] alr@programming.dev 10 points 1 year ago

Rather than messing with the EventListener, wouldn't it be easier to just throttle the function that it calls? You can find a bunch of articles online that will explain how to implement a throttle (and also a debouncer, which is similar, but not quite what you're looking for; a throttle allows a function to be called immediately unless it's already been called too recently, while a debouncer waits every time before calling the function and restarts the wait timer every time someone tried to call the function).

[–] alr@programming.dev 2 points 1 year ago

Me too. I got a MacBook for testing Safari, but sometimes I take it to meetings because it's easier than extricating my usual machine from its dock (which unplugs the Ethernet cable so all my SSH sessions die along with anything running in them). But as somebody who likes having things in full screen (it bothers me if I can see the desktop peeking through), I get very annoyed needing to scroll through every app I've got open until I stumble across the one I want every time I have to switch context.

[–] alr@programming.dev 1 points 1 year ago

Unless you're on a contract. If you're in the US and you're not sure if you're on a contract, you're not on a contract. At-will goes both ways.

[–] alr@programming.dev 4 points 1 year ago

Check what your testing organization is using first. We're using Selenium at work, except for one small team that used Cypress because they couldn't be bothered to find out what the test of us were using, so now that team is faced with either maintaining their own version of the CI pipeline and their own tooling (and not having anyone to ask for advice) or rewriting all of their tests. Not an enjoyable choice to have to make.

[–] alr@programming.dev 4 points 1 year ago* (last edited 1 year ago)

The Danish word for 99 is nioghalvfems, which literally means "nine and half five." Which you could be forgiven for assuming meant 11½. The trick is that a) "half five" actually means 4½, as in half less than five, and b) it's implied that you're supposed to multiply the second part by 20. So the proper math is 9 + (-½ + 5) * 20 = 99.

[–] alr@programming.dev 1 points 1 year ago

Of course, the correct way to quit Vi is ^Zpkill vi.

[–] alr@programming.dev 1 points 1 year ago* (last edited 1 year ago) (2 children)

If you think French is bad...

// Danish
farve = "#(9+½+5)FFAA"
view more: ‹ prev next ›