3 ms·
> did the person write a test for every line of code? No? Does anyone expect this for 2 hour assignment? Seriously!?
by dvh 11y ago
> did the person write a test for every line of code? No?
Does anyone expect this for 2 hour assignment? Seriously!?
- bloat 11y agoPlenty of shops insist on strict test first development. If this is one of them, then why wouldn't they insist on it in their hiring process? As long as it's an explicit requirement of the assignment, what's the problem?
- karmajunkie 11y agoBecause even using TDD there are some things that just don't warrant a test.
- Lewton 11y agoThe author didn't really imply that it was important
- Ensorceled 11y agoYes. I've twice been criticized on "short" interview coding assignments for not having _enough_ unit tests. I had unit tests, just not enough in their minds. One position was CTO and the other was a Software Director position. Tech interviews are getting crazy.
- pc86 11y agoWhy is someone applying for CTO performing coding challenges?
- sundaeofshock 11y agoBecause the company is not really hiring a CTO. What they are hiring is a senior developer who will put in a full week of work coding, and then will be asked to put in another 40 hours dealing with management tasks. The "CTO" title is there to try to make up for the fact that the position is woefully under-compensated.
- Ensorceled 11y agoExactly. "Well, it will grow into a CTO role". They also didn't have an answer to "How often does the board meet and how long is my part of the meeting, typically?"