Auto-translation used

Non-obvious mistakes in the test tasks of beginners and not only

In test tasks, it is important to specify immediately what level of architecture is expected.

If this is not specified, a reasonable question arises: Is it necessary to design a system with scaling in mind (and if so— in which direction)?

— Or is it enough to show the basic things, adhering to the principles of KISS and YAGNI — not to do too much, but to implement strictly according to the requirements?

In my opinion, if there are no clear instructions, it is better to clarify than to guess and take risks: — do "too much" and get feedback "overloaded", — or vice versa — do it simply and hear "architectural skills not shown".

I have personally encountered both situations. And it's more about communication than it is about skill.

Do you think it's worth describing architectural expectations in test assignments right away?  

Comments 5

Login to leave a comment

Абсолютно согласна — ожидания по уровню архитектуры нужно проговаривать заранее.

Reply

Да, я тоже так считаю. Надо сразу уточнять перед выполнением задач

Reply