Best thing about this is that it is available for most of the major platforms with an easy to use GUI. iOS app is excellent.

Some important bugs to beware:

On Windows having the LocalSend app running with the Window visible (after a receive?) prevents the system from sleeping. On Linux, it does the same even if the window isn’t showing. On Linux, having the LocalSend window visible and idle consumes an insane amount of cpu with the desktop window manager constantly refreshing damages. On Windows, the app (with the “startup minimized” option checked) if configured to launch at startup will often show the window anyway (not that you want it running in the background given the sleep issues).

"At first glance, this might seem like a step back — perhaps even un-Svelte-like. Isn't it better if let count is reactive by default? Well, no. The reality is that as applications grow in complexity, figuring out which values are reactive and which aren't can get tricky. And the heuristic only works for let declarations at the top level of a component, which can cause confusion. Having code behave one way inside .svelte files and another inside .js can make it hard to refactor code, for example if you need to turn something into a store so that you can use it in multiple places."

This is absolutely true. I have been confused many times figuring out what are reactive states and what are not.

I never knew Svelte needs changes like this, but seeing this, it sounds like a good plan.

Funny enough, my curent position did not give me a coding interview. Rather they asked difficult technical questions about the technologies I used, and asked me to justify my use of them. I found this was a far better test, because coding out an algorithm is something you can just memorise.

Example: "You've used k8s, how and in what context?" "Ok, great, so you've AWS EC2 instances, how did you manage cost and performance there?" "You're listing Clojure here, what were your thoughts on X feature/limitation"? It was a rather fluid discussion about the ins and outs of technologies, stacks by engineers.

Sometimes actually interrogating someone's knowledge of a system works just as well. I code a lot of things slowly, and need to think through my designs with a pad of paper. I really can't do it when someone is hovering over my shoulder.

The company requested pay slips for the previous three jobs. Also full names and identity card numbers of all relatives, t-shirt size, shoe size, pregnancy status.

This was before the first, codility level interview.