|
|
|
|
|
by rrouse
4642 days ago
|
|
An interview recently felt like that. I was just throwing together little bits of code to make sure I understood the problem clearly, but the interviewer seemed to be a bit agitated that I didn't write a test right away. I honestly don't work like that. So I'm kinda glad I failed that interview. |
|
It always begins a discussion of the problem and what we want to solve, plus a bit of how—so we can figure out what it is that we're going to be testing for and how to build from that point.