Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Thank you for this - reading through the comments, I've been actually quite surprised that the general opinion seems to side with the students. The article suggests that the allowed image formats were clearly defined. Normally, if I were to take this test, I would definitely make sure that I am meeting the technical prerequisites.

Of course, you can argue that not everyone is familiar with the technicalities of image formats. But then again, let's not forget that today's students are "digital natives", so I assume they both now about JPEG and PNG and also about their phones.

However, if I now hear that this point was explicitly addressed in relevant FAQ's, all of the above really becomes irrelevant in my opinion, because it really doesn't leave much in terms of excuses.

At college, every test came with certain rules. For this exam, you're allowed to use any auxiliaries except computers. And stuff like that. You must write in permanent ink. etc. Images must be in one of the following format: ... IMO is just along the same lines.

There is an old principle in jurisdiction: ignorantia juris non excusat - basically stating that it's your responsibility to know the rules.



On the other hand, the article mentions that a demo test did accept (renamed) HEIC files. If you test your setup and are told it works fine, you shouldn't need to dig through FAQs.

I would argue this falls under the equally old jurisdictional principle of estoppel or detrimental reliance.


If the system accepted the files, then what was the problem?


Per the article, the "demo" test accepted it, but the actual exam did not.

Perhaps the demo did something dumb, like check the file extension but not whether the file could actually be opened.


In that case I completely agree. If the demo was there specifically to test technical setups, then it should not behave differently from the exam system. In particular, such a test system should be compliant to what is expressed in the FAQ.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: