I absolutely love post-Roman, pre-Norman British writing because it's so rare it gives the era a sense of mystery. This is of course the time when King Arthur is supposed to have lived. In the absence of contemporary records, the impulse to fill it with wizards and dragons is understandable.
As someone who has had to do some grub editing on the computer in an AirBnB because peripherals were all messed up on the guest account (no internet, no sound, you could only see a tiny part of the screen, I honestly don't know how they had managed to do it) I am super pleased to see this resource. Stuff like this is a bit, you know, hopefully you never need this, but when you do, it is so useful to have it.
I think this is maybe the most important point in this entire thing. It's not just tech. Things change. The funny thing is things change now faster than ever before, yet we still have that tendency not to notice while we're in it which we always have had. To be honest it's part of why I tend to try to put some bits about tech history in my blog posts - it puts a perspective on life more generally which helps me psychologically.
I think this is a really important distinction to make. The OP seems to be making a fallacious equivocation on the word "parameter" - specifically, any individual "parameter" in a large ML model has no unit of measurement because it doesn't mean anything on its own. I watched a great documentary about the "Soft Hair on Black Holes" paper where they talk about having to move from the blackboard to the computer because the equation explodes into thousand of parameters - the key thing to understand being that each of those parameters represents some "real" thing, a momentum, a charge, a curvature, etc.
I'm not convinced for one reason above all: short-circuit evaluation is available to use in most any programming language I've ever used, including Python and C. That said, I have seen this idiom in a lot of bash scripts. I've never understood why it's idiomatic and I'm not seeing an explanation here.
As someone who's big into UK Bass who finds new music mainly through a mix of Spotify, Beatport and Reddit, I found this recommender quite good actually! It seems to respond better to descriptions of the kind of music than to "Find tracks like these: <list>" which is what Spotify is good at.
So I came to Babylon 5 late in life, when my partner's mother revealed she had the entire box set on DVD. My partner had recently introduced me to The Expanse, which, like many, I consider the greatest sci fi TV show of all time - she described B5 to me thus: "Babylon 5 walked so the Expanse could run." Suffice to say, my expectations were sky high.
No other TV show has so greatly exceeded my expectations.
In B5 the only thing close to ineffable alien were the ones that went beyond the rim. Most of the day-to-day aliens were stand-ins for human nations and cultures.
The OPA and Mars were effectively the day-to-day aliens for the Expanse. The gate-builders were the ineffable aliens.
It is like make but designed specifically for the way non-C(++) users - people like me for example adding scripts like "make run" and "make build" to my node/python/PHP/etc repos - use it. It is great! I still don't use it literally just because make is already installed on any *nix system I encounter day to day.
Interesting, I have never compared make with task but I suppose there’s some overlap. My favorite feature is that it’s cross-platform. I do use it for performing complex builds (like chaining several environment setup and docker compose commands, etc.). Of course you could do this with shell scripts, but this adds a layer of abstraction.
> Are we supposed to find the figurative "gym for problem solving" the same way office workers workout after work?
That's it, yeah. It sucks but it's part of the job. It makes you a better engineer.
You're absolutely right that this isn't sustainable however. In one of my earlier jobs - specifically, the one that trained me up to become the senior engineer I am now - we had "FedEx Fridays" (same day delivery, get it?). In a word, you have a single work day to work on something non-work related, with one condition: you had to have a deliverable by the end of the day. I cannot overstate how useful having something like this in place in the place of business is for junior devs. The trick is convincing tech businesses that this kind of "training" is a legitimate overhead - the kinds of businesses that are run by engineers get this intuitively. The kind that have a non-technical C-suite less so.
reply