Блог пользователя _abcd_

Автор _abcd_, история, 5 лет назад, По-английски

In mathematics I am used to read and understand the problem in 70-90 seconds,but in programming i have to spend 4-5 minutes reading the stupid story(Because it does not relate to any application of software engineering), especially UVA and Hackrrank problem statements. Can't they be simple like maths statement?

Mathematical notations are not that hard to get used to.For someone it may be interesting, for me this is annoying.Sometimes after reading a long problem i just found that this a simple problem.

Life will be lot easier for people like us who don't want to read some stupid story , if problems statement are clear and short.

  • Проголосовать: нравится
  • +18
  • Проголосовать: не нравится

»
5 лет назад, # |
  Проголосовать: нравится +151 Проголосовать: не нравится
  1. A problem setter often wants to use their own hero and that makes the statement longer. If you forbid that, the process will be worse (less cool) for setters and fewer will want to make a round.
  2. Math statements are simply less complicated and thus shorter in any version.
  3. Statements with story sometimes allow avoiding definitions like "permutation" or "path".
  4. I guess you should learn to read faster. 4-5 minutes is really long.
  5. Not all stories are stupid. Some are an integral part of the problem, i.e. they are the best possible explanation of what is supposed to be computed.