Being fluent in your professional vernacular is very important for productivity. And a closed test is the best, scalable way we have to test this.
Being fluent in your professional vernacular is very important for productivity. And a closed test is the best, scalable way we have to test this.
Sure I could, it'd be fine, but why store the entire syntax structure in my mind rather than a pointer to the location where I can find it in its most updated form?
There is a surprising amount of complexity behind switch/case.
My current requirements, just this month, are:
* Python
* PHP
* Javascript
* React and Vue
* TypeScript (but not in every JS project!)
* Blade templating
* Liquid templating
* Whatever Algolia uses for it's inline templating
* Bash
* C# (games!)
And if you want you could throw in arbitrary configuration syntaxes for all the infrastructure as code insanity that comes with it all, some of those have loops.For apps and web development, I wouldn't fuss too much about specific language syntaxes since if I were to cull my applicants based on language experience I'd be throwing away plenty of talented developers. I'd hire a talented Python developer for a job writing JS for example, if they're applying then they're willing to learn it.
By scalable you mean cheap.
An actual test would be: design a whole system/experiment to do a thing, in 3 hours.
Can't look up basic things, you'll be too slow.
But then it can't be auto marked, so isn't cheap.
Exams: The very last time in your life you won't have internet access.
True story: when I became a programmer in the 1990s, I used to buy the printed manuals for the Java APIs as they were released. At one of my first interviews (for a Perl job), I was given the Camel Book as reference for the (handwritten) programming test.
The medical industry is not a solutions provider. You should view them as a useful tool, but one that still leaves you with the responsibility to utilize the useful tool to solve your problems.
I am not making a normative claim here; I'm making a descriptive one. The medical system is an incredible toolset, but you need to be ready to assemble it into a solution. Maybe it should be a solutions provider. Maybe it's really discriminatory against the people who won't or can't operate this way. No argument. But it observably isn't a solutions provider today, whatever "should" be.
In this particular case, if you care you should have scheduled a followup with a different doctor. ER doctors don't do that sort of analysis.
That ship sailed a long time ago.