I suspect you have a different notion of what conversion meant than Gladys did. For you it seems to be about internal beliefs; for her it was about external declaration, ceremony, and recognition. Likely beliefs had very little to do with the whole thing.
Huh. Now you are making me picture a metal detector design with an array of overlapping current loops and a fancy deconvolution software on top that gives you an image (probably very fuzzy but still an image) of what magnetic source its detecting. Could be pretty cool!
Is there anywhere a collected writeup of performance review practices of different large employers? I feel like things are somewhat homogenized but by no means is it exactly the same process everywhere...
The horseshoe principle applies on the malice/incompetence dimension. Any sufficiently advanced malice is indistinguishable from incompetence. (Disguising ill intent by as incompetent design is one of the strongest deniability approaches.) But also any sufficiently advanced incompetence is indistinguishable from malice. (A bad actor can fully compromise an incompetently designed system as well as if the vulnerabilities had been intentional.)
Is Julia at the level of stability to be useable by large projects? I've tried to follow and it always looked promising but there were a lot of reports about things being subtly broken in hard-to-debug ways . Anyone have more recent experience?
I did a bunch of contract work last year at a company that was all-in on Julia and it was a really pleasant experience.
IMO one of the issues with Julia is that it’s easy to get nerd-sniped trying to do clever things with the type system and to make as much of your code as possible statically-inferable. Code and libraries that rely heavily on type dispatch ends up throwing MethodErrors deep into the call stack, far away from your code, which makes it harder to debug them.
More mature Julia developers tend to keep things simpler, and make better use of dynamic types instead of contorting to treat it like a statically-typed language.
Have been writing all my numerical code in Julia for the last 1.5 years, haven’t run into any issues at all.
Actively use things like Trixi.jl (CFD framework), Jump/IPOPT/PRIMA for numerical optimisation, OrdinaryDifferentialEquations for ODE solutions; a few colleagues actively use Gridap.jl for their work.
Not sure how large-scale these libraries can be considered, but they all seem to work fine, fast, and stable (potential issues with LoopVectorization.jl in upcoming versions of Julia are somewhat concerning, but IIRC, for 1.11 this has been resolved)
Julia’s been stable for my work, from what I understand, things have gotten better over the years on that front. The biggest issue Julia gives me is packaging, just because two libraries that you import can use different versions of the same dependency (among other things)
agree! how to play??? I found I can click and join knights by knight move with the same subscripts. but what is the king doing? there are no directions and its not obvious!
Apparently he is worth 1024 so you can take him when you have a 1024 piece, and win. I didn't realise this (or that he takes pieces when cornered - I avoided that, assuming a stalemate would mean losing) so played it right through to a regular 2048 which took a verrry long while.
In the legal filing yes spacex putting their stuff on the property is a main complaint. The lawsuit alleges trespassing, destruction of the pristine state of the property, and reputational damage. No idea how well the suit will fare but it certainly appears to have some merit.
reply