Thar makes sense, although I am generally not trying to use the keyboard at the same time (to be honest I was not aware you could filter a finder view like that, I thought it only ran search and I have never found MacOS’s search to be satisfactory)

Interesting, I’m not aware of any way they would affect compile errors. I’d be curious to know more.

Fair enough, I like it better without but I don’t have a strong preference and have no issue adapting to whatever the style of the repo is.

I learned about it researching tools to automatically enforce formatting style and came across StandardJS, which eliminates them by default.

How would you propose to organize it then?

I still run into this issue when one of my company’s clients requires developing on Windows. Doesn’t take many subfolders before node_modules just starts breaking.

There are lots of reasons I hate developing on windows and that’s certainly one of them.

I use that all the time but never knew it had a specific name.

Because if you’re looking for a subfolder you’re not looking for a file, and vice versa? It doesn’t matter much in sparse directories, but it annoys me having to scroll through a ton of files to find the folder I want in directories with both.

I too like a lot of things about Mac, but finder could be improved, for sure.

(I have gotten used to a lot of its features and hate Windows’ defaults too, so there’s that. I don’t think an ideal exists, unless it’s in Linux somewhere and I just need to dual boot the desktop and get it over with)

No,I’ll just disable the cron job before it executes and forget about it.

So do I, but I don’t think I need to worry too much about confusing them with 2090.

Writing the tests first also ensures that the test actually fails when you expect it to. I’ve seen test suites that were silently failing for years because they were (presumably) written after the fact and people just assumed that they tested what they said they did. Went in for some other clean up, stared at the test for 10 minutes wondering “how did this ever pass”, and then came to realize that test assertions in Jest inside a forEach apparently don’t run in the context of the test and failures won’t make the test fail. Changing the forEach to a for…of made it all fail immediately.

Neither Javascript nor Typescript require semicolon, it is entirely a stylistic choice except in very rare circumstances that do not come up in normal code.