> Part of the assignment is using judgment and working in ambiguity.
I love that the industry has become so poor at gathering requirements that devs are now effectively filtered for their ability to mind read.
I love that the industry has become so poor at gathering requirements that devs are now effectively filtered for their ability to mind read.
This project tests your ability not only to code, but to deal with ambiguity and open-endedness
I'm not sure how I feel about that to be honest. On one hand I get what they're shooting for in general by saying that. On the other, they're going to have some preconceived notion of what they want, and it's a bit of luck if you come close to that.> And don't hesitate to tell us if you have any questions!
I personally have no problem dealing with "ambiguity and open-endedness" (and, in fact, enjoy it!), but my solution to this problem at every job that has had this issue is: talk to people and understand the problem.
Attempting to "mind-read" is the worst solution to ambiguity, and, in practice, nearly always leads to disaster.
When the client can play with that, the scope can be expanded and additional features can be described.
What they want is someone they can work with. Take home tests are about cultural fit too.