As someone who conferenced some basic ML research in early 2000s and then left academia for a boring/stable software engineering gig in a non IT org to escape the hype bubble only to end up having to talk to people about ML/AI frequently this article speaks to me.

I don’t have anything against Rust, I’m just not very familiar with it

Pretty much all of the command line coreutils programs I use daily are in C; cd, ls, pwd, touch, rm, etc. If I want to write some small utility I’ll usually reach for a scripting language first like bash python ruby etc, but if it needs to be small and fast I’ll use C instead.

Spend a week or two with each if you can, even if you don’t stick with any you’ll be able to tell what parts you did or didn’t prefer or found difficult or easy that might help make a more informed choice. You might prefer the language features or syntax of one, but the tool chain or frameworks of another.

I’m not sure because google.com requires JavaScript and then when I enable it it says it’s had too much malicious behavior from my VPN address and to enable another host gstatic to connect to I’m guessing for a rechaptcha and I gave up

I think my second favorite thing about Star Wars is the moment in Luke’s hero’s journey when he goes from knight on an adventure to learning to forgive the most hated man in the galaxy when he’s standing on the walkway with Vader after he surrenders in rotj. I’m not saying he’s Shakespeare but he has some good ideas.

Where I’m from we call that Laissez-faire IT

There’s not really a difference between 0 timezones and 1 timezone, let’s split it and go with 1/2 timezones

Based on a completely superficial review there are three almost guaranteed ways to become unhinged; studying infinities, refactoring legacy code, and working with timezones.

Not op but guessing she had an idea from media like TV shows and movies that make technical jobs seem much more exciting for entertainment over realism. Crises are usually more Jerry accidentally deleted a directory and we need to recover some files and establish safe guard procedures to prevent it from happening again or this thing broke that nobody even knew existed so we gotta figure it out and less type fast enough to save the mainframe from l33t hackers.

I think the general idea would be to take the original const, and create a new const with the new location applied. Destroy the original when it’s no longer needed or scoped. State maintained through parameters passed to the move function e.g. move(original const, new location) -> new const object instead of stateful members in the object like move(mutable, new location) -> updated mutable.

Did you know you can significantly degrade the integrity of concrete and cinder blocks using something like dexpan demolition grout and a drill?