If you're at a games studio that values build-times, value that. I worked at a very good SRE-mindset studio and missed it, deeply, after I left. Back then I expected everyone to think and care about such things and have spent many, many hours advocating for best-in-class, more efficient, cheaper development practices.
WRT github actions... I agree with OOP, they leave much to be desired, esp when working on high-velocity work. My ci/cd runs locally first and then GHA is (slower) verification, low-noise, step.
They don’t really tell you how someone works or thinks though. They just show you that the candidate thinks in one of a certain number of ways. If they can’t answer it could be down to a range of factors, that one hadn’t foreseen.
The “thinking ways” that allow one to solve the problem can be considered to be socio-normative and neuro-typical; normally these fit white patriarchal modalities.
The mental modalities that make it harder to solve such problems are those related to sequence memory weaknesses, comprehension weaknesses, stress factors, attention weaknesses, social differences, exposure, culture, education. So dyslexics, ADHD, Autistics, socio deprived (poorer backgrounds), may struggle with tums like this that assume a consistent world view - when in fact they likely have other strengths in problem solving. It’s not a one size fit all.
Additionally like IQ, ability to solve these types of problem
is down to either natural ability or practise in the domain - that is you can increase your IQ by training against the core elements IQ tests look at.
I tend to get candidates to take me through something they know well, or love, or have solved, and then I ask them about how they did it. This shows me genuinely how good they’ll be at the job in hand.. and is why my teams are actually diverse.
One core reason chaining can be bad is robustness; another longevity/maintenance.
Specifically around type-safety, that is knowing that the chained type is what you expect and communicating that expectation to the person who is reading the code without them needing to know the wider context of both the chained-API nor the function the chain resides in. In the context of this article, that means more complexity, and therefore less readability.
I feel this is important because I have worked on many legacy code bases where bugs were found where chains were not behaving as expected, normally after attrition in some other part of the code base, and then you have to become a detective to work out the original intent.
For readability chains are bad, because they can lie about their intent, especially if there’s various semantics that can be swapped. But, like any industry or code base, if their use is consistent, and the api mature/stable, they can be powerful and fast, if.
WRT github actions... I agree with OOP, they leave much to be desired, esp when working on high-velocity work. My ci/cd runs locally first and then GHA is (slower) verification, low-noise, step.