When I was looking for my last job I rejected a company based on the simplicity of it's code task. A company's code task should interest and challenge. View helpers satisfy neither requirement (for me).
I disagree, and cite fizzbuzz. There are so many programming candidates who can't even answer a simple problem like fizzbuzz that it prunes out a good number of candidates by asking a simple question like that. Not every step in an interview is intended to meet the same goals, e.g. your coding question could have easily been a quick pruning method versus saying anything about what sort of work is being done there.
Comments
When I was looking for my last job I rejected a company based on the simplicity of it's code task. A company's code task should interest and challenge. View helpers satisfy neither requirement (for me).
I disagree, and cite fizzbuzz. There are so many programming candidates who can't even answer a simple problem like fizzbuzz that it prunes out a good number of candidates by asking a simple question like that. Not every step in an interview is intended to meet the same goals, e.g. your coding question could have easily been a quick pruning method versus saying anything about what sort of work is being done there.